public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gbarnt at student dot dtu dot dk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/36481] gcc fails to build on Solaris x86 - it forgets the locations of libmpfr
Date: Fri, 01 May 2009 09:01:00 -0000	[thread overview]
Message-ID: <20090501090104.30301.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36481-16025@http.gcc.gnu.org/bugzilla/>



------- Comment #10 from gbarnt at student dot dtu dot dk  2009-05-01 09:01 -------
In reply to #9:

I have tried to build gcc with and without my own patch on our solaris
machines. While both of them fails they fail at the same place (namely
configuration of [arch]/libgcc trying to figure out the object suffix). They do
however die of different reasons (the patched dies due to xgcc seg. faulting
and the unpatched dies because cc1 is unable to locate libmpfr), but that is a
different matter and probably also another bug-thread.

I checked the "build-[arch]/fixincludes" and I cannot see a different between
the patched and the unpatched prior to line 51. Of course these files are
auto-generated, so ... I did however notice that line 50 is the first line in
the make file to use ":=" rather than "=" (both in patched and unpatched
version).

  target = sparc-sun-solaris2.10
  target_noncanonical:=sparc-sun-solaris2.10

Then I realized that we have a GNU Make installed, which I have been using. If
I use a non-GNU make it also fails with that error in that directory. 

  make: Fatal error in reader: Makefile, line 51: Unexpected end of line seen

Nevertheless it also dies in the unpatched version - same place, same error.
(NB: For this test I did not rebuild, I just ran the other make in that dir.)

Opening the Makefile and replacing the ":=" with "=" seems remove the
"Unexpected end of line seen". The other issue you met does not go away though.
But I get this issue with two out of the 4 different "make"s we have installed.
The two succeeding are different version of the GNU make and the failing onces
are (probably) not GNU make (they do not understand --version and -v is
interpreted as something else ... probably verbose).

Nevertheless, from what I can see your issue is likely to originate from a
syntax issue with the Makefile. Since my patch requires running autoconf, the
issue might be that the version of autoconf you used was designed to work with
a newer version of make than the ones failing. My suggestion is to try using an
older autoconf or a newer make or/and a GNU make.

Sorry for the late reply by the way. Hope it helps.

~Niels


-- 


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


  parent reply	other threads:[~2009-05-01  9:01 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-09 23:28 [Bug c/36481] New: " david dot kirkby at onetel dot net
2008-06-10  8:53 ` [Bug bootstrap/36481] " pinskia at gcc dot gnu dot org
2008-06-10 22:37 ` david dot kirkby at onetel dot net
2008-07-02  1:00 ` BlanchardJ at ieee dot org
2009-03-23 17:23 ` gbarnt at student dot dtu dot dk
2009-03-23 17:23 ` gbarnt at student dot dtu dot dk
2009-03-23 18:38 ` gbarnt at student dot dtu dot dk
2009-03-23 18:43 ` gbarnt at student dot dtu dot dk
2009-03-24 17:47 ` rwild at gcc dot gnu dot org
2009-04-16  6:41 ` sebastian dot wenzler at hp dot com
2009-05-01  9:01 ` gbarnt at student dot dtu dot dk [this message]
2009-05-01  9:51 ` schwab at linux-m68k dot org
2010-01-14 10:04 ` abhishekfishy2000 at gmail dot com
2010-01-14 10:06 ` abhishekfishy2000 at gmail dot com
2010-01-15  4:44 ` david dot kirkby at onetel dot net
2010-01-15  5:12 ` BlanchardJ at ieee dot org
2010-01-15  9:59 ` david dot kirkby at onetel dot net
2010-01-15 12:37 ` BlanchardJ at ieee dot org
2010-01-15 13:15 ` david dot kirkby at onetel dot net
     [not found] <bug-36481-4@http.gcc.gnu.org/bugzilla/>
2012-01-28  5:28 ` pinskia 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=20090501090104.30301.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).