public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mexas at bristol dot ac.uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/46086] fail to build gcc 4.5.2 on sparc64-portbld-freebsd9.0 - configure: error: cannot compute suffix of object files: cannot compile
Date: Tue, 19 Oct 2010 21:10:00 -0000	[thread overview]
Message-ID: <20101019211000.aqItqu4myfjSQ3RkilDWP60ivB213m5BiUSSfF-7-rU@z> (raw)
In-Reply-To: <bug-46086-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Anton Shterenlikht <mexas at bristol dot ac.uk> 2010-10-19 21:10:00 UTC ---
yes

I've repeated it maybe 5-10 times over the last several weeks.

I don't know if this is a regression. I think lapack dependency
in freebsd ports recently moved from gcc44 to gcc45, so
probably I haven't tried to build gcc45 until a few weeks ago.


  parent reply	other threads:[~2010-10-19 21:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-19 21:04 [Bug c/46086] New: " mexas at bristol dot ac.uk
2010-10-19 21:06 ` [Bug c/46086] " pinskia at gcc dot gnu.org
2010-10-19 21:10 ` mexas at bristol dot ac.uk [this message]
2010-10-19 21:21 ` [Bug bootstrap/46086] " ebotcazou at gcc dot gnu.org
2010-10-19 22:08 ` mexas at bristol dot ac.uk
2010-10-20  7:26 ` ebotcazou at gcc dot gnu.org
2010-11-02 13:49 ` ebotcazou at gcc dot gnu.org
2010-11-16 13:36 ` mexas at bristol dot ac.uk
2010-11-16 13:40 ` redi at gcc dot gnu.org
2010-11-16 13:46 ` mexas at bristol dot ac.uk
2010-11-16 13:50 ` mexas at bristol dot ac.uk
2010-11-16 17:33 ` ebotcazou at gcc dot gnu.org
2010-11-17 15:12 ` mexas at bristol dot ac.uk
2010-12-25  9:21 ` mexas at bristol dot ac.uk

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=20101019211000.aqItqu4myfjSQ3RkilDWP60ivB213m5BiUSSfF-7-rU@z \
    --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).