Date: Sat, 30 Sep 2006 09:29:06 +0200 From: Uwe Doering <gemini@geminix.org> To: Ruslan Ermilov <ru@FreeBSD.org> Cc: Christer Solskogen <solskogen@carebears.mine.nu>, stable@FreeBSD.org Subject: Re: buildworld fails after patch (FreeBSD-SA-06:23.openssl) Message-ID: <451E1CC2.4090007@geminix.org> In-Reply-To: <20060929224437.GA63401@rambler-co.ru> References: <3466.62.97.242.158.1159516687.squirrel@carebears.mine.nu> <451D3E74.6030805@geminix.org> <20060929181806.GF37741@rambler-co.ru> <451D6735.70401@geminix.org> <20060929185615.GA38232@rambler-co.ru> <451D7254.50807@geminix.org> <20060929224437.GA63401@rambler-co.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Ruslan Ermilov wrote:
> On Fri, Sep 29, 2006 at 09:21:56PM +0200, Uwe Doering wrote:
>> Ruslan Ermilov wrote:
>>> It doesn't matter. What you suggest is not the correct way.
>>> Perhaps the buildworld is broken, but that's a separate issue.
>>>
>>>> My understanding so far is that the files under
>>>> '/usr/include' don't get touched until I run 'installworld'. So the
>>>> 'buildworld' universe has to be self-contained. That's what I was
>>>> trying to point out.
>>>>
>>> Yes, they are not touched. During buildworld, a special version
>>> of the compiler is built that looks headers up in the temporary
>>> location, normally /usr/obj/usr/src/tmp/usr/include. Then all
>>> (new) headers are installed there, then new libraries are built,
>>> then all the rest. If buildworld touched /usr/include, you
>>> could easily end up with a partially upgraded system, e.g. if
>>> build failed in the middle. If it still fails for you (the
>>> buildworld), please collect and put the full combiled stdout +
>>> stderr output from running "make buildworld" available somewhere
>>> for download and analysis. Colin said he did build all worlds,
>>> on all patched branches.
>> Unfortunately I can no longer reproduce the error because I fixed the
>> problem by hand, as pointed out above. Sorry.
>>
>>> OK, you had 4.11 and what were you trying to build? RELENG_4?
>>> So I can try to reproduce the problem here.
>> Yes, I use RELENG_4. Thanks for your help.
>>
> Worked for me building fresh RELENG_4:
>
> : > uname -srm
> : FreeBSD 4.10-RELEASE i386
> : > tail -3 build.log
> : rm -f freebsd.submit.cf
> : m4 -D_CF_DIR_=/spool/ru_tmp/src/etc/sendmail/../../contrib/sendmail/cf/ /spool/ru_tmp/src/etc/sendmail/../../contrib/sendmail/cf/m4/cf.m4 /spool/ru_tmp/src/etc/sendmail/freebsd.submit.mc > freebsd.submit.cf
> : chmod 444 freebsd.submit.cf
> : >
Thanks for testing it. So this problem seems to be specific to my
workstation. If it happens again I'll investigate it more thoroughly.
Regards,
Uwe
--
Uwe Doering | EscapeBox - Managed On-Demand UNIX Servers
gemini@geminix.org | http://www.escapebox.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?451E1CC2.4090007>