public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "Joost.VandeVondele at pci dot uzh.ch" <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 08:50:00 -0000 [thread overview] Message-ID: <bug-46516-4-YhaW8OSVYg@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 #8 from Joost VandeVondele <Joost.VandeVondele at pci dot uzh.ch> 2010-11-17 08:46:11 UTC --- mine look like: static const char *const multilib_raw[] = { ". !m64 !m32;", ".:../lib64 m64 !m32;", ".:../lib !m64 m32;", NULL }; however, I just observe that the libgomp.spec are causing no problems in my build.
next prev parent reply other threads:[~2010-11-17 8:46 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 [this message] 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 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-YhaW8OSVYg@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: linkBe 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).