On Wed, Feb 02, 2000 at 10:53:49AM -0500, Jim Bloom wrote:
> Ruslan Ermilov wrote:
> > 
> > On Tue, Feb 01, 2000 at 02:51:11PM -0500, Jim Bloom wrote:
> > > I did the following and it worked for me:
> > >
> > >       cd /usr/src
> > >       make buildworld
> > >       make installworld
> > >       cd /usr/src/usr.bin/xinstall
> > >       make install
> > >       cd /usr/src
> > >       make installworld
> > >
> > > The first make installworld terminates with an errors, but the second on
> > > goes through.
> > >
> > It can't be true!
> 
> Nope, I'm pretty sure that is exactly what I did.
> 
> > 
> > After the first `make installworld' fails, we will have:
> > 1) a new `libutil' without string_to_flags()
> > 2) an old `libc' without setflags()
> > 3) an old /usr/bin/install with string_to_flags() linked against libutil.
> 
> I believe the new libc has been installed as well.  My first
> installworld got an error while trying to install rcp.  I believe this
> is the first program that uses any flags to install.  Once you get to
> this point, all of the libraries have been installed.
> 
Yeah, just figured this myself, but one thing I still don't understand
is how the new libc.so.4 gets installed on the first pass?  The problem
is that it is declared as PRECIOUSLIB in libc/Makefile, this will result
in -fschg passed to install.  Do you have a log from the first failed
installworld?

> I believe there is lazy resolution of the library symbols at run time. 
> They are not checked until they are actually referenced, not when the
> program starts executing.  They are first checked when ln is run, but
> that used consistent versions of the libraries for both version of
> install. 
> 
True, my apologies.

-- 
Ruslan Ermilov          Sysadmin and DBA of the
[EMAIL PROTECTED]        United Commercial Bank,
[EMAIL PROTECTED]          FreeBSD committer,
+380.652.247.647        Simferopol, Ukraine

http://www.FreeBSD.org  The Power To Serve
http://www.oracle.com   Enabling The Information Age


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

Reply via email to