From: Timur Tabi <timur@freescale.com>
To: gcc-help@gcc.gnu.org
Subject: configure: error: cannot compute suffix of object files: cannot compile
Date: Sat, 18 Apr 2009 01:36:00 -0000 [thread overview]
Message-ID: <ed82fe3e0904171836j73fd91fudc6a9e45fe1a948b@mail.gmail.com> (raw)
I'm building gcc 4.3.3 on Mac OS X 10.5. binutils seems to build
fine, but gcc itself fails with this error:
checking whether ln -s works... yes
checking for powerpc-linux-gcc...
/Volumes/Goliath/Users/timur/dev/gcc-bin/./gcc/xgcc
-B/Volumes/Goliath/Users/timur/dev/gcc-bin/./gcc/
-B/usr/local/powerpc-linux/bin/ -B/usr/local/powerpc-linux/lib/
-isystem /usr/local/powerpc-linux/include -isystem
/usr/local/powerpc-linux/sys-include
checking for suffix of object files... configure: error: cannot
compute suffix of object files: cannot compile
See `config.log' for more details.
make[1]: *** [configure-target-libgcc] Error 1
make: *** [all] Error 2
A Google search of this error message shows several people with this
problem, mostly on Solaris, but no real solution.
--
Timur Tabi
Linux kernel developer at Freescale
next reply other threads:[~2009-04-18 1:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-18 1:36 Timur Tabi [this message]
2009-04-18 3:54 ` Timur Tabi
2013-05-10 14:19 YuGiOhJCJ Mailing-List
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=ed82fe3e0904171836j73fd91fudc6a9e45fe1a948b@mail.gmail.com \
--to=timur@freescale.com \
--cc=gcc-help@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).