multilibbing libgfortran

[Andreas Jaeger]

Nathanael Nerode <neroden@twcny.rr.com> writes:

> Andreas Jaeger wrote:
>> Nathanael Nerode <neroden@twcny.rr.com> writes:
>> Unfortunately exact enough - but too late.  I'd prefer to have
>> libgfortran earlier multi-libbed if possible so that it can get better
>> tested.
>> So, what needs to be done to get this multi-libbed?  I tried copying
>> some stuff from libstdc++-v3 and failed with automake problems :-(
>> Andreas
>
> The current multilibbing scheme is demented, in my opinion.  I still
> recommend not multilibbing at the moment; when multilibbing is moved
> to the top level, you'll have to rip all the multilib code back *out*
> of gfortran.  You can still test gfortran with each individual library

I see.

> configuration directly, you know, right?

No, I don't know how I can build on x86_64 a 32-bit multilib directly.

Andreas
-- 
 Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj
  SuSE Linux AG, Deutschherrnstr. 15-19, 90429 Nürnberg, Germany
   GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <https://gcc.gnu.org/pipermail/gcc/attachments/20030803/8c0e2aaf/attachment.sig>