From: Alexandre Oliva <aoliva@redhat.com>
To: gcc@gcc.gnu.org
Cc: ghazi@caip.rutgers.edu
Subject: Re: LD vs multilibs
Date: Mon, 08 Mar 2004 22:21:00 -0000 [thread overview]
Message-ID: <orn06rt1yz.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <20040308075134.GA30506@disaster.jaj.com>
On Mar 8, 2004, Phil Edwards <phil@jaj.com> wrote:
> Looking at this thread:
> http://gcc.gnu.org/ml/gcc/2003-09/msg00974.html
> Has been solved somewhere and I can't find it in the archives?
For the record from IRC discussion: the unsharing of config.cache
between different libs within a multilib may have hidden the problem,
but I'm pretty sure it hasn't been fixed.
--
Alexandre Oliva http://www.ic.unicamp.br/~oliva/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}
prev parent reply other threads:[~2004-03-08 22:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-08 7:51 Phil Edwards
2004-03-08 22:21 ` Alexandre Oliva [this message]
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=orn06rt1yz.fsf@free.redhat.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=ghazi@caip.rutgers.edu \
/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).