From: Kai Ruottu <kai.ruottu@wippies.com>
To: Timur Tabi <timur@freescale.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Error building on OS X
Date: Thu, 16 Apr 2009 06:42:00 -0000 [thread overview]
Message-ID: <49E6D3A0.7060502@wippies.com> (raw)
In-Reply-To: <ed82fe3e0904151807g70175c8fx8c438076b284977f@mail.gmail.com>
Timur Tabi wrote:
> I'm trying to build a PowerPC-targeted gcc (4.3.3) on a PowerPC OS X
> 10.5 system. I have the latest Xcode installed, which comes with gcc
> 4.0 and 4.2. The reason I'm doing this is because I want to build a
> 4.3-based toolchain that can generate Linux binaries for PowerPC
> embedded systems.
>
> Unfortunately, I'm not getting very far at all. When I run this command:
>
> ./gcc-4.3.3/configure --target=powerpc-linux --program-prefix=powerpc-
>
> I get this error:
>
> checking for C compiler default output file name... configure: error:
> C compiler cannot create executables
Producing GCC binaries requires a working C toolchain (C compiler, C
library, assembler, linker,...) for the "host" system, in your case
for OS X 10.5! The GCC "sources" are mostly in 'C' language, so a
working C compiler for the host is required to compile them. In order
to make the executables for the "OS X to Linux/PPC" crosscompiler,
producing executables for OS X 10.5 MUST work !
The error tells that now you cannot produce any executables for OS X
10.5 with the installed "Xcode" (what on earth is that?) !
> and config.log says this:
>
> configure:3194: checking for C compiler default output file name
> configure:3197: gcc conftest.c >&5
> /usr/libexec/gcc/powerpc-apple-darwin9/4.0.1/ld: warning unknown
> -macosx_version_min parameter value: 10.5.6 ignored (using 10.1)
This says "powerpc-apple-darwin9"... Is that really the same thing
as "a PowerPC OS X 10.5 system" ? Ie do you really have GCC etc
made for OS X 10.5 ? Not one made for OS X 9.x ?
next prev parent reply other threads:[~2009-04-16 6:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 1:07 Timur Tabi
2009-04-16 6:42 ` Kai Ruottu [this message]
2009-04-16 14:50 ` dan hitt
2009-04-17 2:16 ` Timur Tabi
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=49E6D3A0.7060502@wippies.com \
--to=kai.ruottu@wippies.com \
--cc=gcc-help@gcc.gnu.org \
--cc=timur@freescale.com \
/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).