Ralf Wildenhues wrote:
>>> Independently, does anybody know whether odcctools is dead (homepage
>>> seems to be down ATM)?
odcctools is currently seeking a maintainer.
Peter
--
Peter O'Gorman
http://pogma.com
On 10 Jun 2008, at 20:58, Ralf Wildenhues wrote:
* IainS wrote on Tue, Jun 10, 2008 at 09:42:29PM CEST:
On 10 Jun 2008, at 20:06, Ralf Wildenhues wrote:
Can the driver use path/to/libgfortran.a instead of '-Lpath/to
-lgfortran' to avoid being hindered by missing -Bstatic/-Bdynamic?
this do
We're getting a bit off-list; if this loses connection to GCC we may
want to move to [EMAIL PROTECTED]
* IainS wrote on Tue, Jun 10, 2008 at 09:42:29PM CEST:
> On 10 Jun 2008, at 20:06, Ralf Wildenhues wrote:
>>
>> It doesn't do that because that breaks the abstraction. It might also
>> increase
* IainS wrote on Tue, Jun 10, 2008 at 09:42:29PM CEST:
> On 10 Jun 2008, at 20:06, Ralf Wildenhues wrote:
>
>> Can the driver use path/to/libgfortran.a instead of '-Lpath/to
>> -lgfortran' to avoid being hindered by missing -Bstatic/-Bdynamic?
>
> this doesn't appear to work. [I've unset DYLD_LIBRA
On 10 Jun 2008, at 20:06, Ralf Wildenhues wrote:
Hello,
* FX wrote on Tue, Jun 10, 2008 at 05:59:36PM CEST:
De : IainS <[EMAIL PROTECTED]>
I opted to call the static library "libgfortran_static" and to leave
the shared name unchanged.
It would be great if libtool could be persuaded to chang
Hello,
* FX wrote on Tue, Jun 10, 2008 at 05:59:36PM CEST:
>> De : IainS <[EMAIL PROTECTED]>
>>
>> I opted to call the static library "libgfortran_static" and to leave
>> the shared name unchanged.
>>
>> It would be great if libtool could be persuaded to change the basename
>> as well as the ext
FX wrote on 10 June 2008 17:12:
>> The solution is to name the libs differently (as is done elsewhere
>> in gcc).
>
> Target libraries named differently? Which?
Just frex: When you build static libgcc, you get libgcc.a
When you build it shared, you get libgcc_s.so (and a static libgcc_eh.
On 10 Jun 2008, at 17:11, FX wrote:
I opted to call the static library "libgfortran_static" and to
leave the shared name unchanged.
I'd suggest "-static" instead of using an underscore, to follow
libstdc++, but that's a minor point.
A minor point maybe, but, as you say, there seem to be
The solution is to name the libs differently (as is done elsewhere
in gcc).
Target libraries named differently? Which? libssp has three variants,
which I don't really understand :)
$ ls libssp*
libssp.0.dylib libssp.dyliblibssp_nonshared.a
libssp.alibssp.la
0:11 GMT+01:00
À : Fortran List <[EMAIL PROTECTED]>
Objet : [RFC, Patch, gfortran] make -static-libgfortran work on
darwin.
The current implementation of -static-libgfortran has no effect on
darwin{8,9}
[http://gcc.gnu.org/ml/fortran/2008-05/msg00365.html, http://
gcc.gnu.org/ml/fortran
10 matches
Mail list logo
