Re: problems with make world (Sunday)
On Tue, Sep 05, 2000 at 09:20:17AM +0200, Jean-Francois Dockes wrote: > Gary Kline writes: > >For the record, I just cvsup'ed this morning Monday, 04sep00) and > >buildworld hangs here: > > > > ===> objdump > > ... > > cc -O -pipe -D_GNU_SOURCE -I- -I. -I/usr/src/gnu/usr.bin/binutils/objdump >-I/usr/src/gnu/usr.bin/binutils/objdump/../libbfd/i386 >-I/usr/src/gnu/usr.bin/binutils/objdump/../../../../contrib/binutils/include >-I/usr/src/gnu/usr.bin/binutils/objdump/../libbinutils >-I/usr/src/gnu/usr.bin/binutils/objdump/../../../../contrib/binutils/binutils >-DBFD_VERSION=\"2.10.0\" -I/usr/obj/usr/src/i386/usr/include -o objdump objdump.o >prdbg.o ../libbinutils/libbinutils.a ../libopcodes/libopcodes.a ../libbfd/libbfd.a >../libiberty/libiberty.a > > ../libiberty/libiberty.a(choose-temp.o): In function `make_temp_file': > > choose-temp.o(.text+0x264): undefined reference to `mkstemps' > > *** Error code 1 > > I don't know if this applies to your case, but I had this error while > trying a direct upgrade from 3.2-release to 4-stable. It appears that > mkstemps() came in later than 3.2. I guess that a cvsup/buildworld to 3-stable > would be the correct way to solve this issue, but I just ar'd the > appropriate 4.x libc file into libiberty (cough, cough), in case it would > save me one more cvsup and it did do it... I then remade world under > 4-stable to clean things up. I should have grep'd my ~/Mail files earlier. On 20 August the same mkstemps snafu hit me. The fix was (and is) to add mkstemps.c to the SRCS list in /usr/src/gnu/usr.bin/binutils/libiberty/Makefile. The libiberty/Makefile still needs patching and the patch still needs a cvs commit. ...Anybody?? gary > -- Gary D. Kline [EMAIL PROTECTED] Public service Unix To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: problems with make world (Sunday)
Oops ... my mistake. A bit further down in the file there ... Warner Losh wrote: > >From UPDATING: > > To update from 4.0-RELEASE or later to the most current > 4.x-STABLE > -- > ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: problems with make world (Sunday)
Hi again, I did another cvsup (several, in fact) before posting my first message. I also tried "make buildworld" several times after the first build failed. Of course, I removed obj directory in a manner similar to what was suggested by some of you each time. I am using a very simple script that automates the build from freebsddiary.org Yes, it is the build that fails, not the install. If I remember correctly, the build does not even finish building all the stuff in the tools stage (but proceeds for a long time with no errors). I guess you'll have to wait until I am done with my work for the day and get back to the (non-networked) machine on which I have the build logs and post excerpts from them. My only guess at this point is that I managed to not have some C/C++ libraries installed... Well, FreeBSD 4.0 install from the CD set is quite buggy, given that there are 4 CDs and some of the packages/distributions on the first CD are dependent on packages on other CDs and fail to install from the /stand/sysinstall, not even prompting you for the other CD. So that could have happened. I am still hunting down various components across CDs and adding them with pkg_add. -j4 should only affect number of simultaneous processes. Since I have a dual-processor machine, I may try -j8. Thanks for assuring me that the branch is not broken. I was about to ditch FreeBSD with disgust thinking that "these losers even have their stable branch broken...". Just kidding! Nikita. On Mon, 4 Sep 2000, Erick Mechler wrote: > Try doing this: > > 1. do another cvsup to make sure that you got everything (and yes, using > RELENG_4 will give you the latest -STABLE in the 4.x branch). > 2. cd /usr/src > 3. make -j4 buildworld > 4. iff no errors, do make -j4 installworld > > You shouldn't have any problems with this, since I just did a sup this > morning and the world built fine. > > BTW, I would highly recommend not using "make world", since this does the > build and install all at once. If things go wrong during the build, you > won't have a chance to fix them before the world is installed. By > splitting them up with buildworld and installworld, you give yourself the > chance to fix buildworld problems before you install them. > > Also note that to upgrade your kernel (which you have to do every time > you do an installworld), continue on as such: > > 5. cd /usr/src/sys/i386/conf > 6. cp GENERIC > 7. Edit to your liking (be sure to check out > /usr/src/sys/i386/conf/LINT which has all the possible config options. > 8. cd /usr/src/ > 9. make -j4 buildkernel > 10. iff no errors, make -j4 installkernel > > The notes say to drop to single user before you do installworlds, but I > haven't had any problems doing them in multiuser mode (besides, I don't > have a console on my BSD machine, so single user is pretty difficult). > > Good luck, and let me know if you have any problems. > > Regards, > Erick > > At Mon, Sep 04, 2000 at 05:13:50PM -0400, Nikita Proskourine said this: > :: Hi all, > :: > :: I am a newbie to FreeBSD development, so please bear with me. I am > :: currently using FreeBSD-4.0 RELEASE. I did a fresh cvsup (using RELENG_4 > :: tag, that would get me a stable branch, right?) and "make world" on Sunday > :: and the build failed somewhere in objc contribs for gcc. > :: > :: I made logs of the build and will send them later today. In the meantime, I > :: was wondering if this is a known problem and whether there are workarounds > :: for this. > :: > :: Nikita. > :: > :: > :: To Unsubscribe: send mail to [EMAIL PROTECTED] > :: with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: problems with make world (Sunday)
In message <[EMAIL PROTECTED]> Bill Moran writes: : As far as I can tell there is no special documented procedure for : updating within the 4.X line. Should be able to do everything in the : ordinary way. I've done it that way on the current system. >From UPDATING: To update from 4.0-RELEASE or later to the most current 4.x-STABLE -- ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: problems with make world (Sunday)
What I've seen in the UPDATING file seems to refer to 3.X upgraded to 4.X As far as I can tell there is no special documented procedure for updating within the 4.X line. Should be able to do everything in the ordinary way. I've done it that way on the current system. Along those same lines ... I'm having trouble with one of my 4.0 servers trying to update it to 4.1 and getting all kinds of weird errors in doing the kernel. Just re-cvsuped and trying again. I cvsuped on Sunday as well. I think maybe something in the system was broken. -Bill Kent Stewart wrote: > You didn't read /usr/src/UPDATING. It tells you that you can try a > "make world" but if it fails don't complain until you have tried the > buildworld, build[install}kernel, installworld sequence. A lot changed > between 4.0 and 4.1. For example, a kernel build using the config is > not supported after a cvsup. It may work but there can be changes that > the buildkernel mode will process. Your kernel config file can be > different. You need to compare what you have against GENERIC. > > It has been 4 or 5 days since I did a cvsup and all of the builds and > installs. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: problems with make world (Sunday)
Nikita Proskourine wrote: > > Hi all, > > I am a newbie to FreeBSD development, so please bear with me. I am > currently using FreeBSD-4.0 RELEASE. I did a fresh cvsup (using RELENG_4 > tag, that would get me a stable branch, right?) and "make world" on Sunday > and the build failed somewhere in objc contribs for gcc. > > I made logs of the build and will send them later today. In the meantime, I > was wondering if this is a known problem and whether there are workarounds > for this. You didn't read /usr/src/UPDATING. It tells you that you can try a "make world" but if it fails don't complain until you have tried the buildworld, build[install}kernel, installworld sequence. A lot changed between 4.0 and 4.1. For example, a kernel build using the config is not supported after a cvsup. It may work but there can be changes that the buildkernel mode will process. Your kernel config file can be different. You need to compare what you have against GENERIC. It has been 4 or 5 days since I did a cvsup and all of the builds and installs. Kent > > Nikita. > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
problems with make world (Sunday)
Hi all, I am a newbie to FreeBSD development, so please bear with me. I am currently using FreeBSD-4.0 RELEASE. I did a fresh cvsup (using RELENG_4 tag, that would get me a stable branch, right?) and "make world" on Sunday and the build failed somewhere in objc contribs for gcc. I made logs of the build and will send them later today. In the meantime, I was wondering if this is a known problem and whether there are workarounds for this. Nikita. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
