Date: Fri, 29 Sep 2006 20:34:29 +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: <451D6735.70401@geminix.org> In-Reply-To: <20060929181806.GF37741@rambler-co.ru> References: <3466.62.97.242.158.1159516687.squirrel@carebears.mine.nu> <451D3E74.6030805@geminix.org> <20060929181806.GF37741@rambler-co.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Ruslan Ermilov wrote:
> On Fri, Sep 29, 2006 at 05:40:36PM +0200, Uwe Doering wrote:
> [...]
>> The same happened on my workstation, which runs 4.11. The cause of this
>> problem is that the openssl sources under '/usr/src' apparently use some
>> include files installed under '/usr/include/openssl' instead of those in
>> the '/usr/src' tree.
>>
>> The fix for me was to copy the '*.h' files that changed into
>> '/usr/include/openssl' by hand. Afterwards things worked as expected.
>> This is of course just a workaround. The proper fix would be to modify
>> the respective makefiles to add all the directories where there are
>> header files to the list of include directories given to 'cc' with '-I'
>> options. This apparently hasn't been done so far. At least not completely.
>>
> No. The correct way is to either do a full build (aka buildworld),
> or a partial build by first installing headers, and then doing the
> library build.
??????
Did you notice the subject of this thread? The problem occured while
running 'buildworld'. 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.
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?451D6735.70401>