glibc failure with CT_LIBC_DISABLE_VERSIONING

glibc failure with CT_LIBC_DISABLE_VERSIONING

[Johannes Stezenbach]

Hi,

I built a uClibc toolchain and then was asked to build
the same thing with glibc.  So I chose CT_LIBC_GLIBC_V_2_14_1=y
and got this failure:

[INFO ]  Installing C library
[EXTRA]    Configuring C library
[EXTRA]    Building C library
[ERROR]    pthread_kill_other_threads.c:35:1: error: expected identifier or '(' before '...' token
[ERROR]    make[3]: *** [/home/js/pixelworks/Victoria/toolchain/tmp/build/.build/arm-unknown-linux-gnueabi/build/build-libc-final/nptl/pthread_kill_other_threads.os] Error 1

This was caused by CT_LIBC_DISABLE_VERSIONING, which causes
DO_VERSIONING to be unset when pthread_kill_other_threads.c
includes glibc-2.14.1/include/shlib-compat.h.

Is this known?  Should CT_LIBC_DISABLE_VERSIONING depend on !CT_LIBC_glibc?


BTW, I also had -Os in my CT_TARGET_CFLAGS which
causes other, apparently well-known failure with
glibc, so don't do this ;-/
(something about undefined fstatat64 IIRC)


Best Regards
Johannes

--
For unsubscribe information see http://sourceware.org/lists.html#faq

Re: glibc failure with CT_LIBC_DISABLE_VERSIONING

[Johannes Stezenbach]

On Tue, Oct 16, 2012 at 12:57:50PM +0200, Johannes Stezenbach wrote:
> 
> Is this known?  Should CT_LIBC_DISABLE_VERSIONING depend on !CT_LIBC_glibc?

It seems eglibc-1.16 also doesn't build with CT_LIBC_DISABLE_VERSIONING?  I get:

In function `_nss_files_getsecretkey':
.../.build/src/eglibc-2_16/nss/nss_files/files-key.c:103: undefined reference to `xdecrypt'

It builds fine with CT_LIBC_DISABLE_VERSIONING disabled.  Did this
work for earlier versions of eglibc?


BTW, I trying to figure out if it is possible to configure
eglibc so that small utitlities stay small when they are
statically linked.  Does someone know?
In the default config even an empty main() pulls in half
the library, ~450k stripped.


Cheers,
Johannes

--
For unsubscribe information see http://sourceware.org/lists.html#faq

Re: glibc failure with CT_LIBC_DISABLE_VERSIONING

[Florian Fainelli]

Hello Johannes,

Le 10/18/12 17:07, Johannes Stezenbach a écrit :
> On Tue, Oct 16, 2012 at 12:57:50PM +0200, Johannes Stezenbach wrote:
>>
>> Is this known?  Should CT_LIBC_DISABLE_VERSIONING depend on !CT_LIBC_glibc?
>
> It seems eglibc-1.16 also doesn't build with CT_LIBC_DISABLE_VERSIONING?  I get:
>
> In function `_nss_files_getsecretkey':
> .../.build/src/eglibc-2_16/nss/nss_files/files-key.c:103: undefined reference to `xdecrypt'
>
> It builds fine with CT_LIBC_DISABLE_VERSIONING disabled.  Did this
> work for earlier versions of eglibc?

I got the exact same build error with eglibc 2.15, I have not tried with 
earlier versions, but I suspect this bug would also be there.

Have you been able to find an upstream patch fixing this by chance?

>
>
> BTW, I trying to figure out if it is possible to configure
> eglibc so that small utitlities stay small when they are
> statically linked.  Does someone know?
> In the default config even an empty main() pulls in half
> the library, ~450k stripped.
>
>
> Cheers,
> Johannes
>
> --
> For unsubscribe information see http://sourceware.org/lists.html#faq
>

--
For unsubscribe information see http://sourceware.org/lists.html#faq

Re: glibc failure with CT_LIBC_DISABLE_VERSIONING

[Johannes Stezenbach]

Hi Florian,

On Mon, Dec 17, 2012 at 12:02:45PM +0100, Florian Fainelli wrote:
> Le 10/18/12 17:07, Johannes Stezenbach a écrit :
> >On Tue, Oct 16, 2012 at 12:57:50PM +0200, Johannes Stezenbach wrote:
> >>
> >>Is this known?  Should CT_LIBC_DISABLE_VERSIONING depend on !CT_LIBC_glibc?
> >
> >It seems eglibc-1.16 also doesn't build with CT_LIBC_DISABLE_VERSIONING?  I get:
> >
> >In function `_nss_files_getsecretkey':
> >.../.build/src/eglibc-2_16/nss/nss_files/files-key.c:103: undefined reference to `xdecrypt'
> >
> >It builds fine with CT_LIBC_DISABLE_VERSIONING disabled.  Did this
> >work for earlier versions of eglibc?
> 
> I got the exact same build error with eglibc 2.15, I have not tried
> with earlier versions, but I suspect this bug would also be there.
> 
> Have you been able to find an upstream patch fixing this by chance?

Unfortunately I was too time contrained to look into it, so I just
disabled CT_LIBC_DISABLE_VERSIONING and was done with it.

Johannes

--
For unsubscribe information see http://sourceware.org/lists.html#faq