1 |
On Sat, 30 May 2015 14:54:42 -0400 |
2 |
Mike Frysinger <vapier@g.o> wrote: |
3 |
|
4 |
> an example warning message: |
5 |
> * QA Notice: The following files were not built with LFS support: |
6 |
> * Please file a bug at http://bugs.gentoo.org/ and mark it as a |
7 |
> blocker of 471102. |
8 |
> * See that tracker bug (https://bugs.gentoo.org/471102) for more |
9 |
> details. |
10 |
> * fopen@@GLIBC_2.1 bin/route |
11 |
> * fopen@@GLIBC_2.1 bin/ifconfig |
12 |
> * fopen@@GLIBC_2.1 bin/hostname |
13 |
> * |
14 |
> __fxstat@@GLIBC_2.0,open@@GLIBC_2.0,fopen@@GLIBC_2.1,readdir@@GLIBC_2.0 |
15 |
> bin/netstat |
16 |
> * fopen@@GLIBC_2.1 sbin/nameif |
17 |
> * fopen@@GLIBC_2.1 sbin/ipmaddr |
18 |
> * fopen@@GLIBC_2.1 sbin/arp |
19 |
> * fopen@@GLIBC_2.1 sbin/iptunnel |
20 |
> * fopen@@GLIBC_2.1 sbin/rarp |
21 |
> * open@@GLIBC_2.0,creat@@GLIBC_2.0,fopen@@GLIBC_2.1 sbin/slattach |
22 |
|
23 |
|
24 |
nice, but can't we add the lfs flags to our default toolchain flags or |
25 |
even better patch glibc headers to always redefine these functions to |
26 |
the 64bits variants? |
27 |
|
28 |
I don't understand why one should add append-lfs-flags to almost every |
29 |
single package out there. Freebsd has been doing this since version 7. |
30 |
And even dropped the 32bits symbols when going to libc.so.7 I think. |
31 |
|
32 |
Some packages might break with such a change, but they're already |
33 |
half-broken according to your e-mail, so those are the ones that should |
34 |
be fixed. |
35 |
|
36 |
|
37 |
Alexis. |