Re: buildworld problem
On Sat, 19 May 2012 11:18:37 -0500 CyberLeo Kitsana cyber...@cyberleo.net wrote: On 05/19/2012 03:29 AM, Andriy Babiy wrote: Makefile.inc1, line 160: CPUTYPE global should be set with ?=. ... In make.conf I have CPUTYPE=nocona As it says, you need CPUTYPE?=nocona instead of CPUTYPE=nocona in /etc/make.conf or /etc/src.conf; otherwise the build process chokes while building the 32-bit compatibility stuff, since it cannot override your 64-bit CPU selection with a 32-bit one. You are right. Thank you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: buildworld problem
On 05/18/2012 09:17 PM, Andriy Babiy wrote: FreeBSD myhost 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Fri Mar 23 20:00:59 PDT 2012 root@myhost:/usr/obj/usr/src/sys/GENERIC amd64 root#cd /usr/obj root#chflags -R noschg * root#rm -rf * root#make buildworld ... cd /usr/src; MACHINE=i386 MACHINE_ARCH=i386 MACHINE_CPU=i686 mmx sse sse2 LD=ld -m elf_i386_fbsd -Y P,/usr/obj/usr/src/lib32/usr/lib32 AS=as --32 MAKEOBJDIRPREFIX=/usr/obj/lib32 I may be going over my head on this one:-) However to my understanding it seems, it is trying to build 32 bit on a amd 64bit install? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: buildworld problem
FreeBSD myhost 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Fri Mar 23 20:00:59 PDT 2012 root@myhost:/usr/obj/usr/src/sys/GENERIC amd64 root#cd /usr/obj root#chflags -R noschg * root#rm -rf * root#make buildworld ... cd /usr/src; MACHINE=i386 MACHINE_ARCH=i386 MACHINE_CPU=i686 mmx sse sse2 LD=ld -m elf_i386_fbsd -Y P,/usr/obj/usr/src/lib32/usr/lib32 AS=as --32 MAKEOBJDIRPREFIX=/usr/obj/lib32 I may be going over my head on this one:-) However to my understanding it seems, it is trying to build 32 bit on a amd 64bit install? Since 7.0 I upgraded this machine via buildworld. It was always amd64. As you see in uname output, I upgraded it from 8.X to 9.0 with no problem. Time/date is in sync. I don't see any problems in the system I am running, but I got latest code changes for SSL and wanted to do as usual per instructions. On i386 machine everything worked fine, and I don't suspect the code changes are causing it; there must be something simple I miss. In make.conf I have CPUTYPE=nocona and perl version, and obviously clang related definitions. In the error above I see -DCOMPAT_32 string which might be the case for building 32 compatibility libraries for amd64, but it still doesn't explain what fails and why. Any ideas? Thank you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: buildworld problem
On 05/18/2012 09:17 PM, Andriy Babiy wrote:
Makefile.inc1, line 160: CPUTYPE global should be set with ?=
I think the problem is the wrong cpu type define. . I took a
glance at the code in the makefile.inc1 to see what would set that
error off and i found this in the makefile.inc1
if cpu type does not equal target_cputype then throw that error.
.if ${_CPUTYPE} != ${_TARGET_CPUTYPE}
.error CPUTYPE global should be set with ?=.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: buildworld problem
On 5/19/2012 3:11 AM, Edward M wrote: Try 'env -i make buildworld' after cleaning obj. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: buildworld problem
On 05/19/2012 03:29 AM, Andriy Babiy wrote: Makefile.inc1, line 160: CPUTYPE global should be set with ?=. ... In make.conf I have CPUTYPE=nocona As it says, you need CPUTYPE?=nocona instead of CPUTYPE=nocona in /etc/make.conf or /etc/src.conf; otherwise the build process chokes while building the 32-bit compatibility stuff, since it cannot override your 64-bit CPU selection with a 32-bit one. -- Fuzzy love, -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net cyber...@cyberleo.net Furry Peace! - http://.fur.com/peace/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: buildworld problem
On 05/19/2012 09:18 AM, CyberLeo Kitsana wrote: As it says, you need CPUTYPE?=nocona instead of CPUTYPE=nocona in /etc/make.conf or /etc/src.conf; otherwise the build process chokes while building the 32-bit compatibility stuff, since it cannot override your 64-bit CPU selection with a 32-bit one. Just learned something new:-) had a look in share/examples/etc/make.conf file and i noticed this # (?= allows to buildworld for a different CPUTYPE.) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Buildworld problem
I am so sorry. forgot to add details about my system. I am running FreeBSD 6.2. Here is uname output. FreeBSD 6.2-RELEASE-p9 FreeBSD 6.2-RELEASE-p9 #0: Thu Nov 29 04:07:33 UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 Thanks, Venkatesh K On Dec 4, 2007 2:32 PM, Venkatesh K [EMAIL PROTECTED] wrote: Hi, make buildworld failed for me. Here is the error log. --- cc -O2 -fno-strict-aliasing -pipe -DHAVE_CONFIG_H -DRL_NO_COMPAT -DMI_OUT=1 -DTUI=1 -I. -I/usr/src/gnu/usr.bin/gdb/kgdb/../arch/i386 -I/usr/src/gnu/usr.bin/gdb/kgdb/../../binutils/libbfd -I/usr/src/gnu/usr.bin/gdb/kgdb/../../binutils/libbfd/i386 -I/usr/src/gnu/usr.bin/gdb/kgdb/../../../../contrib/gdb/gdb -I/usr/src/gnu/usr.bin/gdb/kgdb/../../../../contrib/gdb/gdb/config -I/usr/src/gnu/usr.bin/gdb/kgdb/../../../../contrib/gdb/include -I/usr/src/gnu/usr.bin/gdb/kgdb/../../../../contrib/binutils/include -I/usr/src/gnu/usr.bin/gdb/kgdb/../../../../contrib/binutils/bfd -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /usr/src/gnu/usr.bin/gdb/kgdb/kthr.c cc -O2 -fno-strict-aliasing -pipe -DHAVE_CONFIG_H -DRL_NO_COMPAT -DMI_OUT=1 -DTUI=1 -I. -I/usr/src/gnu/usr.bin/gdb/kgdb/../arch/i386 -I/usr/src/gnu/usr.bin/gdb/kgdb/../../binutils/libbfd -I/usr/src/gnu/usr.bin/gdb/kgdb/../../binutils/libbfd/i386 -I/usr/src/gnu/usr.bin/gdb/kgdb/../../../../contrib/gdb/gdb -I/usr/src/gnu/usr.bin/gdb/kgdb/../../../../contrib/gdb/gdb/config -I/usr/src/gnu/usr.bin/gdb/kgdb/../../../../contrib/gdb/include -I/usr/src/gnu/usr.bin/gdb/kgdb/../../../../contrib/binutils/include -I/usr/src/gnu/usr.bin/gdb/kgdb/../../../../contrib/binutils/bfd -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /usr/src/gnu/usr.bin/gdb/kgdb/trgt.c cc -O2 -fno-strict-aliasing -pipe -DHAVE_CONFIG_H -DRL_NO_COMPAT -DMI_OUT=1 -DTUI=1 -I. -I/usr/src/gnu/usr.bin/gdb/kgdb/../arch/i386 -I/usr/src/gnu/usr.bin/gdb/kgdb/../../binutils/libbfd -I/usr/src/gnu/usr.bin/gdb/kgdb/../../binutils/libbfd/i386 -I/usr/src/gnu/usr.bin/gdb/kgdb/../../../../contrib/gdb/gdb -I/usr/src/gnu/usr.bin/gdb/kgdb/../../../../contrib/gdb/gdb/config -I/usr/src/gnu/usr.bin/gdb/kgdb/../../../../contrib/gdb/include -I/usr/src/gnu/usr.bin/gdb/kgdb/../../../../contrib/binutils/include -I/usr/src/gnu/usr.bin/gdb/kgdb/../../../../contrib/binutils/bfd -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /usr/src/gnu/usr.bin/gdb/kgdb/trgt_i386.c cc -O2 -fno-strict-aliasing -pipe -DHAVE_CONFIG_H -DRL_NO_COMPAT -DMI_OUT=1 -DTUI=1 -I. -I/usr/src/gnu/usr.bin/gdb/kgdb/../arch/i386 -I/usr/src/gnu/usr.bin/gdb/kgdb/../../binutils/libbfd -I/usr/src/gnu/usr.bin/gdb/kgdb/../../binutils/libbfd/i386 -I/usr/src/gnu/usr.bin/gdb/kgdb/../../../../contrib/gdb/gdb -I/usr/src/gnu/usr.bin/gdb/kgdb/../../../../contrib/gdb/gdb/config -I/usr/src/gnu/usr.bin/gdb/kgdb/../../../../contrib/gdb/include -I/usr/src/gnu/usr.bin/gdb/kgdb/../../../../contrib/binutils/include -I/usr/src/gnu/usr.bin/gdb/kgdb/../../../../contrib/binutils/bfd -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -o kgdb main.o kthr.o trgt.o trgt_i386.o /usr/obj/usr/src/gnu/usr.bin/gdb/kgdb/../../gdb/libgdb/libgdb.a /usr/obj/usr/src/gnu/usr.bin/gdb/kgdb/../../binutils/libbfd/libbfd.a /usr/obj/usr/src/gnu/usr.bin/gdb/kgdb/../../binutils/libopcodes/libopcodes.a /usr/obj/usr/src/gnu/usr.bin/gdb/kgdb/../../binutils/libiberty/libiberty.a -lkvm -lm -lreadline -ltermcap -lgnuregex gzip -cn /usr/src/gnu/usr.bin/gdb/kgdb/kgdb.1 kgdb.1.gz === gnu/usr.bin/gdb/gdbserver (all) make: don't know how to make bsd.README. Stop *** Error code 2 Stop in /usr/src/gnu/usr.bin/gdb. *** Error code 1 Stop in /usr/src/gnu/usr.bin. *** Error code 1 Stop in /usr/src/gnu. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. --- Anyone facing similar problem? Thanks, -- Venkatesh. K ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Buildworld problem
Venkatesh K wrote: === gnu/usr.bin/gdb/gdbserver (all) make: don't know how to make bsd.README. Stop FreeBSD 6.2-RELEASE-p9 FreeBSD 6.2-RELEASE-p9 #0: Thu Nov 29 04:07:33 UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 What code version are you trying to compile? The same as your system? You may just want to run another cvsup, maybe you caught it at a bad time. -- Philip M. Gollucci ([EMAIL PROTECTED]) o:703.549.2050x206 Senior System Admin - Riderway, Inc. http://riderway.com / http://ridecharge.com 1024D/EC88A0BF 0DE5 C55C 6BF3 B235 2DAB B89E 1324 9B4F EC88 A0BF Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Buildworld problem
Venkatesh K wrote: make: don't know how to make bsd.README. Stop obrien 2007-12-03 21:05:20 UTC FreeBSD src repository Modified files:(Branch: RELENG_6_3) gnu/usr.bin/gdb/arch/amd64 Makefile gnu/usr.bin/gdb/arch/i386 Makefile gnu/usr.bin/gdb/kgdb kgdb.h Log: MFC: + Turn on gdbserver for the arch that supports it. + Fix static/extern mismatch. + Remove extern int verbose declaration. Approved by:re(kensmith) Revision ChangesPath 1.3.10.1 +6 -1 src/gnu/usr.bin/gdb/arch/amd64/Makefile 1.4.10.1 +5 -1 src/gnu/usr.bin/gdb/arch/i386/Makefile 1.2.2.3.2.1 +0 -1 src/gnu/usr.bin/gdb/kgdb/kgdb.h ___ Looks like this did it. -- Philip M. Gollucci ([EMAIL PROTECTED]) o:703.549.2050x206 Senior System Admin - Riderway, Inc. http://riderway.com / http://ridecharge.com 1024D/EC88A0BF 0DE5 C55C 6BF3 B235 2DAB B89E 1324 9B4F EC88 A0BF Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buildworld problem
On Mon, 27 Jun 2005, ANdrei wrote: i have a problem, that I think is probably just a mistake in the way I do things... am trying to buildworld on a 5.2.1-release (have done build world several times with success on 4.x) the system is a fresh install. i go to single user, and I get rm: ipf: is a directory as an error. ...this is happening in the make cleandir part already... but it doesn't happen when in multiuser mode... actually in multiuser mode make clean and make cleandir work well... Remove the contents of your /usr/obj tree and build again. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Buildworld problem?
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Java Weenie Sent: Tuesday, June 14, 2005 11:38 AM To: [EMAIL PROTECTED] Subject: Buildworld problem? I had a 4gig drive laying around that I wanted to use for a router, so I installed the latest (from about 1.5 weeks ago) from the 5.x distrubutions. I added ipfw/natd/dummynet to the kernel file and did a full buildworld, buildkernel. I rebooted after install kernel, everything seemed normal, did install world/mergemaster, rebooted. Right now, I have an 'ok' prompt, it appears after the 'Press enter to start booting immediately, or hit any other key to do something else' option and it states it cannot find kernel or kernel.old. My guesses are that either I got a really bad batch of sources, I performed a buildworld wrong (though I did double check my steps with the handbook first), or my hard drive picked a really unusual place to die. It is a new clean install so it wouldn't be a huge issue to reinstall, but if it is hardware, I will need to replace the drive before doing this again. Any thoughts on how to determine the problem? From: John Brooks [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: Java Weenie [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: RE: Buildworld problem? Date: Tue, 14 Jun 2005 12:17:15 -0500 run the hard drive diagnostics software of your hard drive manufacturer to test the condition of your hard drive. it should be available from their website. this should always be done on used drives being put back into service. -- John Brooks [EMAIL PROTECTED] After running the diagnostics, the drive reports no problems, though it still won't boot. Playing around with sysinstall on a 5.4 cd, the partition editor shows my partitions, but the mount points are listed as *, not / and /usr. Is there a way to reassign the mount points without wiping the drive? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Buildworld problem? -Solved
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Java Weenie Sent: Tuesday, June 14, 2005 11:38 AM To: [EMAIL PROTECTED] Subject: Buildworld problem? I had a 4gig drive laying around that I wanted to use for a router, so I installed the latest (from about 1.5 weeks ago) from the 5.x distrubutions. I added ipfw/natd/dummynet to the kernel file and did a full buildworld, buildkernel. I rebooted after install kernel, everything seemed normal, did install world/mergemaster, rebooted. Right now, I have an 'ok' prompt, it appears after the 'Press enter to start booting immediately, or hit any other key to do something else' option and it states it cannot find kernel or kernel.old. My guesses are that either I got a really bad batch of sources, I performed a buildworld wrong (though I did double check my steps with the handbook first), or my hard drive picked a really unusual place to die. It is a new clean install so it wouldn't be a huge issue to reinstall, but if it is hardware, I will need to replace the drive before doing this again. Any thoughts on how to determine the problem? Using sysinstall's label editor, I was able to get my file system back. I also found the source of the problem (I think): my cvsup file was set to grab RELENG_4, this is from a 5.x install cd. I will be doing a new build world after a fresh cvsup. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Buildworld problem?
run the hard drive diagnostics software of your hard drive manufacturer to test the condition of your hard drive. it should be available from their website. this should always be done on used drives being put back into service. -- John Brooks [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Java Weenie Sent: Tuesday, June 14, 2005 11:38 AM To: [EMAIL PROTECTED] Subject: Buildworld problem? I had a 4gig drive laying around that I wanted to use for a router, so I installed the latest (from about 1.5 weeks ago) from the 5.x distrubutions. I added ipfw/natd/dummynet to the kernel file and did a full buildworld, buildkernel. I rebooted after install kernel, everything seemed normal, did install world/mergemaster, rebooted. Right now, I have an 'ok' prompt, it appears after the 'Press enter to start booting immediately, or hit any other key to do something else' option and it states it cannot find kernel or kernel.old. My guesses are that either I got a really bad batch of sources, I performed a buildworld wrong (though I did double check my steps with the handbook first), or my hard drive picked a really unusual place to die. It is a new clean install so it wouldn't be a huge issue to reinstall, but if it is hardware, I will need to replace the drive before doing this again. Any thoughts on how to determine the problem? Thanks for any tips. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [Re: Buildworld problem]
My apologies. I had responded to the wrong address. - Original Message - From: Jacques A. Vidrine [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: HiTech Creations Support [EMAIL PROTECTED] Sent: Friday, February 28, 2003 10:26 AM Subject: Fwd: [Re: Buildworld problem] This belongs on freebsd-questions. - Forwarded message from HiTech Creations Support [EMAIL PROTECTED] - Date: Fri, 28 Feb 2003 10:24:36 -0600 From: HiTech Creations Support [EMAIL PROTECTED] To: Jacques A. Vidrine [EMAIL PROTECTED] Subject: Re: Buildworld problem Message-ID: [EMAIL PROTECTED] Reply-To: HiTech Creations Support [EMAIL PROTECTED] Organization: HiTech Creations We went ahead and did that and managed to get the buildworld to work. We do have NOSECURE currently defined in make.conf. We went ahead and defined NO_OPENSSL and NO_OPENSSH to get around the 'make buildworld' problem. The only side effect we noticed occurred after the reboot of the server. None of our passwords worked. Keep in mind we are doing this from Texas, while our servers are in St. Louis, MO. Of course, we do not allow 'root' to login via telnet, but luckily, we have another server at the co-location which we have tied to this server using serial com ports. This allows us to login as root and rebuild the password database. We still have a problem though. When we attempted to build MySQL in the ports tree, it insisted on trying to build the p5 stuff and would fail with the error Could not find mysql.h while looking in /usr/include and /usr/local/include'. The error is not an exact quote. We went ahead and manually copied mysqld to the /usr/local/libexec directory and it is now working. We got the server up around midnight last night, but we would like to get the problems with the MySQL build resolved before doing this to our other server. Any ideas? - Original Message - From: Jacques A. Vidrine [EMAIL PROTECTED] To: HiTech Creations Support [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Thursday, February 27, 2003 5:19 PM Subject: Re: Buildworld problem On Thu, Feb 27, 2003 at 05:06:51PM -0600, HiTech Creations Support wrote: /usr/src/lib/libpam/modules/pam_ssh/pam_ssh.c:61: openssl/dsa.h: No such file or directory. Take NO_OPENSSL out of your /etc/make.conf ? Cheers, -- Jacques A. Vidrine [EMAIL PROTECTED] http://www.celabo.org/ NTT/Verio SME . FreeBSD UNIX . Heimdal Kerberos [EMAIL PROTECTED] . [EMAIL PROTECTED] . [EMAIL PROTECTED] - End forwarded message - To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: buildworld problem on cyrix 166
Freebies - In re: the 'ncurses' buildworld failures while upgrading, which I've also experienced: On Wed, 18 Dec 2002, JacobRhoden wrote: On Wed, 18 Dec 2002 13:23, Ken Kroel wrote: i am trying to update an old pc and have run into a problem with the make CPU: Cyrix 6x86 (486-class CPU) Origin = CyrixInstead DIR=0x2231 Stepping=2 Revision=2 Perhaps the Cyrix-IBM/166 is the common denominator here, as that is my chip, too. Should I specify the processor to my build environment? I have never tried this. Has it helped others with this build failure? I had the exact same problem with the exact same machine you appear to have. This list at the time attributed it to a hardware issue, probably faulty memory. Try doing a make clean, to clean up everything, and try again. If the make fails at a different place each time, then its definatly a hardware problem. I only recall problems from folks doing upgrades (from RELENG_4_5 to RELENG_4_6, _7 in my case). Have others seen the problem when doing 'buildworld' on an installed system at RELENG_4_6 or later, or is this an 'upgrade only' issue? (I have been able to get some partial and redone builds to complete, but never installed them because my purpose is to set a firm foundation under my system and I didn't feel I knew what was in the mix in those cases.) TIA for comments. - John Mills To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: buildworld problem on cyrix 166
On 2002-12-18 10:27, John Mills [EMAIL PROTECTED] wrote: On Wed, 18 Dec 2002, JacobRhoden wrote: On Wed, 18 Dec 2002 13:23, Ken Kroel wrote: i am trying to update an old pc and have run into a problem with the make CPU: Cyrix 6x86 (486-class CPU) Origin = CyrixInstead DIR=0x2231 Stepping=2 Revision=2 Should I specify the processor to my build environment? I have never tried this. Has it helped others with this build failure? I never specify processor dependent optimizations to my builds. I also have the following in my /etc/make.conf file: NO_CPU_CFLAGS= true# Don't add -march=cpu to CFLAGS automatically NO_CPU_COPTFLAGS=true # Don't add -march=cpu to COPTFLAGS automatically I didn't try enabling any sort of CPU specific flags while I still used that Cyrix, but I also run against the same problem in one of the upgrades from 4.4-RELEASE to 4.5-RELEASE then 4.6-RELEASE and finally to 4.7-RELEASE. I only recall problems from folks doing upgrades (from RELENG_4_5 to RELENG_4_6, _7 in my case). Have others seen the problem when doing 'buildworld' on an installed system at RELENG_4_6 or later, or is this an 'upgrade only' issue? Once I successfully built a 4.7-RELEASE userland (which I needed to keep as a failover installation, in case my upgrade to 5.0-CURRENT didn't quite work) the problems went away. Everything worked fine with newer upgrades of the 4.X series. (I have been able to get some partial and redone builds to complete, but never installed them because my purpose is to set a firm foundation under my system and I didn't feel I knew what was in the mix in those cases.) It's probably easier to grab a CDROM image for 4.7-RELEASE and install that, if you want to be 100% sure that everything your system runs can be trusted. Having written that, there's really nothing wrong with interrupting the buildworld process after it passes the stage of the libraries and continuing the process later on with -DNOCLEAN. The userland programs that are built after that stage will use the already compiled binaries of /usr/obj and the `critical' parts of the system have already been built. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: buildworld problem on cyrix 166
On 2002-12-17 21:23, Ken Kroel [EMAIL PROTECTED] wrote: greetings, i am trying to update an old pc and have run into a problem with the make buildworld step. the box is 4.7 release, using a network install. [...] *default release=cvs tag=RELENG_4_7. next, i made /root/kernel and copied GENERIC into it. [...] cc -fpic -DPIC -O -pipe -I. -I/usr/src/lib/libncurses -I/usr/src/lib/libncurses /../../contrib/ncurses/ncurses -I/usr/src/lib/libncurses/../../contrib/ncurses/i nclude -Wall -DFREEBSD_NATIVE -DNDEBUG -DHAVE_CONFIG_H -DTERMIOS -c unctrl.c -o unctrl.So cc -fpic -DPIC -O -pipe -I. -I/usr/src/lib/libncurses -I/usr/src/lib/libncurses /../../contrib/ncurses/ncurses -I/usr/src/lib/libncurses/../../contrib/ncurses/i nclude -Wall -DFREEBSD_NATIVE -DNDEBUG -DHAVE_CONFIG_H -DTERMIOS -c /usr/src/li b/libncurses/../../contrib/ncurses/ncurses/tinfo/access.c -o access.So cc -fpic -DPIC -O -pipe -I. -I/usr/src/lib/libncurses -I/usr/src/lib/libncurses /../../contrib/ncurses/ncurses -I/usr/src/lib/libncurses/../../contrib/ncurses/i nclude -Wall -DFREEBSD_NATIVE -DNDEBUG -DHAVE_CONFIG_H -DTERMIOS -c /usr/src/li b/libncurses/../../contrib/ncurses/ncurses/tinfo/add_tries.c -o add_tries.So cc -fpic -DPIC -O -pipe -I. -I/usr/src/lib/libncurses -I/usr/src/lib/libncurses/../../contrib/ncurses/ncurses -I/usr/src/lib/libncurses/../../contrib/ncurses/include -Wall -DFREEBSD_NATIVE -DNDEBUG -DHAVE_CONFIG_H -DTERMIOS -c /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/alloc_entry.c -o alloc_entry.So cc: Internal compiler error: program cc1 got fatal signal 11 *** Error code 1 Stop in /usr/src/lib/libncurses. *** Error code 1 I'm not sure if this is a problem that is caused by overheated CPUs, but I had similar problems when trying to upgrade a Cyrix-based machine from 4.4-RELEASE to RELENG_4. Removing everything from the /usr/obj/usr/src/lib/libncurses directory and starting a buildworld with -DNOCLEAN to avoid rebuilding the parts that were already under/usr/obj worked for me. I never had problems of this nature when the same machine (the very same hardware) was running with an Intel Pentium 133 cpu :( To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: buildworld problem on cyrix 166
On Wed, 18 Dec 2002 13:23, Ken Kroel wrote: i am trying to update an old pc and have run into a problem with the make CPU: Cyrix 6x86 (486-class CPU) Origin = CyrixInstead DIR=0x2231 Stepping=2 Revision=2 I had the exact same problem with the exact same machine you appear to have. This list at the time attributed it to a hardware issue, probably faulty memory. Try doing a make clean, to clean up everything, and try again. If the make fails at a different place each time, then its definatly a hardware problem. My solution was to try doing the make over, and over, and after about 10 tries it got all the way through. (which was frustrating because it did take over 7 hours to complete if I remember correctly) Regards, Jacob Jacob RhodenPhone: +61 3 8344 6102 ITS DivisionEmail: [EMAIL PROTECTED] Melbourne University Mobile: +61 403 788 386 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
