From: Andreas Jaeger <aj@suse.de>
To: Nathanael Nerode <neroden@twcny.rr.com>
Cc: gcc@gcc.gnu.org
Subject: Re: multilibbing libgfortran
Date: Sun, 03 Aug 2003 20:25:00 -0000 [thread overview]
Message-ID: <u8el024pyl.fsf@gromit.moeb> (raw)
In-Reply-To: <3F2D3DB6.5030007@twcny.rr.com> (Nathanael Nerode's message of "Sun, 03 Aug 2003 12:52:06 -0400")
[-- Attachment #1: Type: text/plain, Size: 1070 bytes --]
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
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2003-08-03 18:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-03 16:15 Nathanael Nerode
2003-08-03 16:20 ` Andreas Jaeger
2003-08-03 18:54 ` Nathanael Nerode
2003-08-03 20:25 ` Andreas Jaeger [this message]
2003-08-04 4:56 ` Phil Edwards
-- strict thread matches above, loose matches on Subject: below --
2003-08-03 12:30 Andreas Jaeger
2003-08-03 15:16 ` Alexandre Oliva
2003-08-03 16:12 ` Andreas Jaeger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=u8el024pyl.fsf@gromit.moeb \
--to=aj@suse.de \
--cc=gcc@gcc.gnu.org \
--cc=neroden@twcny.rr.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).