Hi.
My ‘downstream’ have a situation in which they make use of a directory outside
of the configured GCC installation - and symlink from there to libraries in the
actual install tree.
e.g.
/foo/bar/lib:
libgfortran.dylib -> /gcc/install/path/lib/libgfortran.dylib
Now I want to find a way fo
On 13 Apr 2010, at 19:05, Peter O'Gorman wrote:
gcc hello.c -g -o hc => dsymutils gets run (not expected from the
syntax, assuming that sources are irrelevant)
gcc hello.o -g -o hc => no dsymutils (expected from the absence of
'.o'
in the list)
We don't want to run dsymutil if there
On 04/12/2010 07:01 PM, IainS wrote:
>
> It clearly depends on something no-obvious.
>
> gcc hello.c -g -o hc => dsymutils gets run (not expected from the
> syntax, assuming that sources are irrelevant)
>
> gcc hello.o -g -o hc => no dsymutils (expected from the absence of '.o'
> in the lis
On 13 Apr 2010, at 00:22, Ian Lance Taylor wrote:
if you put "-lm" on the c/l dsymutil doesn't get called.
Note that in the specs language the %{.XXX: ...} is matched against
the filename passed to the gcc driver. It doesn't know the source
language of a .o file. So if you are linking, and p
IainS writes:
> FWIW I couldn't (quickly) find any other spec using that syntax - so
> perhaps it's not important.
There is an example of in java/lang-specs.h.
%{.class|.zip|.jar|!fsyntax-only:jc1 ...
Ian
On 13 Apr 2010, at 00:22, Ian Lance Taylor wrote:
IainS writes:
yeah .. we use it in Darwin's dsymutil spec.
%{!fdump=*:%{!fsyntax-only:%{!c:%{!M:%{!MM:%{!E:%{!S:\
%{.c|.cc|.C|.cpp|.cp|.c++|.cxx|.CPP|.m|.mm: \
%{gdwarf-2:%{!gstabs*:%{!g0: dsymutil %{o*:%*}%{!
o:a.out"
%{
IainS writes:
> yeah .. we use it in Darwin's dsymutil spec.
>
> %{!fdump=*:%{!fsyntax-only:%{!c:%{!M:%{!MM:%{!E:%{!S:\
> %{.c|.cc|.C|.cpp|.cp|.c++|.cxx|.CPP|.m|.mm: \
>%{gdwarf-2:%{!gstabs*:%{!g0: dsymutil %{o*:%*}%{!
> o:a.out"
> %{!A:%{!nostdlib:%{!nostartfiles:%E}}} %{
On 12 Apr 2010, at 23:24, Ian Lance Taylor wrote:
IainS writes:
what is the expected behavior of ?
%{.c|.cc|.for|.F90: foo }
.. as I read gcc/gcc.c I would expect to get "foo" for command lines
with files with these suffixes:
.c
.cc
.for
.F90
but not otherwise (since it says . binds more
IainS writes:
> what is the expected behavior of ?
>
> %{.c|.cc|.for|.F90: foo }
>
> .. as I read gcc/gcc.c I would expect to get "foo" for command lines
> with files with these suffixes:
> .c
> .cc
> .for
> .F90
>
> but not otherwise (since it says . binds more strongly than |) ;
That sounds ri
what is the expected behavior of ?
%{.c|.cc|.for|.F90: foo }
.. as I read gcc/gcc.c I would expect to get "foo" for command lines
with files with these suffixes:
.c
.cc
.for
.F90
but not otherwise (since it says . binds more strongly than |) ;
Iain
10 matches
Mail list logo
