Date: Wed, 30 Oct 2002 08:11:34 +0000 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: freebsd-questions@FreeBSD.ORG Subject: Re: make buildworld fails Message-ID: <20021030081134.GA49354@happy-idiot-talk.infracaninophi> In-Reply-To: <20021029192615.69e3bb31.cpressey@catseye.mb.ca> References: <20021029033143.7c01a0b7.cpressey@catseye.mb.ca> <20021029112907.GB4480@happy-idiot-talk.infracaninophi> <20021029064730.2637b4e2.cpressey@catseye.mb.ca> <20021029142839.GF4480@happy-idiot-talk.infracaninophi> <20021029192615.69e3bb31.cpressey@catseye.mb.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Oct 29, 2002 at 07:26:15PM -0600, Chris Pressey wrote:
> Unfortunately, no luck there. No Makefile-type files were updated. So, I
> toasted my *entire* source tree (including the 'checkouts' files) and
> grabbed it all anew, tried rebuilding the world... and got the same error.
Well, I'm fresh out of ideas about what's wrong.
> So I added /usr/src/include to the start of my C_INCLUDE_PATH and tried it
> again. It seemed to work better - it got over the place where the glob.h
> error occurred - but now it stops with:
The C_INCLUDE_PATH environment variable is not something that I've
ever seen mentioned in the context of 'make buildworld'. It should
all work perfectly well with that variable unset. In fact, looking at
the 'Environment Variables' node in the gcc.info pages, other than the
locale settings LC_* and TMPDIR I think that all of those
env. variables should be left unset for best results.
However, that's just the theory. It may well work in practice.
> cc -O -pipe -I/usr/src/secure/libexec/sftp-server/../../../crypto/openssh
> -DNO_IDEA -o sftp-server sftp-server.o sftp-common.o -lssh -lcrypto
> /usr/obj/usr/src/i386/usr/lib/libssh.so: undefined reference to
> `readpassphrase'
> *** Error code 1
I think it's worth trying NO_OPENSSH=true in /etc/make.conf together
with your C_INCLUDE_PATH thing to see if you can get to the end of the
buildworld process. If you can get the rest of the system up to
4.7-STABLE, you should have no trouble compiling normally. Means two
buildworld cycles to get everything up to date, I'm afraid.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks
Savill Way
Marlow
Tel: +44 1628 476614 Bucks., SL7 1TH UK
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021030081134.GA49354>