wrong GCC-configuration? (./specs: Is a directory)

wrong GCC-configuration? (./specs: Is a directory)

[Karl Krach]

[-- Attachment #1: Type: text/plain, Size: 2340 bytes --]

Hi!

I'm a Gentoo user and tried to emerge k3b and got stuck while installing 
the necessary app-cdr/cdrdao-1.2.1-r1 package:

     [...]
     checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc
     checking for C compiler default output file name...
             configure: error: *C compiler cannot create executables*
     See `config.log' for more details.
     [...]
     !!! ERROR: app-cdr/cdrdao-1.2.1-r1 failed.

In the config.log the interesting part is

     configure:2357: x86_64-pc-linux-gnu-gcc -v </dev/null >&5
     Reading specs from ./specs
     x86_64-pc-linux-gnu-gcc: *./specs: Is a directory*
     configure:2360: $? = 1
     configure:2362: x86_64-pc-linux-gnu-gcc -V </dev/null >&5
     x86_64-pc-linux-gnu-gcc: '-V' option must have argument
     configure:2365: $? = 1
     configure:2388: checking for C compiler default output file name
     configure:2391: x86_64-pc-linux-gnu-gcc -march=k8 -pipe
                 -O2 -fno-inline conftest.c >&5
     x86_64-pc-linux-gnu-gcc: *./specs: Is a directory*
     configure:2394: $? = 1
     [...]
     configure:2433: error: C compiler cannot create executables

What I figured out: My problem is that my GCC reads the specs from the 
current directory (if available). To demonstrate this:

     bluespirit tmp # ls
     bluespirit tmp # gcc -v
     *Reading specs from /usr/lib/gcc/x86_64-pc-linux-gnu/4.1.1/specs*
     Target: x86_64-pc-linux-gnu
     [...]
     gcc version 4.1.1 (Gentoo 4.1.1-r3)
     bluespirit tmp # touch specs
     bluespirit tmp # gcc -v
     *Reading specs from ./specs*
     gcc: unrecognized option '-v'
     gcc: unrecognized option '-mtune=k8'
     Target: x86_64-pc-linux-gnu
     [...]
     gcc version 4.1.1 (Gentoo 4.1.1-r3)
     bluespirit tmp # rm specs
     bluespirit tmp # mkdir specs
     bluespirit tmp # gcc -v
     *Reading specs from ./specs*
     gcc: ./specs: Is a directory
     bluespirit tmp # unset GCC_SPECS
     bluespirit tmp # gcc -v
     *Reading specs from ./specs*
     gcc: ./specs: Is a directory
     bluespirit tmp #

How can I teach my GCC to use ONLY the given specs - and ignore the 
directory specs (which exists in the cdrdao-folder). In my opinion, I 
use the Gentoo settings for the GCC - so I'm wondering, why this error 
is so rarely documented in the web.

Thanks in advance,
Charly

[-- Attachment #2: gcc.v.txt --]
[-- Type: text/plain, Size: 1016 bytes --]

Reading specs from /usr/lib/gcc/x86_64-pc-linux-gnu/4.1.1/specs
Target: x86_64-pc-linux-gnu
Configured with: /var/tmp/portage/gcc-4.1.1-r3/work/gcc-4.1.1/configure --prefix=/usr --bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/4.1.1 --includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.1.1/include --datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.1.1 --mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.1.1/man --infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.1.1/info --with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.1.1/include/g++-v4 --host=x86_64-pc-linux-gnu --build=x86_64-pc-linux-gnu --disable-altivec --enable-nls --without-included-gettext --with-system-zlib --disable-checking --disable-werror --enable-secureplt --disable-libunwind-exceptions --enable-multilib --disable-libmudflap --disable-libssp --enable-java-awt=gtk --enable-languages=c,c++,java,objc,fortran --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu
Thread model: posix
gcc version 4.1.1 (Gentoo 4.1.1-r3)

Re: wrong GCC-configuration? (./specs: Is a directory)

[Ian Lance Taylor]

Karl Krach <mailinglists@blueSpirit.la> writes:

> What I figured out: My problem is that my GCC reads the specs from the
> current directory (if available).

This is not normal behaviour.  There is something odd about your GCC.
Or you've done something like set the environment variable
GCC_EXEC_PREFIX to ".".

Ian

Re: wrong GCC-configuration? (./specs: Is a directory)

[Karl Krach]

Ian Lance Taylor wrote:
> Karl Krach <mailinglists@blueSpirit.la> writes:
> 
>> What I figured out: My problem is that my GCC reads the specs from the
>> current directory (if available).
> 
> This is not normal behaviour.  There is something odd about your GCC.
> Or you've done something like set the environment variable
> GCC_EXEC_PREFIX to ".".

I've already checked all environment variables. There is only $GCC_SPECS 
and it's empty. But this variable (if empty) has no effect to GCC's 
behavior.

> 
> Ian
> 

And yes, I'm also sure that it's not the normal behavior. But I've no 
idea which parameters to change.

Thanks,
Charly

Re: wrong GCC-configuration? (./specs: Is a directory)

[Ian Lance Taylor]

Karl Krach <mailinglists@blueSpirit.la> writes:

> Ian Lance Taylor wrote:
> > Karl Krach <mailinglists@blueSpirit.la> writes:
> >
> >> What I figured out: My problem is that my GCC reads the specs from the
> >> current directory (if available).
> > This is not normal behaviour.  There is something odd about your GCC.
> > Or you've done something like set the environment variable
> > GCC_EXEC_PREFIX to ".".
> 
> I've already checked all environment variables. There is only
> $GCC_SPECS and it's empty. But this variable (if empty) has no effect
> to GCC's behavior.

GCC_SPECS does nothing with standard gcc.

> And yes, I'm also sure that it's not the normal behavior. But I've no
> idea which parameters to change.

I think you must be using patched source code.  I have no other way of
explaining what you are seeing.  Well, maybe you configured gcc with
"--prefix=." but that would probably cause other problems.

Ian

Re: wrong GCC-configuration? (./specs: Is a directory)

[Steve Kreyer]

[-- Attachment #1: Type: text/plain, Size: 1482 bytes --]

Hi,

only a guess:
Can it be, that gcc searches also in LIBRARY_PATH for the specs file ?
If so, maybe you have to check your LIBRARY_PATH environment variable,
if this contains a fullstop. Or maybe just play with it and find out how
gcc behaves to the content of this variable. Maybe you should set it to
/usr/lib/gcc/target/gcc-version directory, if this is the directory
where your default specs file is located.

Regards,
Steve

Ian Lance Taylor wrote:
> Karl Krach <mailinglists@blueSpirit.la> writes:
>
>   
>> Ian Lance Taylor wrote:
>>     
>>> Karl Krach <mailinglists@blueSpirit.la> writes:
>>>
>>>       
>>>> What I figured out: My problem is that my GCC reads the specs from the
>>>> current directory (if available).
>>>>         
>>> This is not normal behaviour.  There is something odd about your GCC.
>>> Or you've done something like set the environment variable
>>> GCC_EXEC_PREFIX to ".".
>>>       
>> I've already checked all environment variables. There is only
>> $GCC_SPECS and it's empty. But this variable (if empty) has no effect
>> to GCC's behavior.
>>     
>
> GCC_SPECS does nothing with standard gcc.
>
>   
>> And yes, I'm also sure that it's not the normal behavior. But I've no
>> idea which parameters to change.
>>     
>
> I think you must be using patched source code.  I have no other way of
> explaining what you are seeing.  Well, maybe you configured gcc with
> "--prefix=." but that would probably cause other problems.
>
> Ian
>
>   


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3245 bytes --]