public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@redhat.com>
To: james chen <james_ch1@sina.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS]Compiler erros with cygwin
Date: Tue, 06 Feb 2001 05:23:00 -0000	[thread overview]
Message-ID: <3A7FFAD6.F2F82844@redhat.com> (raw)
In-Reply-To: <000701c08fe5$f2610060$c408aa0a@inc.inventec>

james chen wrote:
> 
> I use configuration tool to configure a target of 'Linux synthetic target',
> when I compiler it, it occurs the following message, any one can help me to
> resolve it? I run configuration tool and cygwin in windows98. I also try
> three versions of gcc( 2.95-2, 2.95-6, 2.95-7) in cygwin, and the result 
> same.

This is potentially because you are trying to generate linux native
executables using a cygwin native compiler! You need to build a
cygwin->linux cross compiler. I believe
http://sources.redhat.com/ecos/tools/win-i386-elf.html should build a
compiler you can use, although you may need to change the
CYGBLD_GLOBAL_PREFIX CDL variable.

Jifl

> Thanks
> 
> james chen
> 
> =======================================================================
> ......
> headers finished
> 
> ////////////////////
> 
> make -r -C hal/common/v1_3_1 build
> make[1]: Entering directory `/test/test/test_build/hal/common/v1_3_1'
> make[1]: Nothing to be done for `build'.
> make[1]: Leaving directory `/test/test/test_build/hal/common/v1_3_1'
> make -r -C io/common/v1_3_1 build
> make[1]: Entering directory `/test/test/test_build/io/common/v1_3_1'
> gcc -c  -I//I/ecos_current/test/test_install/include -I//D/PROGRA~1/REDHAT~1
> /eCos/packages/io/common/v1_3_1 -I//D/PROGRA~1/REDHAT~1/eCos/packages/io/com
> mon/v1_3_1/src -I//D/PROGRA~1/REDHAT~1/eCos/packages/io/common/v1_3_1/tests
> -I. -I//D/PROGRA~1/REDHAT~1/eCos/packages/io/common/v1_3_1/src/ -Wall -Wpoin
> ter-arith -Wstrict-prototypes -Winline -Wundef -Woverloaded-virtual -g -O2 -
> ffunction-sections -fdata-sections -fno-rtti -fno-exceptions -fvtable-gc -fi
> nit-priority -Wp,-MD,src/ioinit.tmp -o src/io_common_ioinit.o
> file://D/PROGRA~1/REDHAT~1/eCos/packages/io/common/v1_3_1/src/ioinit.cxx
> file://D/PROGRA~1/REDHAT~1/eCos/packages/io/common/v1_3_1/src/ioinit.cxx:0:
> warning: -ffunction-sections may affect debugging on some targets.
> file://D/PROGRA~1/REDHAT~1/eCos/packages/io/common/v1_3_1/src/ioinit.cxx:60:
> Internal compiler error.
> file://D/PROGRA~1/REDHAT~1/eCos/packages/io/common/v1_3_1/src/ioinit.cxx:60:
> Please submit a full bug report.
> file://D/PROGRA~1/REDHAT~1/eCos/packages/io/common/v1_3_1/src/ioinit.cxx:60:
> See <URL: http://www.gnu.org/software/gcc/faq.html#bugreport > for
> instructions.
> make[1]: *** [src/ioinit.o.d] Error 1
> make[1]: Leaving directory `/test/test/test_build/io/common/v1_3_1'
> make: *** [build] Error 2

-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine

  reply	other threads:[~2001-02-06  5:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-05 18:39 james chen
2001-02-06  5:23 ` Jonathan Larmour [this message]
2001-02-06  5:40   ` Fabrice Gautier
2001-02-08  1:36 ` Masashi Ichikawa
2001-02-08  7:06   ` Olaf Peters

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=3A7FFAD6.F2F82844@redhat.com \
    --to=jlarmour@redhat.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=james_ch1@sina.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).