Re: 5406 warnings during buildworld & other q's

2003-10-20 Thread Kris Kennaway
On Mon, Oct 20, 2003 at 06:38:18PM +0100, David Carter-Hitchin wrote:

> > d) installworld failed the first time as the user 'smmsp' didn't
> > exist.  I dutifully followed the advice given in UPGRADE by building
> > and running mergemaster.  Second run of installworld also failed - at
> > mergemaster, saying "Don't know how to build mergemaster.sh".  I'm not
> > sure if I did the right thing, but copying  /usr/sbin/mergemaster to the
> > source directory /usr/src/usr.sbin/mergemaster and renaming it to
> > mergemaster.sh, fixed the problem.  Can anyone comment on this?
> 
> = It looks like your buildworld didn't complete before you tried to
> = installworld it.
> 
> As far as the process is concerned it definitely completed, and I grepped
> for errors and found none in the logfile.  The last thing buidlworld
> logged was:
> 
> chmod 444 freebsd.submit.cf
> 
> Having done this for the first time, I don't know what the last line
> should be.  Does it say "buildworld complete"?

I forgot you're upgrading from an old version of FreeBSD..it could be
related to your other bootstrapping problems.

Kris


pgp0.pgp
Description: PGP signature


Re: 5406 warnings during buildworld & other q's

2003-10-20 Thread David Carter-Hitchin
Hi Kris,

Thanks for replying...  

> d) installworld failed the first time as the user 'smmsp' didn't
> exist.  I dutifully followed the advice given in UPGRADE by building
> and running mergemaster.  Second run of installworld also failed - at
> mergemaster, saying "Don't know how to build mergemaster.sh".  I'm not
> sure if I did the right thing, but copying  /usr/sbin/mergemaster to the
> source directory /usr/src/usr.sbin/mergemaster and renaming it to
> mergemaster.sh, fixed the problem.  Can anyone comment on this?

= It looks like your buildworld didn't complete before you tried to
= installworld it.

As far as the process is concerned it definitely completed, and I grepped
for errors and found none in the logfile.  The last thing buidlworld
logged was:

chmod 444 freebsd.submit.cf

Having done this for the first time, I don't know what the last line
should be.  Does it say "buildworld complete"?

> I checked the timestamp on both ld-elf.so.1 and libm.so.2 and they were
> built today - anyone know what might have caused this?  Do I need to
> rebuild cvsup, if so how?

= This is explained in UPDATING.

Ah yes... thanks.  

> Readme.html's.  Is that a bug? 

= No, you told cvsup to delete your ports collection (the ports tree is
= not branched).  This is also explained in the handbook.

DOOF! Won't be doing that again in a hurry.

Thanks,
David

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: 5406 warnings during buildworld & other q's

2003-10-18 Thread Kris Kennaway
On Sun, Oct 19, 2003 at 01:50:20AM +0100, David Carter-Hitchin wrote:
> Hi Free BSDers,
> 
> Sorry about my question overload here.
> 
> I've just successfully cvsup'd to -STABLE (I think), done a buildworld,
> installworld and rebuilt the kernel.  Everything seemed to go generally ok
> but I had a few observations/questions:
> 
> a) Firstly I had difficulty finding much information about the specific
> tag I should use in the "tag=" line in the cvsup file.

It is in the handbook, so you must have overlooked it.

> b) The first run of buildworld failed as vgrind was not on my system. I
> hunted down vgrind under /usr/src/usr.bin, built that and ran buildworld
> successfully a second time.  

You need to have a consistent system in order to build world: you
can't bootstrap from a system with some of the mandatory pieces
missing.

> c) buildworld generated 5406 warnings.  Some examples are:

Warnings are notes from the compiler to the developers.  They're
expected and can be ignored unless you want to fix them.

> d) installworld failed the first time as the user 'smmsp' didn't
> exist.  I dutifully followed the advice given in UPGRADE by building
> and running mergemaster.  Second run of installworld also failed - at
> mergemaster, saying "Don't know how to build mergemaster.sh".  I'm not
> sure if I did the right thing, but copying  /usr/sbin/mergemaster to the
> source directory /usr/src/usr.sbin/mergemaster and renaming it to
> mergemaster.sh, fixed the problem.  Can anyone comment on this?

It looks like your buildworld didn't complete before you tried to
installworld it.

> e) 'cvsup -g -L2 ports-supfile' now generates an error:
> /usr/libexec/ld-elf.so.1: /usr/lib/libm.so.2: Undefined symbol "__stderrp"
> 
> I checked the timestamp on both ld-elf.so.1 and libm.so.2 and they were
> built today - anyone know what might have caused this?  Do I need to
> rebuild cvsup, if so how?

This is explained in UPDATING.

> f) At some point (I think after doing a cvsup with "tag=RELENG_4" I lost
> all my ports files - the only files I can see under /usr/ports/*/* are
> Readme.html's.  Is that a bug?  Luckily I kept a copy of my ports tree so
> I'll use that until I can figure out e) above.  

No, you told cvsup to delete your ports collection (the ports tree is
not branched).  This is also explained in the handbook.

Kris


pgp0.pgp
Description: PGP signature