If memory serves me right, Ruslan Ermilov wrote:
> 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 o
> n
> > > > 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?
This is my first attempt at building world (starting from the 20000127
snapshot, then cvsup-ing src-all and cvs-crypto this morning, California
time), but I had a slightly different experience.
make buildworld completed without errors, then I did a make
installworld which failed (no setflags) when trying to install
libcrypto. I did a make -k installworld, which of course finished, but
the make installworld I did afterwards (no -k) failed in the same place.
After having read through the last few messages on -current, I went to
the source directory for libc and tried doing a make install there. It
failed (also because of a lack of setflags). Then I went to the obj
directory for libc and executed the install command for libc manually
(but without the -fschg argument):
install -c -o root -g wheel -m 444 libc.so.4 /usr/lib
A make installworld just finished without errors.
Hopefully this is useful information, and won't add to any of the
confusion.
Bruce.
(who's now wishing he kept slightly better written records of
what he's doing)
PGP signature
