public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tobi at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/18496] Build fails with "libgmp.so.6 not found" error Date: Thu, 02 Dec 2004 21:10:00 -0000 [thread overview] Message-ID: <20041202211012.3069.qmail@sourceware.org> (raw) In-Reply-To: <20041115062616.18496.jim@dishaw.org> ------- Additional Comments From tobi at gcc dot gnu dot org 2004-12-02 21:10 ------- Um, since I didn't reproduce the failure myself I'm not sure if I should have confirmed this bug. I don't see a way to set this back, so I'm going to have to leave this as confirmed. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18496
next prev parent reply other threads:[~2004-12-02 21:10 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-11-15 6:26 [Bug libfortran/18496] New: " jim at dishaw dot org 2004-11-15 14:12 ` [Bug libfortran/18496] " pinskia at gcc dot gnu dot org 2004-11-15 14:13 ` [Bug fortran/18496] " pinskia at gcc dot gnu dot org 2004-11-15 21:55 ` jim at dishaw dot org 2004-11-16 2:41 ` jim at dishaw dot org 2004-12-02 21:08 ` tobi at gcc dot gnu dot org 2004-12-02 21:10 ` tobi at gcc dot gnu dot org [this message] [not found] <bug-18496-9557@http.gcc.gnu.org/bugzilla/> 2005-11-04 17:55 ` fxcoudert at gcc dot gnu dot 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=20041202211012.3069.qmail@sourceware.org \ --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).