Re: -Bstatic and -Bdynamic flags when checking fortran compiler libraries

[Christopher Hulbert]

On Thu, Jan 22, 2009 at 11:33 PM, Eric Blake <address@hidden> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> According to Christopher Hulbert on 1/22/2009 8:56 AM:
>> I have a case where I want to statically link the compiler libraries.
>> In this case, the PGI compiler provides the -Bstatic_pgi flag which
>> adds '-Bstatic' in front of its libraries. This information is lost,
>> and the compiler does not check for its own libraries on the compile
>> line to add the flag in front of. The attached patch adds cases for
>> the '-Bstatic' and '-Bdynamic' flags in the _AC_FC_LIBRARY_LDFLAGS
>> macro. Is there any chance of getting this in?
>
> I'm not familiar with Fortran, so I'm hoping someone else will chime in.
> But off-hand, I don't see any reason against applying it, so even if no
> one else responds, I will probably add it after a few days of waiting.
>
> By the way, can you convince your mailer to send patches in a text MIME
> type, instead of application/octet-stream?  It makes reviewing easier.
> Also, providing a ChangeLog entry speeds up the process.

Sorry about that. I do not use Google's mail much for sending
messages. I will try to pay extra attention to the MIME type next
time.

Chris

>
> - --
> Don't work too hard, make some time for fun as well!
>
> Eric Blake             address@hidden
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (Cygwin)
> Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iEYEARECAAYFAkl5SJcACgkQ84KuGfSFAYD6/gCfSnWZNK3/KrZIK6eHhn/V3QeI
> 4LkAnRDMmOXe24yGvsnC1/Cd7bfGIrwx
> =35DK
> -----END PGP SIGNATURE-----
>