From: "Nicola Bergamin [BW]" <nicola.bergamin@bluewind.it>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] cc1plus problem
Date: Thu, 24 May 2001 23:14:00 -0000 [thread overview]
Message-ID: <3B0E139F.22570.BAF9B@localhost> (raw)
Hi,
I've tried to build gcc2.95.2 under cygwin1.3.1.
using source files:
binutils-2.10.1.tar.gz2,
gcc-core-2.95.2.tar.bz2
gcc-g++-2.95.2.tar.bz2
and patch:
ecos-gcc-2952.pat
The build seemed ok, except that "cc1plus.exe" was not built at all!
Another strange thing, "libgcc.a" was 99kB, appeared too small in
size.
(I checked with other builds, it should make 240kB)
The instruction I followed is the standard set in eCos website, and
here is the
command file I used under bash shell:
(just report here the GCC section...)
************************************
#!/bin/sh
target=arm-elf
prefix=/tools_ecos
mkdir -p /tmp/build/build_gcc
cd /tmp/build/build_gcc/src/gcc/gcc-2.95.2/configure \
--target=$target \
--prefix=$prefix \
--exec_prefix=$prefix/xgcc \
--with-gnu-as \
--with-gnu-ld \
--with-newlib -v 2>&1 | tee configure-xgcc.out
make -w all-gcc install-gcc LANGUAGES="c c" 2>&1 | tee make-
xgcc.out
***********************************************************************
By changing to ...LANGUAGES="c c++"
everything worked, cc1plus.exe was built and libgcc.a got 240kB
size, as expected.
Does anybody know the meaning of "c c", and "c c++" strings?
What's wrong with the original build commands?
Thanks
Nicola
------------------------------------------
Nicola Bergamin
BlueWind Embedded Systems Design
Via Steffani, 7/B
I-31033 Castelfranco Veneto (TV)
Office: +39 0 423 723431
Fax : +39 0 423 744738
GSM : +39 335 7556736
mailto:nicola.bergamin@bluewind.it
http://www.bluewind.it
------------------------------------------
next reply other threads:[~2001-05-24 23:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-24 23:14 Nicola Bergamin [BW] [this message]
2001-05-25 6:22 ` Robin Farine
2001-05-25 6:39 ` Jonathan Larmour
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=3B0E139F.22570.BAF9B@localhost \
--to=nicola.bergamin@bluewind.it \
--cc=ecos-discuss@sources.redhat.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).