| 1 |
On 08-08-2008 14:07:08 +0200, Michael Haubenwallner wrote: |
| 2 |
> I'd say use the GNU ones if gnulib detects they're better. |
| 3 |
|
| 4 |
Ok, does that mean gnulib currently doesn't install them if the platform |
| 5 |
has "sufficiently good enough" versions? |
| 6 |
|
| 7 |
> > In other words, for those platforms which do not use elibc_glibc, why |
| 8 |
> > don't we install gnulib as part of @system, |
| 9 |
> |
| 10 |
> Yes, so there's no need to add an explicit platform specific DEPEND. |
| 11 |
|
| 12 |
Ok, but this is not the worst problem (using kernel_SunOS you can merge |
| 13 |
4 into 1 ;) ) |
| 14 |
|
| 15 |
> > and have the linker wrapper inject -lgnu? |
| 16 |
> |
| 17 |
> No (but maybe it's worth a try). |
| 18 |
> Any package that requires libgnu should activate it explicitly. |
| 19 |
> But it's fine to have some eclass function which does nothing for |
| 20 |
> elibc_glibc, and adds proper flags for others, so the activation is a |
| 21 |
> one-liner per ebuild. |
| 22 |
|
| 23 |
I thought of an eclass with function call e.g. like "gnulib strndup" |
| 24 |
which would then do the necessary magic. But this is no longer |
| 25 |
necessesary if gnulib already makes sure it doesn't do unnecessary code |
| 26 |
duplication. |
| 27 |
|
| 28 |
> Iff it is added by default, we definitely need a way to disable this, |
| 29 |
> see below. |
| 30 |
> |
| 31 |
> Question is how many packages break when it's added by default, compared |
| 32 |
> to how many packages need it. |
| 33 |
|
| 34 |
I wouldn't know what package would/could break. In the end they all |
| 35 |
"work" with GNU stuff on origin platform: Gentoo Linux. Of course the |
| 36 |
"smarter" packages always remain a problem. |
| 37 |
|
| 38 |
> Now, when -lgnu is there always, we cannot rebuild gnulib itself, as |
| 39 |
> it's configure would detect sufficient "libc", and build an empty |
| 40 |
> libgnu.a. |
| 41 |
> This is the main reason why not to add -lgnu always, or the need to |
| 42 |
> disable it. |
| 43 |
|
| 44 |
Hah, that's valid, but if that's the only thing, I'm willing to either |
| 45 |
teach the linker wrapper some neat trick, or to have -lgnu in LDFLAGS |
| 46 |
only. (and disable this stupid --as-needed warning) |
| 47 |
|
| 48 |
Maybe Portage LDFLAGS *is* the best solution, as it is definitely |
| 49 |
something you rather don't have by default if you're developing software |
| 50 |
yourself (like our users might do), but don't really care about if |
| 51 |
you're just trying to get a package compiled (like we do). |
| 52 |
|
| 53 |
|
| 54 |
-- |
| 55 |
Fabian Groffen |
| 56 |
Gentoo on a different level |
Archives