public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/54415] GCC 4.4.4 build fails on solaris sparc with error as undefined reference to `_Qp_xtoq'
Date: Sat, 01 Sep 2012 15:19:00 -0000 [thread overview]
Message-ID: <bug-54415-4-E0im7toPjg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54415-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54415
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |ebotcazou at gcc dot
| |gnu.org
Resolution| |WORKSFORME
--- Comment #1 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2012-09-01 15:19:28 UTC ---
> Building 64bit gcc-4.4.4 on solaris 10 sparc machine. Configured successfully
> but fails while executing 'make' command.
>
> Steps to produce:
>
> # pwd
> /els/install/gcc-4.4.4_64/build_64
>
> Configures command:
> # ../gcc-4.4.4/configure --prefix=/usr/local/gcc-4.4.4_64
> --with-gmp=/els/install/gcc-4.4.4_64/gmp32
> --with-mpfr=/els/install/gcc-4.4.4_64/mpfr32 --build=sparcv9-sun-solaris2.10
> --enable-languages=c,c++ --with-gnu-as --with-gnu-ld
As documented, do not use a relative path to 'configure'. And if the base
compiler is 32-bit, you need to add CC="gcc -m64" on the configure line.
next prev parent reply other threads:[~2012-09-01 15:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-30 9:09 [Bug bootstrap/54415] New: " birender.singh at hotmail dot com
2012-09-01 15:19 ` ebotcazou at gcc dot gnu.org [this message]
2012-09-03 6:31 ` [Bug bootstrap/54415] " birender.singh at hotmail dot com
2012-09-03 6:35 ` birender.singh at hotmail dot com
2012-09-03 8:21 ` ebotcazou 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-54415-4-E0im7toPjg@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).