public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/46516] Non-multilib search problem in gcc.c / gfortran error: libgfortran.spec: No such file or directory
Date: Wed, 17 Nov 2010 11:57:00 -0000	[thread overview]
Message-ID: <bug-46516-4-np72CDjh3l@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46516-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46516

--- Comment #12 from joseph at codesourcery dot com <joseph at codesourcery dot com> 2010-11-17 11:55:29 UTC ---
In <http://gcc.gnu.org/ml/gcc-patches/2009-09/msg00826.html> I discussed 
issues relating to finding specs in the presence of multilib paths.  I 
hope this - and Nathan Froyd's patch linked from there in particular, 
which solved the libgomp.spec issue - helps provide a roadmap for 
resolving the present issue.


  parent reply	other threads:[~2010-11-17 11:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-17  7:04 [Bug driver/46516] New: gfortran-trunk: " Joost.VandeVondele at pci dot uzh.ch
2010-11-17  7:23 ` [Bug driver/46516] " Joost.VandeVondele at pci dot uzh.ch
2010-11-17  7:25 ` burnus at gcc dot gnu.org
2010-11-17  7:39 ` burnus at gcc dot gnu.org
2010-11-17  8:03 ` fxcoudert at gcc dot gnu.org
2010-11-17  8:20 ` Joost.VandeVondele at pci dot uzh.ch
2010-11-17  8:23 ` burnus at gcc dot gnu.org
2010-11-17  8:31 ` [Bug driver/46516] Non-multilib search problem in gcc.c / gfortran " burnus at gcc dot gnu.org
2010-11-17  8:46 ` burnus at gcc dot gnu.org
2010-11-17  8:50 ` Joost.VandeVondele at pci dot uzh.ch
2010-11-17  9:27 ` Joost.VandeVondele at pci dot uzh.ch
2010-11-17  9:33 ` burnus at gcc dot gnu.org
2010-11-17  9:45 ` burnus at gcc dot gnu.org
2010-11-17 11:57 ` joseph at codesourcery dot com [this message]
2010-11-17 15:33 ` burnus at gcc dot gnu.org
2010-11-17 16:26 ` burnus at gcc dot gnu.org
2010-11-18 10:24 ` burnus at gcc dot gnu.org
2010-11-18 14:40 ` burnus at gcc dot gnu.org
2010-11-21  8:01 ` burnus at gcc dot gnu.org
2010-11-21  8:06 ` burnus at gcc dot gnu.org

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=bug-46516-4-np72CDjh3l@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).