On Wed, 5 Feb 2003 05:43:50 +0200
Giorgos Keramidas <[EMAIL PROTECTED]> wrote:

>  What is the output of:
>        % ls -ld /usr/lib/*termcap*
> ?  I think that buildworld uses stuff from /usr/obj when it can find
> it though.

I wonder about this also ^

_My_ _working_ 4.7-STABLE system reports:
mybox># ls -ld /usr/lib/*termcap*
lrwxr-xr-x  1 root  wheel  12 Jan 28 08:18 /usr/lib/libtermcap.a 
-> libncurses.a
lrwxr-xr-x  1 root  wheel  13 Jan 28 08:18 /usr/lib/libtermcap.so 
-> libncurses.so
lrwxrwxrwx  1 root  wheel  14 Dec 10 04:46 /usr/lib/libtermcap_p.a 
-> libncurses_p.a

> Another possibility for the failures that you are seeing is that you
> have spammed your /usr/src tree by running 'make' in the wrong place
> under /usr/src.

Would not the 'cd /usr/src && make cleandir && make cleandir' 
correct this, if followed by a cvsup?

>  Try updating your sources with CVSup and make sure
> your supfile includes the line:
>       *default delete use-rel-suffix
> - Giorgos

I have heard IIRC from JDP that '*default delete' is now 
prefered to using '*default delete use-rel-suffix'

The original posters cvsupfile looks like this:

*default host=cvsup.FreeBSD.org
*default base=/usr
*default prefix=/usr
*default release=cvs tag=RELENG_4_7
*default delete use-rel-suffix
*default compress

And he did buildworld to 4.7-p2 ok already

In researching this problem I came across this freebsd 
mailing list thread from 2001 regarding docs/24662 relating 
to potentially corrupted src trees from assorted end-user 
miss-steps and other reasons. It also covered some advanced 
cvsup usage, including some info that helped me understand 
the hows and whys of properly adopting your source tree. 

And came upon this little gem "cvsupchk"

An excerpt from the README is:
"cvsupchk is a python script that checks a CVSup maintained 
directory hierarchy against the corresponding CVSup checkouts 
file. It looks for a number of anomalies: missing checked out 
files, deleted files being present, extra RCS files, 'dead' 
directories being present and so on."

To get this tool:

cd /usr/ports/net/cvsup
make extract

cd ./work/cvsup-snap-16.1f/contrib/cvsupchk

And for my PC with a /usr/src directory and a 
cvsupfile with src-all selected, and an existing  
/usr/sup/src-all/checkouts file, I ran this command:

./cvsupchk -d /usr -c /usr/sup/src-all/checkouts

and found some things to look into in my src tree that 
could use some cleaning.

Why with all the questions that pop up regarding mucked 
up src directories is this tool not mentioned more?

Does it have problems, or give incorrect information? 

Is there a good article/how-to someplace that I missed?

http://www.hiltonbsd.com/articles/buildworld.php was my 
attempt last year to share my limited understanding of 
this topic, with plenty of examples :-) and I am thinking 
about giving it an update.

Not having a strong programming background sure makes 
getting a better understanding of some of these topics 
difficult. Better get that "Learn C in 24 Hours" book 
out again ;-)


Stephen Hilton

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

Reply via email to