>Now, for the first pass (to get a kernel onto the board) is arm-linux
>the correct target?

Yes.

>(I am confused about the arm-elf and other targets for standalone boards
>- why aren't I using the stand alone board target?)

`Stand alone' in this context implies no operating system.  It would probably 
work to compile the kernel itself with an arm-elf compiler in fact but you 
need arm-linux for user space things.  Also, the arm-elf support in the Linux 
versions of egcs is in a somewhat indeterminate state so I don't suggest you 
use it.

>OK assuming that arm-linux is the right target, and I am cross
>compiling on a solaris machine, then why do you recommend
>the --build=i586-linux switch for configure on the web page at:
>[...]
>The dialog there says it is necessary, but it can be anything so long
>as it is different to the host system type.
>
>(I also noticed in one of the recent emails that you told Jason to use:
>CC=arm-linux-gcc ./configure arm-linux --enable-add-ons
>--prefix=whatever
>So is the build switch actually unnecessary?)

I think the --build switch is certainly less necessary these days than it used 
to be.  Maybe you can get away without it altogether.  In that email to Jason 
I just forgot about it.

As you mention above, all that matters is that --build is different from the 
host.  Some parts of the configure system use this to determine whether 
they're cross-compiling or not.

>*** You should not compile the GNU libc without the `linuxthreads' and
>*** `crypt' add-on.  Not using them risks to be incompatible with the
>
>DO I REALLY NEED THESE??

Yes.  I think linuxthreads at least is pretty non-negotiable.  You can 
probably make do without crypt but I don't recommend it.

>I don't want to have to blast away glibc2.1 and
>get the crypt package. I tried the --disable-sanity-checks switch and
>got:

Just download crypt and linuxthreads and unpack them according to the 
instructions.  I don't follow what you're saying about `blasting away 
glibc2.1'.  What's the big deal?

p.


unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]

Reply via email to