|
From: | Gary V. Vaughan |
Subject: | Re: Documentation of lib$package.a? |
Date: | Thu, 31 Jan 2013 08:27:11 +0700 |
Hi Reuben, On 31 Jan 2013, at 00:37, Reuben Thomas <address@hidden> wrote:
Then, may I humbly suggest you switch to my bootstrap rewrite, which has behaviour the two of us at least are considerably more familiar with?
That seems entirely wrong to me. If I have a package, say GNU m4, then libm4 is a library built and installed by my package. Why on earth would I want gnulib to stomp all over my namespace? At least there is a straight forward work around: In your gnulib bootstrap using package, always set: gnulib_name=libgnu
Agreed, I missed that, sorry. It seems like a simple oversight though, and I'm sure a patch would be welcome. Adding something along the lines of the following after line 5500 or so of gnulib-tool should do the trick: echo echo "You will need to ensure any libraries or programs that may use entry points" echo "from $libname.$libext are linked against it correctly by adding $libname.$libext" echo "to <program>_LDADD or <library>_a_LDFLAGS or <library>_la_LDFLAGS as" echo "appropriate." Cheers, -- Gary V. Vaughan (gary AT gnu DOT org) |
[Prev in Thread] | Current Thread | [Next in Thread] |