This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: gcc/g++ don't work in home folder


2013/2/9 Mahmood Naderan <nt_mahmood@yahoo.com>:
> Hi
[deleted]
>
> I don't know what happened to my ubuntu 12.04, that when I run "g++" command in the home folder, I get weird response
>
>     mahmood@pc:~$ g++ -v
>     Reading specs from ./specs
>     g++: ./specs: Is a directory
>
>     mahmood@pc:~$ /usr/bin/gcc-4.4 -v
>     Reading specs from ./specs
>     gcc-4.4: ./specs: Is a directory
>
>     mahmood@pc:~$ /usr/bin/g++-4.6
>     g++-4.6: error: ./specs: Is a directory
>
>
> 'specs' is a folder in my home. However when I run the same command in another folder (~/trunk), there is no problem.
>
[deleted]
>
> This is the first time I see such a problem.
>
> Regards,
> Mahmood

Hi, Mahmood,

GCC uses specs mechanism to invoke a sequence of other programs for
entire compilation work. About specs syntax, see Chapter 3-15 of
GCC Manual for more information.

Generally, it uses builtin specs which is already compiled inside 'gcc' driver.
But it also provide a chance that users can dynamically apply their own specs
without rebuilding gcc program.

In your case, gcc/g++ detected 'specs' appears under your working directory
so it tried to read specs syntax from it but failed.


Best regards,
jasonwucj


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]