Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 19 Feb 2001 10:34:26 -0700
From:      Warner Losh <imp@harmony.village.org>
To:        Stephen McKay <mckay@freebsd.org>
Cc:        arch@freebsd.org
Subject:   Re: The whole libc thing. 
Message-ID:  <200102191734.f1JHYQW61198@harmony.village.org>
In-Reply-To: Your message of "Mon, 19 Feb 2001 22:17:49 %2B1000." <200102191217.f1JCHno13825@dungeon.home> 
References:  <200102191217.f1JCHno13825@dungeon.home>  <20010216161948.B70642@gsmx07.alcatel.com.au> <200102160225.f1G2PFw09227@hak.lan.Awfulhak.org> <200102160317.f1G3HqE26659@billy-club.village.org> <200102170638.f1H6ckW84622@harmony.village.org> 

next in thread | previous in thread | raw e-mail | index | archive | help
In message <200102191217.f1JCHno13825@dungeon.home> Stephen McKay writes:
: >Case 3.  I've installed a port that installs libfred.so.3 from 4.2
: >release.  It contains __sF references.  I have a binary (say barney)
: >that links libfred.so.3 and libc.so.4.  Things work now.  I rebuild
: >the world.  Things still work because neither of the above has
: >changed.  Now let's say I want to build wilma that depends on libfred.
: >When wilma is built, it will fail to run because it links against
: >libfred.so.3 and libc.so.5.20010220.  This libc doesn't have __sF, so
: >it will fail at link time or run time.  This is easy to fix.  Just
: >rebuild the port tht produced libfred.so.3.  A new libfred.so.3 is
: >installed.  wilma will now run (maybe after being rebuilt).  barney
: >will also still run because it gets all the symbols it needs
: >(including the new libfred.so.3).
: 
: Doesn't barney die due to unresolved references to __stdout (etc) from
: the recompiled libfred.so.3?  It only has the old libc.so.4 to help it.
: Or are you proposing to regenerate all libc.so.* back to the ELF
: transition?  I am still confused, and still concerned, and still
: think a global major version bump is unavoidable.

I am saying that we regenerate libc.so.[34].  barney then wouldn't die
from the missing symbol and life would be good, assuming that no
macros used _up, which I'm nearly positive none do.  We've added
symbols like this in the past for various reasons, but maybe never so
late in the 3.x branch.  We also have the technology to regenerate the
libc.so.[34] in place if we needed to w/o recompiling,  but polishing
it for the great masses will take some time.

After talking with Peter on IRC extensively about this, I think that
we need a bigger window where we generate __stdout before trying to
take the plunge.  There are still too many libraries that depend on
__sF.

Warner


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200102191734.f1JHYQW61198>