public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jcea at jcea dot es" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/65988] Trying to compile GCC 5.1 in my (customized) Solaris 10/x86-64 fails with GMP errors
Date: Wed, 08 Jul 2015 02:25:00 -0000	[thread overview]
Message-ID: <bug-65988-4-5UqGRnA9Fc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65988-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65988

Jesus Cea <jcea at jcea dot es> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |WORKSFORME

--- Comment #7 from Jesus Cea <jcea at jcea dot es> ---
I tried to compile GCC 4.9.3 and I was unable, too. Different error but same
result. I recompiled GCC 4.9.2 and it worked.

I messed with different versions of "CLOOG" and "ISL" and I got GCC 4.9.3 and
5.1.0 working correctly.

I am currently using GCC 5.1.0 and compiling with it seems to work well. I
compiled Python, bind, etc., and it works.

I close this but report, but I would love future GCC releases to document what
CLOOG and ISL versions they require.

Thanks for your time.


  parent reply	other threads:[~2015-07-08  2:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-65988-4@http.gcc.gnu.org/bugzilla/>
2015-05-03  8:16 ` glisse at gcc dot gnu.org
2015-06-08 14:56 ` jcea at jcea dot es
2015-06-08 15:12 ` redi at gcc dot gnu.org
2015-06-08 16:06 ` jcea at jcea dot es
2015-07-02 10:04 ` manu at gcc dot gnu.org
2015-07-08  2:25 ` jcea at jcea dot es [this message]
2015-07-08  7:46 ` redi 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-65988-4-5UqGRnA9Fc@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).