slugos/nslu2le/binutils build: fail

slugos/nslu2le/binutils build: fail

[Frans Meulenbroeks]

I was asked to give slugos as spin on the autobuilder, and as slugos
still occupies a sweet spot in me I gave it a spin.
Unfoprtunately things did not build:

distro: slugos
machine: nslu2le
bitbake target: binutils
libc: glibc.

Failure is in building glibc.c:

| /home/hudson/jobs/FM_test/workspace/tmp/work/armv5te-linux-gnueabi/glibc-2.10.1-r36.1/build-arm-linux-gnueabi/libc_pic.os:
In function `faccessat':
| find_exidx.c:(.text+0x900e8): undefined reference to `fstatat64'
| collect2: ld returned 1 exit status
| make[1]: *** [/home/hudson/jobs/FM_test/workspace/tmp/work/armv5te-linux-gnueabi/glibc-2.10.1-r36.1/build-arm-linux-gnueabi/libc.so]
Error 1
| make[1]: Leaving directory
`/home/hudson/jobs/FM_test/workspace/tmp/work/armv5te-linux-gnueabi/glibc-2.10.1-r36.1/glibc-2.10.1'
| make: *** [all] Error 2
| FATAL: oe_runmake failed
NOTE: package glibc-2.10.1-r36.1: task do_compile: Failed

I can imagine this has something to do with kernel headers, but didn't
investigate.

Frans

Re: slugos/nslu2le/binutils build: fail

[Khem Raj]

On Thu, Sep 9, 2010 at 2:42 AM, Frans Meulenbroeks
<fransmeulenbroeks@gmail.com> wrote:
> I was asked to give slugos as spin on the autobuilder, and as slugos
> still occupies a sweet spot in me I gave it a spin.
> Unfoprtunately things did not build:
>
> distro: slugos
> machine: nslu2le
> bitbake target: binutils
> libc: glibc.

as I can see slugos uses eglibc 2.11 is there any special reason you
chose glibc 2.10 ?
I would suggest to try the defaults and subject of this email is wrong.

>
> Failure is in building glibc.c:
>
> | /home/hudson/jobs/FM_test/workspace/tmp/work/armv5te-linux-gnueabi/glibc-2.10.1-r36.1/build-arm-linux-gnueabi/libc_pic.os:
> In function `faccessat':
> | find_exidx.c:(.text+0x900e8): undefined reference to `fstatat64'
> | collect2: ld returned 1 exit status
> | make[1]: *** [/home/hudson/jobs/FM_test/workspace/tmp/work/armv5te-linux-gnueabi/glibc-2.10.1-r36.1/build-arm-linux-gnueabi/libc.so]
> Error 1
> | make[1]: Leaving directory
> `/home/hudson/jobs/FM_test/workspace/tmp/work/armv5te-linux-gnueabi/glibc-2.10.1-r36.1/glibc-2.10.1'
> | make: *** [all] Error 2
> | FATAL: oe_runmake failed
> NOTE: package glibc-2.10.1-r36.1: task do_compile: Failed
>
> I can imagine this has something to do with kernel headers, but didn't
> investigate.
>
> Frans
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>



-- 
-Khem

Re: slugos/nslu2le/binutils build: fail

[Frans Meulenbroeks]

2010/9/9 Khem Raj <raj.khem@gmail.com>:
> On Thu, Sep 9, 2010 at 2:42 AM, Frans Meulenbroeks
> <fransmeulenbroeks@gmail.com> wrote:
>> I was asked to give slugos as spin on the autobuilder, and as slugos
>> still occupies a sweet spot in me I gave it a spin.
>> Unfoprtunately things did not build:
>>
>> distro: slugos
>> machine: nslu2le
>> bitbake target: binutils
>> libc: glibc.
>
> as I can see slugos uses eglibc 2.11 is there any special reason you
> chose glibc 2.10 ?
> I would suggest to try the defaults and subject of this email is wrong.
>

Yes sorry the subject could have been better. binutils was the target
recipe that I build not the failing one.
Wrt glibc: the reason for using it is very simple. I didn't know how
to set LIBC, so I just asked the person who asked me to give slugos a
try, and he said slugos used glibc, not eglibc.
I didn't really verify this, but took it for granted.

I'll try with eglibc.

Frans