Re: Strange make buildworld problem...
Hi I just committed a fix for this. M > Recently, the make world problems with perl have been fixed, and I can do > a make world all the way through, provided I do a make world the first > time only. However, I did a cvsup to update my source tree again after > the first make world. I did a make -DNOCLEAN buildworld with /usr/obj > untouched. I get this: > > >>> stage 2: build tools > -- > cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj INSTALL="sh > /usr/src/tools/install.sh" > PATH=/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/us r/s > rc/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin make -f Makefile.inc1 > build-tools > cd /usr/src/bin/sh; make build-tools > cd /usr/src/games/adventure; make build-tools > cd /usr/src/games/hack; make build-tools > cd /usr/src/games/phantasia; make build-tools > cd /usr/src/gnu/usr.bin/cc/cc_tools; make build-tools > cd /usr/src/gnu/usr.bin/cc/f771; make build-tools > cd /usr/src/lib/libncurses; make build-tools > cd /usr/src/share/syscons/scrnmaps; make build-tools > cd /usr/src/gnu/usr.bin/perl; make build-tools > cd /usr/src/gnu/usr.bin/perl/libperl && make build-tools > make: don't know how to make > /usr/obj/usr/src/i386/usr/include/sys/types.h. Stop > *** Error code 2 > Stop in /usr/src/gnu/usr.bin/perl. > *** Error code 1 > Stop in /usr/src. > *** Error code 1 > > Again, this is after re-making buildworld with -DNOCLEAN after a > successful first make buildworld. > > - Donn > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Strange make buildworld problem...
> On Wed, Jun 28, 2000 at 07:54:17PM -0400, Donn Miller wrote: > > make: don't know how to make > > /usr/obj/usr/src/i386/usr/include/sys/types.h. Stop > > *** Error code 2 > > This is what I got when I tried to ``make -DNOCLEAN buildworld'' after > the Perl 5.006 upgrade. Perl is being built at the wrong time, or a > dependacy is missing. This is now fixed. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Strange make buildworld problem...
On Wed, Jun 28, 2000 at 07:54:17PM -0400, Donn Miller wrote: > make: don't know how to make > /usr/obj/usr/src/i386/usr/include/sys/types.h. Stop > *** Error code 2 This is what I got when I tried to ``make -DNOCLEAN buildworld'' after the Perl 5.006 upgrade. Perl is being built at the wrong time, or a dependacy is missing. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Strange make buildworld problem...
On Wed, 28 Jun 2000 19:54:17 -0400, Donn Miller wrote: > Again, this is after re-making buildworld with -DNOCLEAN after a > successful first make buildworld. Any chance the sources changed between buildworlds? Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Strange make buildworld problem...
Recently, the make world problems with perl have been fixed, and I can do a make world all the way through, provided I do a make world the first time only. However, I did a cvsup to update my source tree again after the first make world. I did a make -DNOCLEAN buildworld with /usr/obj untouched. I get this: >>> stage 2: build tools -- cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj INSTALL="sh /usr/src/tools/install.sh" PATH=/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/s rc/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin make -f Makefile.inc1 build-tools cd /usr/src/bin/sh; make build-tools cd /usr/src/games/adventure; make build-tools cd /usr/src/games/hack; make build-tools cd /usr/src/games/phantasia; make build-tools cd /usr/src/gnu/usr.bin/cc/cc_tools; make build-tools cd /usr/src/gnu/usr.bin/cc/f771; make build-tools cd /usr/src/lib/libncurses; make build-tools cd /usr/src/share/syscons/scrnmaps; make build-tools cd /usr/src/gnu/usr.bin/perl; make build-tools cd /usr/src/gnu/usr.bin/perl/libperl && make build-tools make: don't know how to make /usr/obj/usr/src/i386/usr/include/sys/types.h. Stop *** Error code 2 Stop in /usr/src/gnu/usr.bin/perl. *** Error code 1 Stop in /usr/src. *** Error code 1 Again, this is after re-making buildworld with -DNOCLEAN after a successful first make buildworld. - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make buildworld problem...
On Fri, 29 Oct 1999 08:46:29 -0400, "Chris D. Faulhaber" wrote: > As an interim hack, would the following patch, which verifies > kern.osreldate >= 400011, suffice? I'd be in favour of this if all the changes were associated with comments containing ``XXX required for sigset_t migration''. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make buildworld problem...
"Chris D. Faulhaber" wrote: > > On Thu, 28 Oct 1999, Marcel Moolenaar wrote: > > > Peter Jeremy wrote: > > > > > > IMHO, the correct solution is to for the entire make world process to > > > be re-worked. > > > > That's what I'm currently doing. If I have a stripped down make process > > ready for public viewing, I'll let you all know. A thread on the subject > > can be found in the -arch archives. > > As an interim hack, would the following patch, which verifies > kern.osreldate >= 400011, suffice? IMO it's overkill for a one time situation that can be considered historical at this point in time :-) -- Marcel Moolenaarmailto:[EMAIL PROTECTED] SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD projectmailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make buildworld problem...
On Thu, 28 Oct 1999, Marcel Moolenaar wrote:
> Peter Jeremy wrote:
> >
> > >(/me wonders how many MORE times we are going to have to say this because
> > >of the signal changes...)
> >
> > A very large number I suspect.
> >
> > IMHO, the correct solution is to for the entire make world process to
> > be re-worked.
>
> That's what I'm currently doing. If I have a stripped down make process
> ready for public viewing, I'll let you all know. A thread on the subject
> can be found in the -arch archives.
>
As an interim hack, would the following patch, which verifies
kern.osreldate >= 400011, suffice?
Index: Makefile.inc0
===
RCS file: /home/ncvs/src/Makefile.inc0,v
retrieving revision 1.18
diff -u -r1.18 Makefile.inc0
--- Makefile.inc0 1999/08/28 01:35:58 1.18
+++ Makefile.inc0 1999/10/29 12:41:18
@@ -15,6 +15,11 @@
MAKEOBJDIRPREFIX?=/usr/obj
#
+# Check kern.osreldate to ensure kernel will support building world
+#
+OSRELDATE= `/sbin/sysctl -a | grep osreldate | awk '{ print $$2; }'`
+
+#
# Variables passed to make work better if they are set as environment
# variables instead of command line options.
#
@@ -106,6 +111,13 @@
# support if the current object format is elf on i386.
#
buildworld :
+ @if [ ${OSRELDATE} -lt "400011" ]; then \
+ echo; \
+ echo "The current kernel does not support building world. Please
+read"; \
+ echo "the 19990929 entry in ${.CURDIR}/UPDATING for more
+information."; \
+ echo; \
+ exit 1; \
+ fi
@cd ${.CURDIR}; ${MK_ENV} ${MAKE} buildworld
.if${MACHINE_ARCH} == "i386" && ${OBJFORMAT} == "elf" && defined(WANT_AOUT)
@cd ${.CURDIR}; ${LEGACY_ENV} ${XMAKE} legacy-build
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: make buildworld problem...
As Peter Jeremy wrote ... > On 1999-Oct-28 07:36:53 +1000, David O'Brien wrote: > >IF you are going to run -CURRENT, you need to read this list. > > And read /usr/src/UPDATING which also warns about this > > >(/me wonders how many MORE times we are going to have to say this because > >of the signal changes...) > > A very large number I suspect. > > IMHO, the correct solution is to for the entire make world process to > be re-worked. I believe the process should always be to boot a new > kernel first (as bde(?) commented - it's much easier to recover from a > broken kernel than a broken world), and then install a new world. > Getting there from here is non-trivial - the major problem being that > our build process does not adequately differentiate between compiling > code that must run now and code that must run with the new kernel. Marcel (the one that hacked on signals ;-) is giving this very subject intensive thought. But it is definitely a lot of work. -- | / o / / _ Arnhem, The Netherlands- Powered by FreeBSD - |/|/ / / /( (_) BulteWWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make buildworld problem...
Peter Jeremy wrote: > > >(/me wonders how many MORE times we are going to have to say this because > >of the signal changes...) > > A very large number I suspect. > > IMHO, the correct solution is to for the entire make world process to > be re-worked. That's what I'm currently doing. If I have a stripped down make process ready for public viewing, I'll let you all know. A thread on the subject can be found in the -arch archives. -- Marcel Moolenaarmailto:[EMAIL PROTECTED] SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD projectmailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make buildworld problem...
> cc -c -O -pipe ^ <-- try getting rid of this and see what happens. Good Luck, Jerry Hicks [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make buildworld problem...
On 1999-Oct-28 07:36:53 +1000, David O'Brien wrote: >IF you are going to run -CURRENT, you need to read this list. And read /usr/src/UPDATING which also warns about this >(/me wonders how many MORE times we are going to have to say this because >of the signal changes...) A very large number I suspect. IMHO, the correct solution is to for the entire make world process to be re-worked. I believe the process should always be to boot a new kernel first (as bde(?) commented - it's much easier to recover from a broken kernel than a broken world), and then install a new world. Getting there from here is non-trivial - the major problem being that our build process does not adequately differentiate between compiling code that must run now and code that must run with the new kernel. Peter -- Peter Jeremy (VK2PJ)[EMAIL PROTECTED] Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5982 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make buildworld problem...
On Wed, 27 Oct 1999, David O'Brien wrote: > IF you are going to run -CURRENT, you need to read this list. > (/me wonders how many MORE times we are going to have to say this because > of the signal changes...) So why not automate a warning? In the current Makefiles, make the build depend upon the existence of a file that we create only if the kernel is sufficiently new. If the file is not present, issue an error message. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make buildworld problem...
> /shared1/FreeBSD/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/libgcc1.c > *** Signal 12 > Stop in /shared1/FreeBSD/src/gnu/lib/libgcc. > *** Error code 1 RTFML (Read The FINE Mailing List)!! This has come up for the past many weeks. You need to build a kernel BEFORE your ``make world''. IF you are going to run -CURRENT, you need to read this list. (/me wonders how many MORE times we are going to have to say this because of the signal changes...) -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: make buildworld problem...
My last update was from: Sep 14 20:24:31 My kernel is: root@[space /usr/src] # uname -a FreeBSD space.nextra.sk 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Tue Sep 14 20:24:31 GMT 1999 [EMAIL PROTECTED]:/shared1/src/sys/compile/tps-common i386 -- Tomas TPS Ulej Network Administrator NEXTRA by Telenor Internet more? http://www.ripe.net/cgi-bin/whois?tu36-ripe > -Original Message- > From: Mike Pritchard [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, October 27, 1999 10:00 PM > To: Tomas TPS Ulej > Subject: Re: make buildworld problem... > > > How old is your kernel? This looks like what you see when you > try and do a buildworld without a -current kernel after all > of the recent signal changes. > > -Mike > > On Wed, Oct 27, 1999 at 09:26:14PM +0200, Tomas TPS Ulej wrote: > > >From today's cvsup: > > > > cd /usr/src ; make clean ; make buildworld > > > > [snip] > > > > rm -f .depend /usr/obj/shared1/FreeBSD/src/gnu/lib/libgcc/GPATH > > /usr/obj/shared1/FreeBSD/src/gnu/lib/libgcc/GRTAGS > > /usr/obj/shared1/FreeBSD/src/gnu/lib/libgcc/GSYMS > > /usr/obj/shared1/FreeBSD/src/gnu/lib/libgcc/GTAGS > > echo '#include ' > config.h > > echo '#include ' >> config.h > > echo '#include "i386/xm-i386.h"' > tconfig.h > > echo '#include "i386/i386.h"' > tm.h > > echo '#include "i386/att.h"' >> tm.h > > echo '#include "i386/freebsd.h"' >> tm.h > > echo '#include "i386/perform.h"' >> tm.h > > cc -c -O -pipe > -I/shared1/FreeBSD/src/gnu/lib/libgcc/../../../contrib/egcs/g > > cc/config > -I/shared1/FreeBSD/src/gnu/lib/libgcc/../../../contrib/egcs/gcc -I > > . -fexceptions -DIN_GCC > -I/usr/obj/shared1/FreeBSD/src/tmp/usr/include -DL_m > > ulsi3 -o _mulsi3.o > > /shared1/FreeBSD/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/libgcc1.c > > *** Signal 12 > > > > Stop in /shared1/FreeBSD/src/gnu/lib/libgcc. > > *** Error code 1 > > > > Stop in /shared1/FreeBSD/src. > > *** Error code 1 > > > > -- > > Tomas TPS Ulej > > Network Administrator > > NEXTRA by Telenor Internet > > more? http://www.ripe.net/cgi-bin/whois?tu36-ripe > > > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-current" in the body of the message > > -- > Mike Pritchard > [EMAIL PROTECTED] or [EMAIL PROTECTED] > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
make buildworld problem...
>From today's cvsup: cd /usr/src ; make clean ; make buildworld [snip] rm -f .depend /usr/obj/shared1/FreeBSD/src/gnu/lib/libgcc/GPATH /usr/obj/shared1/FreeBSD/src/gnu/lib/libgcc/GRTAGS /usr/obj/shared1/FreeBSD/src/gnu/lib/libgcc/GSYMS /usr/obj/shared1/FreeBSD/src/gnu/lib/libgcc/GTAGS echo '#include ' > config.h echo '#include ' >> config.h echo '#include "i386/xm-i386.h"' > tconfig.h echo '#include "i386/i386.h"' > tm.h echo '#include "i386/att.h"' >> tm.h echo '#include "i386/freebsd.h"' >> tm.h echo '#include "i386/perform.h"' >> tm.h cc -c -O -pipe -I/shared1/FreeBSD/src/gnu/lib/libgcc/../../../contrib/egcs/g cc/config -I/shared1/FreeBSD/src/gnu/lib/libgcc/../../../contrib/egcs/gcc -I . -fexceptions -DIN_GCC -I/usr/obj/shared1/FreeBSD/src/tmp/usr/include -DL_m ulsi3 -o _mulsi3.o /shared1/FreeBSD/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/libgcc1.c *** Signal 12 Stop in /shared1/FreeBSD/src/gnu/lib/libgcc. *** Error code 1 Stop in /shared1/FreeBSD/src. *** Error code 1 -- Tomas TPS Ulej Network Administrator NEXTRA by Telenor Internet more? http://www.ripe.net/cgi-bin/whois?tu36-ripe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
