Trouble making a filesystem

[Patrick Mahan]

> -----Original Message-----
> From: owner-freebsd-mips at freebsd.org [mailto:owner-freebsd-
> mips at freebsd.org] On Behalf Of Andrew Duane
> Sent: Wednesday, April 06, 2011 2:15 PM
> To: Juli Mallett
> Cc: mips at freebsd.org
> Subject: RE: Trouble making a filesystem
>
> Some sample files are:
>
> /sbin/init: ELF 64-bit MSB MIPS32 rel2 executable, MIPS, version 1
> (FreeBSD), for FreeBSD 9.0 (900034), statically linked, not stripped
> /bin/cat:   ELF 64-bit MSB MIPS32 rel2 executable, MIPS, version 1
> (FreeBSD), for FreeBSD 9.0 (900034), dynamically linked (uses shared libs),
> not stripped
>
> /sbin/init works, it is statically linked. /bin/cat does not, it is
> dynamically linked. It could be an issue with the linker not being packaged
> or some other configuration issue, like ldscript not being there.
>
>
> I tried the "make distribute" and it yelled at me for /base not existing.
> DESTDIR is set to my local directory, which worked for installworld, but
> distribute seems to forcibly override it to /base
>

For the dynamically linked images, what does ldd show?  Is it possible that
the kernel is able to find ldd?  I ran into this a couple times when porting
linux to a new platform and usually when it tried to exec ldd it failed because
ldd was either missing (or in the case of a cavium port, it had failed to build
a 64-bit version on a 32-bit host system).

Patrick

>
> /Andrew
>
>
> -----Original Message-----
> From: juli at clockworksquid.com [mailto:juli at clockworksquid.com] On Behalf Of
> Juli Mallett
> Sent: Wednesday, April 06, 2011 5:05 PM
> To: Andrew Duane
> Cc: mips at freebsd.org
> Subject: Re: Trouble making a filesystem
>
> On Wed, Apr 6, 2011 at 13:58, Andrew Duane <aduane at juniper.net> wrote:
> > I'm having trouble making a working filesystem for my OCTEON1 kernel to
> run on. I do a "buildworld", but there are three problems:
> >
> > 1) Most of the executables won't execute, they give "Exec format error".
> The problem seems to be with dynamically linked executables. When I rebuilt
> "/bin/sh" as a static executable, it worked OK. I guess I could manually
> fix every Makefile to use static linking, but that seems absurd.
>
> It would probably be helpful to include your build scripts and the
> output of 'file' on one of the troublesome binaries.
>
> > 2) Some things aren't being populated. For example, that the only thing
> in the buildworld output of etc is sendmail. In the installworld output
> there are a handful of subdirectorties, but no "rc" files.
>
> You need 'make distribute DESTDIR=/whatever'.  Or is it make
> distribution?  Something.  Then you'll just need to set up fstab and
> rc.conf
>
> > 3) Eventually, the kernel tips over with:
> >
> >   panic: sched_priority: invalid priority 231: nice 0, ticks 1955000
> ftick 14022821 ltick 14023821 tick pri 59
>
> I've never seen this.  Sounds like a problem with signed vs. unsigned
> chars for priorities.  Most of those should be fixed these days,
> though.
> _______________________________________________
> freebsd-mips at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-mips
> To unsubscribe, send any mail to "freebsd-mips-unsubscribe at freebsd.org"