help-octave
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: octave 3.6.2 build error: invalid preprocessing directive #!


From: Mike Miller
Subject: Re: octave 3.6.2 build error: invalid preprocessing directive #!
Date: Thu, 16 Aug 2012 13:43:01 -0700

On Thu, Aug 16, 2012 at 1:36 PM, Jordi Gutiérrez Hermoso wrote:
> On 16 August 2012 16:22, Richard <address@hidden> wrote:
>> On 16/08/2012 17:32, Jordi Gutiérrez Hermoso wrote:
>
>>> Can you please show me the output of the following commands?
>>>
>>>      echo '#include <map>' > foo.c++
>>>      cpp foo.c++
>>>      echo $CFLAGS
>>>      echo $CXXFLAGS
>>
>> Sorry for the delay, here's the output:
>>
>>
>> bash-4.1$ echo '#include <map>' > foo.c++
>> bash-4.1$ cpp foo.c++
>> # 1 "foo.c++"
>> # 1 "<built-in>"
>> # 1 "<command-line>"
>> # 1 "foo.c++"
>> # 1 "/usr/bin/map" 1 3
>> In file included from foo.c++:1:
>>
>> /usr/bin/map:1:2: error: invalid preprocessing directive #!
>
> Your gcc is broken. I don't know how, I don't know why, but your gcc
> thinks /usr/bin contains header files and it thinks /usr/bin/map is
> this header file:
>
>     http://www.cplusplus.com/reference/stl/map/
>
> I suppose the next thing to do is figure out who setup your system and
> tell them to fix it. You are unable to compile any C++ file that does
> "#include <map>".

Richard, try running

  g++ -v -E foo.c++

with the same file as above. The -v should print what directories g++
is searching for header files in, right near the top of the output,
here's what I see:

#include "..." search starts here:
#include <...> search starts here:
 /usr/include/c++/4.7
 /usr/include/c++/4.7/x86_64-linux-gnu
 /usr/include/c++/4.7/backward
 /usr/lib/gcc/x86_64-linux-gnu/4.7/include
 /usr/local/include
 /usr/lib/gcc/x86_64-linux-gnu/4.7/include-fixed
 /usr/include/x86_64-linux-gnu
 /usr/include
End of search list.

This should confirm whether it's a built-in misconfiguration of the
compiler or something else in your environment.

-- 
mike


reply via email to

[Prev in Thread] Current Thread [Next in Thread]