public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "markus at trippelsdorf dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/50952] libquad relocation R_X86_64_32S failure
Date: Wed, 02 Nov 2011 05:56:00 -0000 [thread overview]
Message-ID: <bug-50952-4-lVV51pMh7B@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50952-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50952
Markus Trippelsdorf <markus at trippelsdorf dot de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |markus at trippelsdorf dot
| |de
--- Comment #5 from Markus Trippelsdorf <markus at trippelsdorf dot de> 2011-11-02 05:56:14 UTC ---
(In reply to comment #4)
> (In reply to comment #3)
> > It looks like a problem with libquadmath/configure. I recently
> > updated by bleeding edge freebsd system to FreeBSD 10.0, and
> > it looks like configure can't handle the new version number.
> >
>
> > configure: freebsd[123]*) objformat=aout ;;
> > configure: version_type=freebsd-$objformat
> > configure: freebsd-elf*)
> > configure: freebsd-*)
> > configure: freebsd2*)
> > configure: freebsd3.[01]* | freebsdelf3.[01]*)
> > configure: freebsd3.[2-9]* | freebsdelf3.[2-9]* | \
> > configure: freebsd4.[0-5] | freebsdelf4.[0-5] | freebsd4.1.1 |
> > freebsdelf4.1.1)
> > configure: version_type=freebsd-elf
> >
> > I'm suspicious that the 'freebsd[123]*) objformat=aout ;;' is now bogus.
>
> A quick hack to remove the 1 in the above line allows me
> to configure, build, and install gcc/gfortran.
>
> Anyone know how to fix this issue properly?
Yes, just update in-tree libtool:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50952
next prev parent reply other threads:[~2011-11-02 5:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-01 22:42 [Bug bootstrap/50952] New: " kargl at gcc dot gnu.org
2011-11-01 22:43 ` [Bug bootstrap/50952] " kargl at gcc dot gnu.org
2011-11-01 22:44 ` kargl at gcc dot gnu.org
2011-11-01 22:53 ` kargl at gcc dot gnu.org
2011-11-01 23:03 ` [Bug target/50952] " kargl at gcc dot gnu.org
2011-11-02 5:56 ` markus at trippelsdorf dot de [this message]
2011-11-02 5:57 ` markus at trippelsdorf dot de
2011-11-04 23:01 ` sgk at troutmask dot apl.washington.edu
2011-12-15 0:20 ` pinskia at gcc dot gnu.org
2011-12-15 1:37 ` sgk at troutmask dot apl.washington.edu
2011-12-15 1:38 ` pinskia at gcc dot gnu.org
2011-12-15 16:46 ` kargl 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-50952-4-lVV51pMh7B@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).