Christopher Friedt wrote:
Hi Jeff,
Crossdev will _always_ pick the most recent package available. That
unfortunately has a high correlation with being unstable. If I were
you,
and especially since you're building for glibc, I would stick to
<binutils-2. 17, <glibc-2.5, and ~gcc-3.4.6 or ~gcc-4.1.1 .
The linux kernel headers have changed quite dramatically after 2.6.19.
If you're building something to be bleeding edge, then use the 2.6.21
headers, but you could also do pretty well with something like
>=2.6.18
<2.6.20 .
jcunningham63 wrote:
> I am going to work through your list today and see what I can make
> work. I am puzzled that Triffid Hunter was able build a toolchain
that
> I am not:
>
> "crossdev -t arm-unknown- linux-gnu worked for me. 2nd stage gcc
failed
> first time around, but emerge --resume fixed it. crossdev chose
> binutils-2.17, gcc-4.1.2, glibc-2.5-r3 and linux-headers- 2.6.21
for me
> all by itself."
>
> (from http://tech.
groups.yahoo. com/group/ ts-7000/message/ 7204 )
>
> Have you tried this particular combination yourself?
So to answer your question, no, I didn't try that particular
combination.
I was working on this myself for some time, still not finished, but
what
would be __incredibly_ _ useful for the gentoo embedded people would be
to have an automated build script for all combinations of versions,
with
'rules' (that is, don't try combinations that will absolutely not
compile).
This could end up being something in the range of hundreds of
combinations, which each take between 20 and 50 minutes on my single
1.73 GHz processor. What this sort of app needs is DistCC - i.e.
distributed computation, otherwise the full range of combinations could
literally take weeks.
If you're interested in working together on such a project, please let
me know, because it would be of incredible use to a lot of people.
~/Chris
Yes, I am interested. I have several Gentoo boxes sitting around doing
not much in addition to the one I work on most of the time.
I ran your last case that worked for you and it failed, so something is
amiss. Here's what I ran:
USE="-* nls glibc-omitfp nptl nptlonly tls" crossdev \
--b 2.16.1-r3 \
--g 4.1.1-r3 \
--k 2.6.19.2-r2 \
--l 2.3.6-r5 \
-t arm-unknown-linux-gnu
Here is the topmost error message:
gcc version.c -c -std=gnu99 -O2 -Wall
-Winline -Wstrict-prototypes -Wwrite-strings -fno-strict-aliasing
-march=athlon-xp -pipe
-g0 -O2 -fgcse-after-reload -finline-functions -fomit-frame-pointer
-D__USE_STRING_INLINES -I../include -I. -I/var/tmp/cross/a
rm-unknown-linux-gnu/portage/cross-arm-unknown-linux-gnu/glibc-2.3.6-r5/work/build-default-arm-unknown-linux-gnu-linuxthreads/csu
-I.. -I../libio
-I/var/tmp/cross/arm-unknown-linux-gnu/portage/cross-arm-unknown-linux-gnu/glibc-2.3.6-r5/work/build-default-ar
m-unknown-linux-gnu-linuxthreads -I../sysdeps/arm/elf
-I../linuxthreads/sysdeps/unix/sysv/linux/arm
-I../linuxthreads/sysdeps/uni
x/sysv/linux -I../linuxthreads/sysdeps/pthread -I../sysdeps/pthread
-I../linuxthreads/sysdeps/unix/sysv -I../linuxthreads/sysdeps
/unix -I../linuxthreads/sysdeps/arm -I../libidn/sysdeps/unix
-I../sysdeps/unix/sysv/linux/arm -I../sysdeps/unix/sysv/linux -I../s
ysdeps/gnu -I../sysdeps/unix/common -I../sysdeps/unix/mman
-I../sysdeps/unix/inet -I../sysdeps/unix/sysv -I../sysdeps/unix/arm -I
../sysdeps/unix -I../sysdeps/posix -I../sysdeps/arm/fpu
-I../sysdeps/arm -I../sysdeps/wordsize-32 -I../sysdeps/ieee754/flt-32
-I.
./sysdeps/ieee754/dbl-64 -I../sysdeps/ieee754 -I../sysdeps/generic/elf
-I../sysdeps/generic -nostdinc -isystem /usr/lib/gcc/i686-
pc-linux-gnu/4.1.2/include -isystem
/usr/arm-unknown-linux-gnu/usr/include -D_LIBC_REENTRANT -include
../include/libc-symbols.h
-DHAVE_INITFINI -o
/var/tmp/cross/arm-unknown-linux-gnu/portage/cross-arm-unknown-linux-gnu/glibc-2.3.6-r5/work/build-defaul
t-arm-unknown-linux-gnu-linuxthreads/csu/version.o -MD -MP -MF
/var/tmp/cross/arm-unknown-linux-gnu/portage/cross-arm-unknown-lin
ux-gnu/glibc-2.3.6-r5/work/build-default-arm-unknown-linux-gnu-linuxthreads/csu/version.o.dt
-MT /var/tmp/cross/arm-unknown-linux
-gnu/portage/cross-arm-unknown-linux-gnu/glibc-2.3.6-r5/work/build-default-arm-unknown-linux-gnu-linuxthreads/csu/version.o
../sysdeps/unix/sysv/linux/arm/sysdep.S:
Assembler messages:
../sysdeps/unix/sysv/linux/arm/sysdep.S:31: Error: no such instruction:
`rsb r0,r0,$0'
../sysdeps/unix/arm/sysdep.S:41: Error: invalid char '[' beginning
operand 2 `[sp'
../sysdeps/unix/arm/sysdep.S:42: Error: invalid char '[' beginning
operand 2 `[sp'
../sysdeps/unix/arm/sysdep.S:43: Error: no such instruction: `bl
__errno_location(PLT)'
../sysdeps/unix/arm/sysdep.S:44: Error: no such instruction: `ldr
r1,[sp],'
../sysdeps/unix/arm/sysdep.S:45: Error: invalid char '[' beginning
operand 2 `[r0]'
../sysdeps/unix/arm/sysdep.S:46: Error: no such instruction: `mvn r0,$0'
../sysdeps/unix/arm/sysdep.S:47: Error: no such instruction: `ldr
pc,[sp],'
make[2]: ***
[/var/tmp/cross/arm-unknown-linux-gnu/portage/cross-arm-unknown-linux-gnu/glibc-2.3.6-r5/work/build-default-arm-unkn
own-linux-gnu-linuxthreads/csu/sysdep.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory
`/var/tmp/cross/arm-unknown-linux-gnu/portage/cross-arm-unknown-linux-gnu/glibc-2.3.6-r5/work/glibc-2.
3.6/csu'
make[1]: *** [csu/subdir_lib] Error 2
make[1]: Leaving directory
`/var/tmp/cross/arm-unknown-linux-gnu/portage/cross-arm-unknown-linux-gnu/glibc-2.3.6-r5/work/glibc-2.
3.6'
make: *** [all] Error 2
!!! ERROR: cross-arm-unknown-linux-gnu/glibc-2.3.6-r5 failed.
Call stack:
ebuild.sh, line 1615: Called dyn_compile
ebuild.sh, line 972: Called qa_call 'src_compile'
ebuild.sh, line 44: Called src_compile
glibc-2.3.6-r5.ebuild, line 1127: Called src_compile
glibc-2.3.6-r5.ebuild, line 1138: Called toolchain-glibc_src_compile
glibc-2.3.6-r5.ebuild, line 221: Called die
The use flags came from Triffid Hunter. I am trying it without any USE
flags now. I'm taking a look at your script...
Incidentally, what is the difference between the 9tdmi build and the
vanilla (unknown) build? I have a ts7200 board.
Thanks.
Jeff
__._,_.___
![]()
SPONSORED LINKS
__,_._,___
|
|