public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
* [ECOS] compile 2.95.2 error
       [not found] <NFBBJAJICAKJPMMKDAGBEEHICMAA.wpd@delcomsys.com>
@ 2001-11-02 19:34 ` RolandKane
  2001-11-03  3:08   ` Patrick Doyle
  0 siblings, 1 reply; 2+ messages in thread
From: RolandKane @ 2001-11-02 19:34 UTC (permalink / raw)
  To: eCos

When creating the i386 tools, I get the following error. I installed as per
the instructions and applied the patch for gcc-2.95.2. The Binutils built
without any errors.


MAKE="make"; srcdir=`cd /src/gcc/gcc-2.95.2/gcc/fixinc; pwd` ; \
export MAKE srcdir ; \
cd ./fixinc; /bin/sh ${srcdir}/mkfixinc.sh i386-pc-elf
constructing ../fixinc.sh for i386-pc-elf
make SHELL="/bin/sh" install
make[2]: Entering directory `/tmp/build/gcc/gcc/fixinc'
gcc -c -g -I. -I.. -I/src/gcc/gcc-2.95.2/gcc/fixinc -I/src/gcc/gcc-2.95.2/gc
c/fixinc/.. -I/src/gcc/gcc-2.95.2/gcc/fixinc/../config -I/src/gcc/gcc-2.95.2
/gcc/fixinc/../../include /src/gcc/gcc-2.95.2/gcc/fixinc/fixincl.c
/src/gcc/gcc-2.95.2/gcc/fixinc/fixincl.c: In function `initialize':
/src/gcc/gcc-2.95.2/gcc/fixinc/fixincl.c:349: `SIGIOT' undeclared (first use
in this function)
/src/gcc/gcc-2.95.2/gcc/fixinc/fixincl.c:349: (Each undeclared identifier is
reported only once
/src/gcc/gcc-2.95.2/gcc/fixinc/fixincl.c:349: for each function it appears
in.)
make[2]: *** [fixincl.o] Error 1
make[2]: Leaving directory `/tmp/build/gcc/gcc/fixinc'
Could not install binary fixincludes.
Installing shell script instead.
rm -rf include; mkdir include


Thanks,
Roland Kane



^ permalink raw reply	[flat|nested] 2+ messages in thread

* RE: [ECOS] compile 2.95.2 error
  2001-11-02 19:34 ` [ECOS] compile 2.95.2 error RolandKane
@ 2001-11-03  3:08   ` Patrick Doyle
  0 siblings, 0 replies; 2+ messages in thread
From: Patrick Doyle @ 2001-11-03  3:08 UTC (permalink / raw)
  To: RolandKane, eCos

I experienced the same behavior, but since the build process continued, and
the message displayed by the build process led be to believe that this error
was benign, I ignored it.  The tools compile and work for me just fine, even
with that warning.

--wpd


> -----Original Message-----
> From: ecos-discuss-owner@sources.redhat.com
> [mailto:ecos-discuss-owner@sources.redhat.com]On Behalf Of RolandKane
> Sent: Tuesday, November 13, 2001 8:44 AM
> To: eCos
> Subject: [ECOS] compile 2.95.2 error
>
>
> When creating the i386 tools, I get the following error. I
> installed as per
> the instructions and applied the patch for gcc-2.95.2. The Binutils built
> without any errors.
>
>
> MAKE="make"; srcdir=`cd /src/gcc/gcc-2.95.2/gcc/fixinc; pwd` ; \
> export MAKE srcdir ; \
> cd ./fixinc; /bin/sh ${srcdir}/mkfixinc.sh i386-pc-elf
> constructing ../fixinc.sh for i386-pc-elf
> make SHELL="/bin/sh" install
> make[2]: Entering directory `/tmp/build/gcc/gcc/fixinc'
> gcc -c -g -I. -I.. -I/src/gcc/gcc-2.95.2/gcc/fixinc
> -I/src/gcc/gcc-2.95.2/gc
> c/fixinc/.. -I/src/gcc/gcc-2.95.2/gcc/fixinc/../config
> -I/src/gcc/gcc-2.95.2
> /gcc/fixinc/../../include /src/gcc/gcc-2.95.2/gcc/fixinc/fixincl.c
> /src/gcc/gcc-2.95.2/gcc/fixinc/fixincl.c: In function `initialize':
> /src/gcc/gcc-2.95.2/gcc/fixinc/fixincl.c:349: `SIGIOT' undeclared
> (first use
> in this function)
> /src/gcc/gcc-2.95.2/gcc/fixinc/fixincl.c:349: (Each undeclared
> identifier is
> reported only once
> /src/gcc/gcc-2.95.2/gcc/fixinc/fixincl.c:349: for each function it appears
> in.)
> make[2]: *** [fixincl.o] Error 1
> make[2]: Leaving directory `/tmp/build/gcc/gcc/fixinc'
> Could not install binary fixincludes.
> Installing shell script instead.
> rm -rf include; mkdir include
>
>
> Thanks,
> Roland Kane
>
>
>

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2001-11-13 13:41 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <NFBBJAJICAKJPMMKDAGBEEHICMAA.wpd@delcomsys.com>
2001-11-02 19:34 ` [ECOS] compile 2.95.2 error RolandKane
2001-11-03  3:08   ` Patrick Doyle

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).