public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joel at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/55790] Build Failure on Head Targeting x86_64 Linux
Date: Mon, 07 Jan 2013 17:07:00 -0000	[thread overview]
Message-ID: <bug-55790-4-pCrAhPprlR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55790-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #2 from Joel Sherrill <joel at gcc dot gnu.org> 2013-01-07 17:07:05 UTC ---
The gcc dependencies are reminding me of the pre-egcs days. I hope we don't
return there. :(

Anyway.. These are the sources I have linked into today's gcc-svn. This is what
I had been using over the holidays to test using Centos 6.x. But this isn't
working on a Fedora host. 

$ ls -l | grep " -> "
lrwxrwxrwx  1 joel rtems      33 Jan  7 10:03 cloog ->
/users/joel/test-gcc/cloog-0.17.0
lrwxrwxrwx  1 joel rtems      29 Dec 22 10:15 gmp ->
/home/joel/test-gcc/gmp-5.1.0
lrwxrwxrwx  1 joel rtems      28 Dec 22 10:16 isl ->
/home/joel/test-gcc/isl-0.10
lrwxrwxrwx  1 joel rtems      44 Oct 28  2011 libgloss ->
/users/joel/test-gcc/newlib-cvs/src/libgloss
lrwxrwxrwx  1 joel rtems      29 Dec 22 10:14 mpc ->
/home/joel/test-gcc/mpc-1.0.1
lrwxrwxrwx  1 joel rtems      30 Dec 22 10:13 mpfr ->
/home/joel/test-gcc/mpfr-3.1.1
lrwxrwxrwx  1 joel rtems      42 Oct 28  2011 newlib ->
/users/joel/test-gcc/newlib-cvs/src/newlib

Do you have to use any special configure option when using these sources inside
the gcc tree?


  parent reply	other threads:[~2013-01-07 17:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-22 16:24 [Bug bootstrap/55790] New: " joel at gcc dot gnu.org
2012-12-31 16:15 ` [Bug bootstrap/55790] " rguenth at gcc dot gnu.org
2013-01-07 17:07 ` joel at gcc dot gnu.org [this message]
2013-01-07 17:40 ` joel at gcc dot gnu.org
2013-01-08  9:58 ` rguenth at gcc dot gnu.org
2013-01-08 20:33 ` joel 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-55790-4-pCrAhPprlR@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).