Russ Allbery wrote:
Roumen Petrov <[EMAIL PROTECTED]> writes:
Russ Allbery wrote:
Debian's experience to date is that --as-needed is buggy and breaks a
lot of software, and overall is not a particularly stable solution.
Removing *.la files so that the unneeded shared libraries aren't linked
i
On Sat, Nov 8, 2008 at 7:00 AM, Roumen Petrov
<[EMAIL PROTECTED]> wrote:
> Russ Allbery wrote:
>>
>> Roumen Petrov <[EMAIL PROTECTED]> writes:
>>>
>>> Russ Allbery wrote:
>>
Debian's experience to date is that --as-needed is buggy and breaks a
lot of software, and overall is not a particu
[SNIP]
But problem is not in the libtool.
Yes it is. If you're linking to libfoo, libtool reads libfoo.la and
adds direct links to everything in dependency_libs. Let's say libfoo
depends on libbar and libbaz. You're application ends up directly
linking to libfoo, libbar and libbaz instead of ju
On Sat, Nov 8, 2008 at 9:22 AM, Roumen Petrov
<[EMAIL PROTECTED]> wrote:
> [SNIP]
>>>
>>> But problem is not in the libtool.
>>
>> Yes it is. If you're linking to libfoo, libtool reads libfoo.la and
>> adds direct links to everything in dependency_libs. Let's say libfoo
>> depends on libbar and lib
Roumen Petrov <[EMAIL PROTECTED]> writes:
> Russ Allbery wrote:
>> When you create a libtool library, libtool records every library
>> against which that library was linked into the *.la file. If you then
>> link another shared library against that shared library using libtool,
>> libtool reads t
Russ Allbery wrote:
Roumen Petrov <[EMAIL PROTECTED]> writes:
Russ Allbery wrote:
When you create a libtool library, libtool records every library
against which that library was linked into the *.la file. If you then
link another shared library against that shared library using libtool,
libt
Dan Nicholson wrote:
On Sat, Nov 8, 2008 at 9:22 AM, Roumen Petrov
<[EMAIL PROTECTED]> wrote:
[SNIP]
But problem is not in the libtool.
Yes it is. If you're linking to libfoo, libtool reads libfoo.la and
adds direct links to everything in dependency_libs. Let's say libfoo
depends on libbar and
Roumen Petrov <[EMAIL PROTECTED]> writes:
> It was old build bug when building readline library on some linux-es. In
> my memory is suse 7.1 but I'm sure that only this particular version was
> affected.
> Many other linux verdors build readline without dependent libraries and
> this allow applic
Russ Allbery wrote:
Roumen Petrov <[EMAIL PROTECTED]> writes:
It was old build bug when building readline library on some linux-es. In
my memory is suse 7.1 but I'm sure that only this particular version was
affected.
Many other linux verdors build readline without dependent libraries and
th
Roumen Petrov <[EMAIL PROTECTED]> writes:
> Russ Allbery wrote:
>> libreadline is linked against libncurses on Debian.
> Which version ?
readline 5.2-3, ncurses 5.7-2.
> This is an 7(5?) years old linux bug.
I'm very dubious of that assertion. Applications which use readline but
do not direct
Russ Allbery wrote:
Roumen Petrov <[EMAIL PROTECTED]> writes:
Russ Allbery wrote:
libreadline is linked against libncurses on Debian.
Which version ?
readline 5.2-3, ncurses 5.7-2.
No,no debian version/release.
This is an 7(5?) years old linux bug.
I'm very dubious of that asserti
I feel like today I just watched the movie "Groundhog Day" another 20
times. This topic re-emerges just as often as the one about whether
list replies should default to the original sender, or to the list.
It seems that there is an issue for Linux distribution maintainers.
What needs to be do
On Sat, 8 Nov 2008, Russ Allbery wrote:
pkg-config supports having separate dependency lists for static linking
and shared linking, which seems to adequately address this problem (if
that feature is actually used; the documentation last I looked was a bit
lacking and a lot of pkg-config *.pc pro
Bob Friesenhahn <[EMAIL PROTECTED]> writes:
> Quite a lot can known from .la files but it is apparent that .la files
> are now spontaneously deleted.
Hm, I must admit that I generally find them useless compared to reading
readelf -a output, but I'm not the normal user. :)
> It is really quite a
Bob Friesenhahn <[EMAIL PROTECTED]> writes:
> It seems that there is an issue for Linux distribution maintainers. What
> needs to be done about it so that this topic does not come up so often?
Well, my preference would be to implement the change to libtool described
in my previous message, but si
Roumen Petrov wrote:
> Linking readline against ncurses prevent application to link against
> readline against ncursesw and to offer wide characters support.
Note that this is only even possible on a system with lazy binding. For
windows, shared libraries cannot have any undefined symbols at link
16 matches
Mail list logo
