On 24-Mar-00 Jordan K. Hubbard wrote:
>> Hmph, it seems sysinstall (and thus make release) is broken in -current:
> 
> I don't know what version of sysinstall you're using, but it builds just
> fine for me under -current.  I saw some other kvetching about kget
> being broken and just tried building it last night.  Observe:
> 
> root@zippy-> make
> Warning: Object directory not changed from original /usr/src/release/sysinstall
> cc -O -pipe -Wall -I/usr/src/release/sysinstall/../../gnu/lib/libdialog 
>-I/usr/src/release/sysinstall
> -I/usr/src/release/sysinstall/../../sys   -c kget.c
> cc -O -pipe -Wall -I/usr/src/release/sysinstall/../../gnu/lib/libdialog 
>-I/usr/src/release/sysinstall
> -I/usr/src/release/sysinstall/../../sys    -static -o sysinstall anonFTP.o cdrom.o 
>command.o config.o
> devices.o dhcp.o kget.o disks.o dispatch.o dist.o dmenu.o doc.o dos.o floppy.o ftp.o 
>globals.o http.o
> index.o install.o installUpgrade.o keymap.o label.o lndir.o main.o makedevs.o 
>media.o menus.o misc.o
> mouse.o msg.o network.o nfs.o options.o package.o pccard.o system.o tape.o tcpip.o 
>termcap.o ufs.o use
> r.o 
> variable.o wizard.o  -ldialog -lncurses -lmytinfo -lutil -ldisk -lftpio
> root@zippy-> uname -a
> FreeBSD zippy.cdrom.com 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Wed Mar 15 13:05:47 PST 
>2000    
> [EMAIL PROTECTED]:/usr/src/sys/compile/ZIPPY  i386

That's because your -current is too old:

revision 1.178
date: 2000/03/19 12:57:49;  author: peter;  state: Exp;  lines: +102 -108
Completely decouple userconfig from 'struct isa_device' and friends.
Userconfig was only using this for convenience since newbus, and even
then it was rather inconvenient.

That's the commit that broke it.  And its dated 4 days after your kernel. :)

> - Jordan

-- 

John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/


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

Reply via email to