public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bonzini at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/24297] [4.1 Regression] libtool: link: unable to infer tagged configuration
Date: Wed, 12 Oct 2005 12:17:00 -0000 [thread overview]
Message-ID: <20051012121710.4712.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24297-276@http.gcc.gnu.org/bugzilla/>
------- Comment #8 from bonzini at gcc dot gnu dot org 2005-10-12 12:17 -------
Created an attachment (id=9976)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=9976&action=view)
patch to be "optimistic" about which tool to use
Can you guys please test the attached patch?
--
bonzini at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|unassigned at gcc dot gnu |bonzini at gcc dot gnu dot
|dot org |org
Status|NEW |ASSIGNED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24297
next prev parent reply other threads:[~2005-10-12 12:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-10 16:08 [Bug bootstrap/24297] New: " danglin at gcc dot gnu dot org
2005-10-10 16:31 ` [Bug boehm-gc/24297] " ebotcazou at gcc dot gnu dot org
2005-10-10 16:49 ` [Bug boehm-gc/24297] [4.1 Regression] " pinskia at gcc dot gnu dot org
2005-10-10 16:51 ` pinskia at gcc dot gnu dot org
2005-10-10 16:51 ` pinskia at gcc dot gnu dot org
2005-10-10 16:53 ` pinskia at gcc dot gnu dot org
2005-10-11 16:30 ` [Bug bootstrap/24297] " bonzini at gcc dot gnu dot org
2005-10-12 8:46 ` bonzini at gcc dot gnu dot org
2005-10-12 12:17 ` bonzini at gcc dot gnu dot org [this message]
2005-10-19 20:32 ` bonzini at gcc dot gnu dot org
2005-10-22 10:37 ` cvs-commit at gcc dot gnu dot org
2005-10-22 10:38 ` bonzini 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=20051012121710.4712.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: 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).