>1) Am I correct in assuming it doesn't matter about the processor
> type with binutils?
Yes.
>2) armv3 is the *right* type definition for an ARM610?
Yes. The reason binutils didn't like it is just because its configure scripts
need updating.
>In file included from /usr/local/armv3-linux/include/linux/ptrace.h:24,
> from /usr/local/armv3-linux/include/linux/personality.h:5,
> from ../sysdeps/unix/sysv/linux/init-first.c:23:
>/usr/local/armv3-linux/include/asm/ptrace.h:4: asm/proc/ptrace.h: No such
>file or directory
You have to make the appropriate symlinks in the kernel source directory.
This happens automatically when you configure the kernel; otherwise you must
manually link include/asm-arm/proc-armv -> include/asm-arm/proc and so on.
>binutils successfully compiled with arm-linux-aout as the target as did
>egcs. Neither of them liked armv3-linux-aout. What target processor have
>I actually built these for. What do I do about libraries. Sources for
>libc4 are not on the ARM Linux web site.
I think the default target processor for a.out is still an ARM3. Binutils
doesn't care, it's only egcs that needs to know.
>Am I right in thinking that the 2.0 kernels are broken wrt ELF for the
>ARM?
It might be OK in the latest versions. Corel's are definitely OK but their
source may not work on non-NetWinder machines.
>What is the best kernel to use for an ELF system.
I use 2.2.1 quite successfully.
>What other tools do I need to build to get an aout/ELF hybrid
>system up and running.
None that I can think of.
p.
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
