This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
RE: 4.1.1 spec files missing, FAQ misinformation
- From: "Dave Korn" <dave dot korn at artimi dot com>
- To: "'Daniel Jacobowitz'" <drow at false dot org>
- Cc: "'Jeff Blaine'" <jblaine at kickflop dot net>, "'Mike Stump'" <mrs at apple dot com>, <gcc at gcc dot gnu dot org>
- Date: Wed, 4 Oct 2006 18:32:28 +0100
- Subject: RE: 4.1.1 spec files missing, FAQ misinformation
On 04 October 2006 18:19, Daniel Jacobowitz wrote:
> On Wed, Oct 04, 2006 at 06:01:19PM +0100, Dave Korn wrote:
>> On 04 October 2006 17:43, Jeff Blaine wrote:
>>
>>
>>> "This file can be found in the same directory that
>>> contains cc1 (run gcc -print-prog-name=cc1 to find it)."
>>>
>>> Finding the location of cc1 indicates libexec/blah/blah.
>>> Putting the specs file there does nothing.
>>>
>>> Tracing GCC, I found that it was looking for it in
>>> lib/blah/blah. Putting the specs file there works.
>>
>> I think that indicates someone trying to be overly clever when they
>> configured your gcc package. Normally libdir and libexecdir point to the
>> same dir. What output do you see from "gcc -v"?
>
> Not any more. The default changed some time ago. Some distributors
> configure them to the same location.
Oh, I didn't know. Guess I'm just stuck in the past :)
> Jeff, for background, up until a few releases ago cc1 and specs would
> always be in the same directory.
So, is it now guaranteed to belong in the libs dir? Does libgcc live in
libdir or libexecdir when they're different places? Maybe we can reword it
that way.
cheers,
DaveK
--
Can't think of a witty .sigline today....