Skip to contentSkip to conversation

ARM EABI toolchain - anyone build it successfully?

Buildroot Tomasz Chmielewski 2 participants 14 messages Aug 19, 2008 – Aug 20, 2008

lore
Share & tools
lore
#0 lore raw

I'm trying to make ARM EABI toolchain using the latest snapshot of Buildroot.
However, no matter which options I use (thread library implementation, uClibc version etc.) I'm only able to build GCC (4.3.1).

Then, it breaks later on on building uClibc.

I also tried building uClibc from nptl branch, but it also failed.

As different thread library implementations and uClibc versions give different errors, I won't paste it here, unless requested.

So my question - did anyone manage to build ARM EABI toolchain with buildroot (GCC 4.3.1 + uClibc; I also need busybox)?

Signature · 2 lines
Tomasz Chmielewski
http://wpkg.org
#1 lore raw
Quoted 2 lines · Tomasz Chmielewski

So my question - did anyone manage to build ARM EABI toolchain with buildroot (GCC 4.3.1 + uClibc; I also need busybox)?

Built fine for me last time i tried.

#2 lore raw
Quoted 6 lines · Bernhard Reutner-Fischer
Quoted 2 lines · Tomasz Chmielewski

So my question - did anyone manage to build ARM EABI toolchain with buildroot (GCC 4.3.1 + uClibc; I also need busybox)?

Built fine for me last time i tried.

Do you still have it anywhere?

If yes, could you paste your .config for Buildroot?

If possible, also .config for uClibc?

Signature · 2 lines
Tomasz Chmielewski
http://wpkg.org
#3 lore raw
Quoted 9 lines · Tomasz Chmielewski
Quoted 6 lines · Bernhard Reutner-Fischer
Quoted 2 lines · Tomasz Chmielewski

So my question - did anyone manage to build ARM EABI toolchain with buildroot (GCC 4.3.1 + uClibc; I also need busybox)?

Built fine for me last time i tried.

Do you still have it anywhere?

Unfortunately i've lost the disk that contained the configs, but going off a minimal config should work fine.

#4 lore raw
Quoted 11 lines · Bernhard Reutner-Fischer
Quoted 7 lines · Tomasz Chmielewski
Quoted 5 lines · Bernhard Reutner-Fischer
Quoted 2 lines · Tomasz Chmielewski

So my question - did anyone manage to build ARM EABI toolchain with buildroot (GCC 4.3.1 + uClibc; I also need busybox)?

Built fine for me last time i tried.

Do you still have it anywhere?

Unfortunately i've lost the disk that contained the configs, but going off a minimal config should work fine.

OK, it builds (I had a custom uClibc config, which perhaps made some problems), but even then, lots of Busybox things don't work.

I.e.:

# ./busybox
(...)
Currently defined functions:
         ash, cat, mount, sh, sleep, switch_root, umount, whoami
# ./busybox ash
Illegal instruction

Similar to: http://bugs.busybox.net/view.php?id=3364 which maybe points to http://bugs.busybox.net/view.php?id=0003804 (some things are build as EABI, and some things are build as OABI, although EABI is chosen).

Signature · 2 lines
Tomasz Chmielewski
http://wpkg.org
#5 lore raw
Quoted 5 lines · Tomasz Chmielewski

OK, it builds (I had a custom uClibc config, which perhaps made some problems), but even then, lots of Busybox things don't work.

I.e.:

Quoted 7 lines
# ./busybox
(...)
Currently defined functions:
        ash, cat, mount, sh, sleep, switch_root, umount, whoami
# ./busybox ash
Illegal instruction

what CPU did you select? ISTR that i have fixed this for iWMMXT && EABI

#6 lore raw
Quoted 12 lines · Bernhard Reutner-Fischer
Quoted 10 lines · Tomasz Chmielewski

OK, it builds (I had a custom uClibc config, which perhaps made some problems), but even then, lots of Busybox things don't work.

I.e.:

# ./busybox
(...)
Currently defined functions:
        ash, cat, mount, sh, sleep, switch_root, umount, whoami
Quoted 4 lines
Quoted 2 lines
# ./busybox ash
Illegal instruction

what CPU did you select? ISTR that i have fixed this for iWMMXT && EABI

xscale.

Signature · 2 lines
Tomasz Chmielewski
http://wpkg.org
#7 lore raw
In reply to Bernhard Reutner-Fischer
Quoted 12 lines · Bernhard Reutner-Fischer
Quoted 10 lines · Tomasz Chmielewski

OK, it builds (I had a custom uClibc config, which perhaps made some problems), but even then, lots of Busybox things don't work.

I.e.:

# ./busybox
(...)
Currently defined functions:
        ash, cat, mount, sh, sleep, switch_root, umount, whoami
Quoted 4 lines
Quoted 2 lines
# ./busybox ash
Illegal instruction

what CPU did you select? ISTR that i have fixed this for iWMMXT && EABI

BTW, could you point which changes you did to fix this issue for iWMMXT && EABI?

Signature · 2 lines
Tomasz Chmielewski
http://wpkg.org
#8 lore raw
Quoted 6 lines · Tomasz Chmielewski
Quoted 1 line · Bernhard Reutner-Fischer

what CPU did you select? ISTR that i have fixed this for iWMMXT && EABI

BTW, could you point which changes you did to fix this issue for iWMMXT && EABI?

aa42116fd34890d8765e126e11e1466e4f91874f
and
f3ddcec9cb2e6fa27955f3fef11092bebdd6a04b

xscale is supposed to work just fine here.

#9 lore raw
Quoted 10 lines · Bernhard Reutner-Fischer
Quoted 5 lines · Tomasz Chmielewski
Quoted 1 line · Bernhard Reutner-Fischer

what CPU did you select? ISTR that i have fixed this for iWMMXT && EABI

BTW, could you point which changes you did to fix this issue for iWMMXT && EABI?

aa42116fd34890d8765e126e11e1466e4f91874f
and
f3ddcec9cb2e6fa27955f3fef11092bebdd6a04b

I'm not very familiar with buildroot's versioning - how can I find those changes?

Quoted 1 line

xscale is supposed to work just fine here.

Well, it doesn't :(

Signature · 2 lines
Tomasz Chmielewski
http://wpkg.org
#10 lore raw
In reply to Bernhard Reutner-Fischer
Quoted 4 lines · Bernhard Reutner-Fischer
Quoted 3 lines · Tomasz Chmielewski
Quoted 1 line · Bernhard Reutner-Fischer

what CPU did you select? ISTR that i have fixed this for iWMMXT && EABI

Quoted 8 lines
Quoted 2 lines

BTW, could you point which changes you did to fix this issue for iWMMXT && EABI?

aa42116fd34890d8765e126e11e1466e4f91874f
and
f3ddcec9cb2e6fa27955f3fef11092bebdd6a04b

xscale is supposed to work just fine here.

Out of all shels, only hush and lush work:

# ./busybox
(...)
Currently defined functions:
         ash, cat, hush, lash, mount, msh, sh, sleep, switch_root, 
umount, whoami
# ./busybox ash
Illegal instruction
# ./busybox hush
/tmp # exit
# ./busybox lash
/tmp # exit
# ./busybox msh
# Illegal instruction
# ./busybox sh
Illegal instruction

Hopefully hush is enough ;)

Signature · 2 lines
Tomasz Chmielewski
http://wpkg.org
#11 lore raw

Tomasz Chmielewski schrieb:

(...)

Quoted 21 lines

Out of all shels, only hush and lush work:

# ./busybox
(...)
Currently defined functions:
         ash, cat, hush, lash, mount, msh, sh, sleep, switch_root, 
umount, whoami
# ./busybox ash
Illegal instruction
# ./busybox hush
/tmp # exit
# ./busybox lash
/tmp # exit
# ./busybox msh
# Illegal instruction
# ./busybox sh
Illegal instruction
Quoted 1 line

Hopefully hush is enough ;)

Unfortunately, it breaks, too:

# ./busybox hush
/tmp # BLAH=1
/tmp # if [ $BLAH == 1 ] ; then
Quoted 2 lines

./busybox whoami
fi

Illegal instruction

Signature · 2 lines
Tomasz Chmielewski
http://wpkg.org
#12 lore raw
In reply to Tomasz Chmielewski
Quoted 7 lines · Tomasz Chmielewski
Quoted 6 lines · Bernhard Reutner-Fischer
Quoted 5 lines · Tomasz Chmielewski
Quoted 4 lines · Bernhard Reutner-Fischer
Quoted 2 lines · Tomasz Chmielewski

So my question - did anyone manage to build ARM EABI toolchain with buildroot (GCC 4.3.1 + uClibc; I also need busybox)?

Quoted 7 lines
Quoted 4 lines
Quoted 2 lines
Quoted 1 line

Built fine for me last time i tried.

Do you still have it anywhere?

Unfortunately i've lost the disk that contained the configs, but going off a minimal config should work fine.

OK, it builds (I had a custom uClibc config, which perhaps made some problems), but even then, lots of Busybox things don't work.

BTW, I know why it initially failed for me - I removed networking support in uClibc configuration, which resulted in:

CC libpthread/linuxthreads.old/pthread.oS
STRIP -x -R .note -R .comment libpthread/linuxthreads.old/libpthread_so.a
AR cr libpthread/linuxthreads.old/libpthread_so.a
LD libpthread-0.9.29.so
libpthread/linuxthreads.old/libpthread_so.a(wrapsyscall.os): In function `sendto':
wrapsyscall.c:(.text+0x44): undefined reference to __libc_sendto' libpthread/linuxthreads.old/libpthread_so.a(wrapsyscall.os): In function sendmsg':
wrapsyscall.c:(.text+0x90): undefined reference to __libc_sendmsg' libpthread/linuxthreads.old/libpthread_so.a(wrapsyscall.os): In function send':
wrapsyscall.c:(.text+0xe4): undefined reference to __libc_send' libpthread/linuxthreads.old/libpthread_so.a(wrapsyscall.os): In function recvmsg':
wrapsyscall.c:(.text+0x130): undefined reference to __libc_recvmsg' libpthread/linuxthreads.old/libpthread_so.a(wrapsyscall.os): In function recvfrom':
wrapsyscall.c:(.text+0x194): undefined reference to __libc_recvfrom' libpthread/linuxthreads.old/libpthread_so.a(wrapsyscall.os): In function recv':
wrapsyscall.c:(.text+0x1e8): undefined reference to __libc_recv' libpthread/linuxthreads.old/libpthread_so.a(wrapsyscall.os): In function connect':
wrapsyscall.c:(.text+0x234): undefined reference to __libc_connect' libpthread/linuxthreads.old/libpthread_so.a(wrapsyscall.os): In function accept':
wrapsyscall.c:(.text+0x280): undefined reference to `__libc_accept'
collect2: ld returned 1 exit status
make[1]: *** [lib/libpthread.so] Error 1
make[1]: Leaving directory `/home/build/buildroot/buildroot-arm-gcc-4.3.1-EABI/toolchain_build_arm/uClibc'
make: *** [/home/build/buildroot/buildroot-arm-gcc-4.3.1-EABI/toolchain_build_arm/uClibc/lib/libc.a] Error 2

Signature · 2 lines
Tomasz Chmielewski
http://wpkg.org
#13 lore raw
Quoted 1 line · Tomasz Chmielewski

BTW, I know why it initially failed for me - I removed networking support in uClibc configuration, which resulted in:

well yes, that's somewhat expected :) I usually do not do threads. If you need threads, you should at least turn on socket support for obvious reasons.

Quoted 26 lines

CC libpthread/linuxthreads.old/pthread.oS
STRIP -x -R .note -R .comment libpthread/linuxthreads.old/libpthread_so.a
AR cr libpthread/linuxthreads.old/libpthread_so.a
LD libpthread-0.9.29.so
libpthread/linuxthreads.old/libpthread_so.a(wrapsyscall.os): In function `sendto':
wrapsyscall.c:(.text+0x44): undefined reference to __libc_sendto' libpthread/linuxthreads.old/libpthread_so.a(wrapsyscall.os): In function sendmsg':
wrapsyscall.c:(.text+0x90): undefined reference to __libc_sendmsg' libpthread/linuxthreads.old/libpthread_so.a(wrapsyscall.os): In function send':
wrapsyscall.c:(.text+0xe4): undefined reference to __libc_send' libpthread/linuxthreads.old/libpthread_so.a(wrapsyscall.os): In function recvmsg':
wrapsyscall.c:(.text+0x130): undefined reference to __libc_recvmsg' libpthread/linuxthreads.old/libpthread_so.a(wrapsyscall.os): In function recvfrom':
wrapsyscall.c:(.text+0x194): undefined reference to __libc_recvfrom' libpthread/linuxthreads.old/libpthread_so.a(wrapsyscall.os): In function recv':
wrapsyscall.c:(.text+0x1e8): undefined reference to __libc_recv' libpthread/linuxthreads.old/libpthread_so.a(wrapsyscall.os): In function connect':
wrapsyscall.c:(.text+0x234): undefined reference to __libc_connect' libpthread/linuxthreads.old/libpthread_so.a(wrapsyscall.os): In function accept':
wrapsyscall.c:(.text+0x280): undefined reference to `__libc_accept'
collect2: ld returned 1 exit status
make[1]: *** [lib/libpthread.so] Error 1
make[1]: Leaving directory `/home/build/buildroot/buildroot-arm-gcc-4.3.1-EABI/toolchain_build_arm/uClibc'
make: *** [/home/build/buildroot/buildroot-arm-gcc-4.3.1-EABI/toolchain_build_arm/uClibc/lib/libc.a] Error 2