From: Frank Beesley <frank.beesley@aeroflex.com>
To: karuottu@mbnet.fi
Cc: gcc-help@gcc.gnu.org
Subject: Re: Updating powerpc-crosscompile environment from gcc-2.95.3
Date: Wed, 09 Nov 2005 22:18:00 -0000 [thread overview]
Message-ID: <43727695.1090804@aeroflex.com> (raw)
In-Reply-To: <43726A38.4060506@mbnet.fi>
Lets take one step back - take a look at Kimmo Mustonen's original message:
-------
./configure --target=powerpc-linux --prefix=/tmp/cross --nfp
make TARGET_CONFIGDIRS=
make install
PATH=/tmp/cross/bin:$PATH
export PATH
cd /tmp/cross/src
bzip2 -dc /m/nfs/data/readwrite/sipo-external/gcc-4.0.2.tar.bz2 \
| tar -xf -
mkdir -p gcc-4.0.2-obj
cd gcc-4.0.2-obj
../gcc-4.0.2/configure --target=powerpc-linux --with-cpu=603e --nfp \
--prefix=/tmp/cross --enable-shared --enable-languages="c" \
--with-newlib --disable-threads
make TARGET_CONFIGDIRS=
-------
So we both have just built and installed a new binutils (2.16 for Kimmo,
2.15 for me) using a native gcc (2.95 for Kimmo, 3.2.2 for me) and we
are now trying to build the first-stage gcc cross-compiler (4.0.2 for
Kimmo, 4.0.1 for me). My suggestion to Kimmo was to change his gcc
configure to remove enable-shared and replace it with disable-shared.
Because of this change I am able to get further through the first-step
gcc cross-compiler build - though is does not successfully complete.
After I run the gcc configure I run make to build the gcc cross
compiler. This is what is failing with the message that it cannot create
executables - this is from within the make script, and yes I understand
that the "compiler" is not who actually makes the "executable". I have
also tried setting my path to $PREFIX/$TARGET/bin:$PATH to point at the
newly built tools but the configure for gcc fails when I do this. So
still have not figured out the right combination to build the gcc cross
compiler. I cannot successfully run "make install-gcc" because I cannot
build gcc for the powerpc-motorola-linux target.
Thanks
Frank
Kai Ruottu wrote:
> Frank Beesley wrote:
>
>> "../gcc-4.0.1/configure --prefix=$PREFIX --target=$TARGET
>> --disable-nls --disable-shared --enable-languages=c --without-headers
>> --with-newlib"
>>
>> "make"
>>
>> I get farther then the message you have but it still fails with:
>> checking for powerpc-motorola-linux-gcc...
>> /rpm/ppc/build/gcc/gcc/xgcc -B/rpm/ppc/build/gcc/gcc/
>> -B/opt/ppc/powerpc-motorola-linux/bin/
>> -B/opt/ppc/powerpc-motorola-linux/lib/ -isystem
>> /opt/ppc/powerpc-motorola-linux/include -isystem
>> /opt/ppc/powerpc-motorola-linux/sys-include
>> checking for C compiler default output file name... configure: error:
>> C compiler cannot create executables
>
>
> What do you think being required for "creating executables" ? If you
> know this quite basic thing about "C compilers", then you also know why
> it cannot create them !
>
> In the GCC world, "creating executables" is very far from "compiling",
> but in the Windoze MSVC, BCC etc. cases "compiling" is considered being
> just the same thing as "creating executables" !
>
> So, believe me or not, this error message is really misleading or just
> a fact in the GCC world: A "C compiler" never creates executables there,
> it doesn't even "create objects", one needs an assembler from the GNU
> binutils or some "native 'as'" for this task... What kind of tool
> creates executables and what kind of components will be required
> additionally with the "compiled & assembled" object created from the
> "hello world" C source, will be leaved to you as a homework to find
> out...
>
> In your case I would try writing :
>
> make install-gcc
>
> and then try "compiling" a Hello World in order to see what happens:
>
> powerpc-motorola-linux-gcc -v -O2 -o hello-test hello.c
>
> Can it create this 'hello-test' executable at all? What very obvious is
> still missing
>
next prev parent reply other threads:[~2005-11-09 22:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-09 20:08 Frank Beesley
2005-11-09 21:22 ` Kai Ruottu
2005-11-09 21:33 ` corey taylor
2005-11-09 22:17 ` Kai Ruottu
2005-11-09 22:24 ` Kai Ruottu
2005-11-09 22:18 ` Frank Beesley [this message]
2005-11-10 9:24 ` Kai Ruottu
2005-11-10 9:58 ` Kai Ruottu
2005-11-10 10:16 ` Kai Ruottu
2005-11-10 17:02 ` Frank Beesley
-- strict thread matches above, loose matches on Subject: below --
2005-11-05 13:53 Kimmo Mustonen
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=43727695.1090804@aeroflex.com \
--to=frank.beesley@aeroflex.com \
--cc=gcc-help@gcc.gnu.org \
--cc=karuottu@mbnet.fi \
/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).