* FX wrote on Fri, Sep 10, 2010 at 07:08:10PM CEST:
> I'm CC'ing the gcc list so I can get insight from people who
> understand correctly how static libraries should be handled by the
> driver...
>
> > I'm seeing a similar issue with -static linkage.
> >
> > % gfc4x -o z norm2_3.f90 -L/usr/home/s
Il 11/09/2010 1.42, Steve Kargl ha scritto:
On Sat, Sep 11, 2010 at 01:05:23AM +0200, Angelo Graziosi wrote:
Il 10/09/2010 19.31, Steve Kargl ha scritto:
The ideal solution would be incorporating libquad into libgfortran
The ideal solution would be building GCC enabling QP with
./configure..
On Sat, Sep 11, 2010 at 01:05:23AM +0200, Angelo Graziosi wrote:
> Il 10/09/2010 19.31, Steve Kargl ha scritto:
> >The ideal solution would be incorporating libquad into libgfortran
>
> The ideal solution would be building GCC enabling QP with
>
> ./configure... --enable-quad
>
> if the syst
Il 10/09/2010 19.31, Steve Kargl ha scritto:
The ideal solution would be incorporating libquad into libgfortran
The ideal solution would be building GCC enabling QP with
./configure... --enable-quad
if the system allow for QP: in this case, perhaps, QP should be enabled
by default.
Cia
On Fri, Sep 10, 2010 at 07:08:10PM +0200, FX wrote:
> I'm CC'ing the gcc list so I can get insight from people who understand
> correctly how static libraries should be handled by the driver...
>
> > I'm seeing a similar issue with -static linkage.
> >
> > % gfc4x -o z norm2_3.f90 -L/usr/home/sg
I'm CC'ing the gcc list so I can get insight from people who understand
correctly how static libraries should be handled by the driver...
> I'm seeing a similar issue with -static linkage.
>
> % gfc4x -o z norm2_3.f90 -L/usr/home/sgk/work/lib -lquad -static
OK, I see the same thing. It's due to
