From: Waskita Adijarto <waszbulk@hq.ee.itb.ac.id>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] eCos problem: if_lancepci.c does not compile for i386 (vmWare)
Date: Mon, 24 Aug 2009 08:12:00 -0000 [thread overview]
Message-ID: <4A924B46.4050209@hq.ee.itb.ac.id> (raw)
I've just found problem compiling if_lancepci.c under eCos. After
googling , I found similar problem in the archive here:
http://www.mail-archive.com/ecos-discuss@ecos.sourceware.org/msg09854.html.
I used similar new gnutools
(ecoscentric-gnutools-i386-elf-20081107-sw.cygwin.tar.bz2)
I experienced this problem while compiling eCos 3.0 and 1.0.8 (from
gaisler) in cygwin
Tool chain version:
$ i386-elf-gcc -v
Using built-in specs.
Target: i386-elf
Configured with: /gnutools/src/toolchains/gcc/gcc-4.3.2/configure -v --target=i386-elf --prefix=/gnutools/builds/toolchains/i386-elf/tools --with-newlib --with-gnu-as --with-gnu-ld --enable-languages=c,c++ --disable-__cxa_atexit --enable-threads --with-bugurl=http://bugs.ecos.sourceware.org/ --with-pkgversion='eCosCentric GNU tools 4.3.2-sw'
Thread model: single
gcc version 4.3.2 (eCosCentric GNU tools 4.3.2-sw)
My solution: use old gnutools
(ecoscentric-gnutools-i386-elf-1.4-2.cygwin.tar.bz2) . The problem goes
away.
tool chain version:
$ i386-elf-gcc -v
Reading specs from /opt/gnutools/i386-elf/bin/../lib/gcc-lib/i386-elf/3.2.1/specs
Configured with: /local/demonweb/tools/ecos-gnutools-v1.4/r2/i386-elf/cygwin/tar_bz2/source/gcc-3.2.1/configure --target=i386-elf --prefix=/local/demonweb/tools/ecos-gnutools-v1.4/r2/i386-elf/cygwin/tar_bz2/opt/ecos/gnutools/i386-elf --enable-languages=c,c++ --with-gnu-as --with-gnu-ld --with-newlib --with-gxx-include-dir=/local/demonweb/tools/ecos-gnutools-v1.4/r2/i386-elf/cygwin/tar_bz2/opt/ecos/gnutools/i386-elf/i386-elf/include
Thread model: single
gcc version 3.2.1
I wonder why gcc 4.3.2 behave so different than 3.2.1
-waskita-
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next reply other threads:[~2009-08-24 8:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-24 8:12 Waskita Adijarto [this message]
2009-08-24 11:36 ` [ECOS] Ethernet controllers Jim Bradleigh
2009-08-24 12:35 ` [ECOS] " John Dallaway
2009-08-24 15:23 ` Jim Bradleigh
2009-08-24 15:33 ` Gary Thomas
2009-08-24 15:59 ` Jim Bradleigh
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=4A924B46.4050209@hq.ee.itb.ac.id \
--to=waszbulk@hq.ee.itb.ac.id \
--cc=ecos-discuss@ecos.sourceware.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).