[Buildroot] ARM EABI toolchain - anyone build it successfully?

[Buildroot] ARM EABI toolchain - anyone build it successfully?

[Tomasz Chmielewski]

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)?


-- 
Tomasz Chmielewski
http://wpkg.org

[Buildroot] ARM EABI toolchain - anyone build it successfully?

[Bernhard Reutner-Fischer]

On Tue, Aug 19, 2008 at 05:34:42PM +0200, Tomasz Chmielewski wrote:

>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.

[Buildroot] ARM EABI toolchain - anyone build it successfully?

[Tomasz Chmielewski]

Bernhard Reutner-Fischer schrieb:
> On Tue, Aug 19, 2008 at 05:34:42PM +0200, Tomasz Chmielewski wrote:
> 
>> 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?


-- 
Tomasz Chmielewski
http://wpkg.org

[Buildroot] ARM EABI toolchain - anyone build it successfully?

[Bernhard Reutner-Fischer]

On Tue, Aug 19, 2008 at 05:54:30PM +0200, Tomasz Chmielewski wrote:
> Bernhard Reutner-Fischer schrieb:
>> On Tue, Aug 19, 2008 at 05:34:42PM +0200, Tomasz Chmielewski wrote:
>>
>>> 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.

[Buildroot] ARM EABI toolchain - anyone build it successfully?

[Tomasz Chmielewski]

Bernhard Reutner-Fischer schrieb:
> On Tue, Aug 19, 2008 at 05:54:30PM +0200, Tomasz Chmielewski wrote:
>> Bernhard Reutner-Fischer schrieb:
>>> On Tue, Aug 19, 2008 at 05:34:42PM +0200, Tomasz Chmielewski wrote:
>>>
>>>> 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).



-- 
Tomasz Chmielewski
http://wpkg.org

[Buildroot] ARM EABI toolchain - anyone build it successfully?

[Bernhard Reutner-Fischer]

On Wed, Aug 20, 2008 at 11:29:02AM +0200, Tomasz Chmielewski wrote:

> 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

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

[Buildroot] ARM EABI toolchain - anyone build it successfully?

[Tomasz Chmielewski]

Bernhard Reutner-Fischer schrieb:
> On Wed, Aug 20, 2008 at 11:29:02AM +0200, Tomasz Chmielewski wrote:
> 
>> 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
> 
> what CPU did you select? ISTR that i have fixed this for iWMMXT && EABI

xscale.


-- 
Tomasz Chmielewski
http://wpkg.org

[Buildroot] ARM EABI toolchain - anyone build it successfully?

[Tomasz Chmielewski]

Bernhard Reutner-Fischer schrieb:
> On Wed, Aug 20, 2008 at 11:29:02AM +0200, Tomasz Chmielewski wrote:
> 
>> 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
> 
> 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?


-- 
Tomasz Chmielewski
http://wpkg.org

[Buildroot] ARM EABI toolchain - anyone build it successfully?

[Bernhard Reutner-Fischer]

On Wed, Aug 20, 2008 at 12:07:18PM +0200, Tomasz Chmielewski wrote:
> Bernhard Reutner-Fischer schrieb:

>> 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.

[Buildroot] ARM EABI toolchain - anyone build it successfully?

[Tomasz Chmielewski]

Bernhard Reutner-Fischer schrieb:
> On Wed, Aug 20, 2008 at 12:07:18PM +0200, Tomasz Chmielewski wrote:
>> Bernhard Reutner-Fischer schrieb:
> 
>>> 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?


> xscale is supposed to work just fine here.

Well, it doesn't :(


-- 
Tomasz Chmielewski
http://wpkg.org

[Buildroot] ARM EABI toolchain - anyone build it successfully?

[Tomasz Chmielewski]

Bernhard Reutner-Fischer schrieb:
> On Wed, Aug 20, 2008 at 12:07:18PM +0200, Tomasz Chmielewski wrote:
>> Bernhard Reutner-Fischer schrieb:
> 
>>> 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.

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 ;)


-- 
Tomasz Chmielewski
http://wpkg.org

[Buildroot] ARM EABI toolchain - anyone build it successfully?

[Tomasz Chmielewski]

Tomasz Chmielewski schrieb:

(...)

> 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 ;)

Unfortunately, it breaks, too:

# ./busybox hush
/tmp # BLAH=1
/tmp # if [ $BLAH == 1 ] ; then
 > ./busybox whoami
 > fi
Illegal instruction


-- 
Tomasz Chmielewski
http://wpkg.org

[Buildroot] ARM EABI toolchain - anyone build it successfully?

[Tomasz Chmielewski]

Tomasz Chmielewski schrieb:
> Bernhard Reutner-Fischer schrieb:
>> On Tue, Aug 19, 2008 at 05:54:30PM +0200, Tomasz Chmielewski wrote:
>>> Bernhard Reutner-Fischer schrieb:
>>>> On Tue, Aug 19, 2008 at 05:34:42PM +0200, Tomasz Chmielewski wrote:
>>>>
>>>>> 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.

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



-- 
Tomasz Chmielewski
http://wpkg.org

[Buildroot] ARM EABI toolchain - anyone build it successfully?

[Bernhard Reutner-Fischer]

On Wed, Aug 20, 2008 at 12:00:51PM +0200, Tomasz Chmielewski wrote:

> 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.
>
>
>  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