* De: David O'Brien <[EMAIL PROTECTED]> [ Data: 2002-10-31 ]
        [ Subjecte: Re: [PATCH: libc]Re: gnome on current ]
> On Wed, Oct 30, 2002 at 06:02:38PM -0800, Juli Mallett wrote:
> > Considering that I built the same applications and ran the same applications
> > fine a while ago, and we've had a binutils upgrade, and things don't break
> > on other systems, I'm inclined to assume there are linker bugs afoot, and
> > all the other speculative stuff seems to be based on misunderstandings or
> > bad information.
> 
> Huh?  Your statement is rather speculative stuff.  Other systems (say
> Linux) are using the same linker we are.  Please speculate less.  Please
> grab an older ld and try to prove your speculation.

It's deductive.  Other systems are using similar library setups, in terms
of weak vs. strong systems, and some of those are very well supported by
GNOME by a commercial vendor, or will be if not now for GNOME2.  I'm running
GNOME2 right now that was built about two weeks before the last binutils
upgrade, which had about 900 lines of ChangeLog entries associated with
it.  The symbol strength in libc and libc_r has not changed similarly in
that time.

I was just throwing my speculation based on my experiences with what is
working, trying to keep in mind what has changed in the mean time, and
what is involved with what's going on.

Which Linux distributions have the symbol strength as we do, have libXThrStub
in their link lines, -and- are using the same binutils as us?  I'm not
saying that has to be it, I'm saying given what I'm writing this reply
on/inside, I'm saying "I doubt dfr's insistance on breaking non libc_r.so
thread libraries being the only thing is seeming more and more wrong,
as I ldd every binary I'm currently running."

juli.
-- 
Juli Mallett <[EMAIL PROTECTED]>       | FreeBSD: The Power To Serve
Will break world for fulltime employment. | finger [EMAIL PROTECTED]
http://people.FreeBSD.org/~jmallett/      | Support my FreeBSD hacking!

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to