Subject: Re: 20030518 i386 build
To: David Laight <firstname.lastname@example.org>
From: Frederick Bruckman <email@example.com>
Date: 05/18/2003 11:04:09
On Sun, 18 May 2003, David Laight wrote:
> On Sun, May 18, 2003 at 07:51:33AM -0500, Frederick Bruckman wrote:
> > On Sun, 18 May 2003, John Nemeth wrote:
> > > It looks like the flists for i386 are out of date. This is the
> > > output from a 20030518 i386 build:
> > > > ./lib/libc.so.12.97
> > > 1357a1359
> > > > ./usr/include/i386/mouse.h
> > > 1916a1919
> > > > ./usr/include/sys/float_ieee.h
> > > checkflist: flist inconsistencies found
> > > checkflist: key to output:
> > > < file is in flist but missing from DESTDIR
> > > (file wasn't installed ?)
> > > > file is in DESTDIR but missing from flist
> > > (file is obsolete or flist is out of date ?)
> > > *** Error code 1
> > Those are all obsolete files. Your DESTDIR wasn't clean?
> And when you delete them (which is usually safe) you'll find that
> libstdc++ (IIRC) has a .depend file that refers to float_ieee.h
> so makes the build fail.
So remove it. You're building a release with UPDATE set? That can't
always work. Every now and then, you have to clean everything out.
> Actually I do wonder if these extra files are a problem?
> (especially after an 'update' build).
> If you build the sets, then don't their contents depend on the flists
> with permissions from METALOG (if unprived) not on DESTDIR.
> (makbe lukem knows the answer...)
Extra files in DESTDIR are a clue that there may be something wrong
with the build, such as, for example, some of the executables may be
linked against libraries that won't be present in the sets. Assuming
that the build does complete on a clean system, then the warnings
are probably harmless on yours. If you're not building a full
distribution, the file lists aren't even checked.