[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Using libtool even when not strictly needed
From: |
Thomas Jahns |
Subject: |
Using libtool even when not strictly needed |
Date: |
Mon, 26 Sep 2016 11:59:06 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.2.0 |
Hello,
I've run into the problem where a compiler we regularly use (NAG Fortran
compiler) has flag conventions that are at odds with libtool (i.e. nagfor uses
-Wc,opt to pass opt to the C compiler it uses as backend). For this reason I'd
like to add the compiler options to FCFLAGS in a form that's escaped for the
purposes of libtool, i.e. prefixed with -Xcompiler or -Xlinker.
This works well but at the moment requires me to override FCCOMPILE like this in
Makefile.am (note the -static flag):
FCCOMPILE = $(LIBTOOL) $(AM_V_lt) --tag=FC $(AM_LIBTOOLFLAGS) \
$(LIBTOOLFLAGS) --mode=compile $(FC) -static $(AM_FCFLAGS) $(FCFLAGS)
This way all compilations are passed through libtool and options are subjected
consistently to the same parsing sequence. I'm not sure how this would affect
people who want to build pie executables, but that's an issue for later.
Now the question remains, since FCCOMPILE is really something that automake
ought to setup properly and corresponding to automake version, how to achieve
the same in a more robust fashion?
Regards, Thomas
smime.p7s
Description: S/MIME Cryptographic Signature
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Using libtool even when not strictly needed,
Thomas Jahns <=