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 <your_kernel_here>
> 7. Edit <your_kernel_here> 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