public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: fsciarra@tin.it
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: re: bootstrap/3437: [vxworks] cross-compile problem because of fixincludes
Date: Thu, 01 May 2003 17:56:00 -0000	[thread overview]
Message-ID: <20030501175601.17503.qmail@sources.redhat.com> (raw)

The following reply was made to PR bootstrap/3437; it has been noted by GNATS.

From: fsciarra@tin.it
To: gcc-gnats@gcc.gnu.org,
 gcc-bugs@gcc.gnu.org,
 nobody@gcc.gnu.org,
 gcc-prs@gcc.gnu.org,
 alexsh@hectic.net
Cc: fsciarra@tin.it
Subject: re: bootstrap/3437: [vxworks] cross-compile problem because of fixincludes
Date: Thu, 1 May 2003 19:40:24 +0200

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=3Dview%20audit-trail&database=3D=
 gcc&pr=3D3437
 
 Hi,
 I'm experiencing the same problem with:
 vxWorks 5.4
 binutils 2.13.2.1
 gcc 3.2.3
 
 The compiler I'm using to compile (!) is gcc-3.2.2 on a Mandrake box.
 I'm available to make other tryies.
 Following the error (just the latest step.if you need more just ask).
 
 
 /projects/cross/gcc-3.2.3/gcc/xgcc -B/projects/cross/gcc-3.2.3/gcc/ 
 -B/projects/cross/vxworks/powerpc-wrs-vxworks/bin/ 
 -B/projects/cross/vxworks/powerpc-wrs-vxworks/lib/ 
 -isystem /projects/cross/vxworks/powerpc-wrs-vxworks/include -O2  
 -DIN_GCC -DCROSS_COMPILE   -W -Wall -Wwrite-strings 
 -Wstrict-prototypes -Wmissing-prototypes -isystem ./include   -g 
 -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED  -I. -I. -I. 
 -I./. -I./config -I./../include  -mrelocatable-lib -mno-eabi 
 -mstrict-align -DL_muldi3 -c ./libgcc2.c -o libgcc/./_muldi3.o
 In file included from /projects/cross/vxworks/powerpc-wrs-vxworks/sys-inc=
 lude/types/vxANSI.h:44,
                  from /projects/cross/gcc-3.2.3/gcc/include/stdio.h:66,
                  from tsystem.h:63,
                  from libgcc2.c:37:
 /projects/cross/gcc-3.2.3/gcc/include/types/vxCpu.h:209:2: #error CPU is
 not defined correctly
 make[2]: *** [libgcc/./_muldi3.o] Error 1
 make[2]: Leaving directory `/projects/cross/gcc-3.2.3/gcc'
 make[1]: *** [stmp-multilib] Error 2
 make[1]: Leaving directory `/projects/cross/gcc-3.2.3/gcc'
 make: *** [all-gcc] Error 2
 
 
 Best regards and thanks you all for the job you're doing.
   Fabrizio Sciarra
 


             reply	other threads:[~2003-05-01 17:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-01 17:56 fsciarra [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-14 10:56 giovannibajo
2003-05-14  8:36 Dara Hazeghi
2003-03-27 20:23 neroden
2002-11-26 15:46 bangerth
2001-06-27  6:36 bootstrap/3437: vxworks " alexsh

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=20030501175601.17503.qmail@sources.redhat.com \
    --to=fsciarra@tin.it \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.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).