*BSD News Article 98340


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.cs.su.oz.au!metro!metro!munnari.OZ.AU!news.Hawaii.Edu!news.caldera.com!enews.sgi.com!nntprelay.mathworks.com!howland.erols.net!news-peer.gsl.net!news.he.net!cnn.nas.nasa.gov!not-for-mail
From: Hugh LaMaster <lamaster@nas.nasa.gov>
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: problem doing "make world" after CVSup to 2.2.2
Date: Mon, 23 Jun 1997 13:10:36 -0700
Organization: NASA Ames Research Center
Lines: 79
Message-ID: <33AED83C.15FB@nas.nasa.gov>
References: <RHUFF.97Jun20180653@shell1.cybercom.net>
	    <33AB39AB.41C6@nas.nasa.gov> <5oloel$bhp@ui-gate.utell.co.uk> <5olsan$c8n@ui-gate.utell.co.uk>
NNTP-Posting-Host: win144.nas.nasa.gov
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 3.0 (X11; U; IRIX 6.2 IP22)
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:43421

Brian Somers wrote:
> 
> Did I post this ?  I meant to say that there shouldn't
> be any problems building ls.  Hugh, what problems did
> you have ?  Perhaps your source is "unclean" ?

> >       Hugh LaMaster <lamaster@nas.nasa.gov> writes:

> >> However, you may (or may not?) also have a problem
> >> with compiling ls (in /usr/src/bin/ls).   ...

OK, first of all, when I wrote that, I thought I was
upgrading to 2.2.2-current, when, after I completed 
the install, I discovered it was 3.0-current.  :-)
Shows how much I know.  Surprisingly, considering
my confusion, the system is running just fine.

Since I am kind of flying blind, the probability of pilot error
in my case is extremely large.  Hence, I don't want to waste
anyone's time, but, when I did the CVSup upgrade from 2.2.1
to FreeBSD-current, I found first of all that I couldn't build 
a new kernel because the assembler couldn't understand some new
stuff, used in some new code somewhere.  So, I got brave and did
a make world, and, it broke right away.  At this point,
I contemplated doing a clean install, but instead tried
to patch the source that broke.  In /usr/src/bin/ls/stat_flags.c,
I had to insert the following after #include <sys/stat.h>,
for reasons I was unable to explain from looking at the 
headers:


#ifndef UF_NOUNLINK
#define UF_NOUNLINK     0x00000010    /* file may not be removed or
renamed */
#endif
 
#ifndef SF_NOUNLINK
#define SF_NOUNLINK     0x00100000    /* file may not be removed or
renamed */
#endif
 
Then, the "make world" completed after about three hours,
I built a new kernel, fixed the SB16 PnP config again,
patched pnp.c, built a new kernel, and the soundcard
worked again. 

The problem with stat_flags.c may be purely a temporary 
upgrade thing, I don't know, since I am doing some other
upgrade stuff and haven't gotten back to removing the
"patch" and seeing if it compiles without the patch.  
Probably, the glitches I experienced were related to 
(inadvertently) upgrading by a larger increment than 
I originally intended.  

--

BTW, what is the "correct" way to install local patches 
in a CVSup world?

---

Also, I find the sound quality from the SB16 PnP is not
too good when accessing it from "vat".  Since I think 
some people were satisfied with it once upon a time under 
FreeBSD 2.1.5 (I never ran under 2.1.5, so I can't compare),
I'm wondering if anyone knows why or whether anyone is
working on bringing the driver up to snuff (unfortunately,
I know next-to-nothing about the SB16 and sound(cards), or
I would work on it myself).



-- 
  Hugh LaMaster, M/S 258-5,     ASCII Email: 
hlamaster@mail.arc.nasa.gov
  NASA Ames Research Center     Or:           lamaster@nas.nasa.gov
  Moffett Field, CA 94035-1000  No Junkmail:  USC 18 section 2701
  Phone:  415/604-1056          Disclaimer:   Unofficial, personal
*opinion*.