Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 20 May 2007 01:27:06 -0600
From:      Scott Long <scottl@samsco.org>
To:        Ruslan Ermilov <ru@freebsd.org>
Cc:        cvs-src@freebsd.org, src-committers@freebsd.org, Alexander Kabaev <kabaev@gmail.com>, cvs-all@freebsd.org
Subject:   Re: cvs commit: src/gnu/usr.bin/cc/cc_tools Makefile
Message-ID:  <464FF84A.3030106@samsco.org>
In-Reply-To: <20070520062748.GA54935@rambler-co.ru>
References:  <200705190756.l4J7u9wP058382@repoman.freebsd.org> <20070519085103.GA61276@rambler-co.ru> <20070519105804.6b6cae10@kan.dnsalias.net> <20070520062748.GA54935@rambler-co.ru>

next in thread | previous in thread | raw e-mail | index | archive | help
Ruslan Ermilov wrote:
> On Sat, May 19, 2007 at 10:58:04AM -0400, Alexander Kabaev wrote:
>> On Sat, 19 May 2007 12:51:03 +0400
>> Ruslan Ermilov <ru@FreeBSD.org> wrote:
>>
>>> On Sat, May 19, 2007 at 07:56:09AM +0000, Scott Long wrote:
>>>> scottl      2007-05-19 07:56:09 UTC
>>>>
>>>>   FreeBSD src repository
>>>>
>>>>   Modified files:
>>>>     gnu/usr.bin/cc/cc_tools Makefile 
>>>>   Log:
>>>>   Work-around for upgrading from a pre-symbol-versioned world.
>>>>   
>>>>   Blame-to: cperciva
>>>>   
>>>>   Revision  Changes    Path
>>>>   1.86      +1 -0      src/gnu/usr.bin/cc/cc_tools/Makefile
>>>>
>>> Can you elaborate as to what problem you're trying to address?
>>> I went through this process yesterday and hit no problems, all
>>> was smooth.
>> GCC build tools somehow were built against shared libc.so.7 with symbol
>> versioning, instead of library on host. So then when we attempted to
>> run them, they were failing. I do not know why it was happening on
>> amd64 machine Scott was trying upgrade on yet. My relatively old i386
>> installation worked without a hitch :( 
>>
> It sometimes happens when the date/time are not being set
> properly, so that the tools are mistakenly rebuilt again
> at an inappropriate time when in the foreign environment
> of the target -- the problem is usually understood better
> when building for another CPU architecture and hitting it.
> I think this was an inappropriate commit to make, unless
> the problem can be reproduced.  I have upgraded several
> i386's and amd64's without a problem.
> 
> 
> Cheers,

You spell it "inappropriate", I spell it "making a simple temporary 
commit to help be sure that the entire userbase doesn't get screwed over 
by a last minute problem."  Whatever, fix it however you like.

Scott




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?464FF84A.3030106>