public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: kim@mso.anu.edu.au
To: gcc-gnats@gcc.gnu.org
Subject: bootstrap/6415: powerpc-wrs-vxworks wont bootstrap
Date: Mon, 22 Apr 2002 22:06:00 -0000 [thread overview]
Message-ID: <20020423045940.14020.qmail@sources.redhat.com> (raw)
>Number: 6415
>Category: bootstrap
>Synopsis: powerpc-wrs-vxworks wont bootstrap
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Mon Apr 22 22:06:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: Kim Sebo
>Release: 3.1 (CVS of 20020423), 3.0.4 and 2.95.3
>Organization:
>Environment:
Solaris 8 sparc crosscompiling to powerpc-wrs-vxworks
>Description:
Bootstrapping powerpc-wrs-vxworks (v2.0.2) from Solaris 8 sparc fails
due to "CPU" not being defined, as required by the vxworks
headers.
The configure line was:
../gcc/configure --target=powerpc-wrs-vxworks --with-headers=${WIND_BASE}/target/h --enable-languages=c,c++ --with-gnu-as --with-as=$WIND_BASE/host/sun4-solaris2/powerpc-wrs-vxworks/bin/as --with-gnu-ld --with-ld=$WIND_BASE/host/sun4-solaris2/powerpc-wrs-vxworks/bin/ld
The last part of the bootstrap is:
> if [ -f stmp-dirs ]; then true; else touch stmp-dirs; fi
> ./xgcc -B./ -B/data/mizar/kim/powerpc-wrs-vxworks/bin/ -isystem /data/mizar/kim/powerpc-wrs-vxworks/include -isystem /data/mizar/kim/powerpc-wrs-vxworks/sys-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../../gcc/gcc -I../../gcc/gcc/. -I../../gcc/gcc/config -I../../gcc/gcc/../include -mrelocatable-lib -mno-eabi -mstrict-align -DL_muldi3 -c ../../gcc/gcc/libgcc2.c -o libgcc/./_muldi3.o
> In file included from /data/mizar/kim/powerpc-wrs-vxworks/sys-include/types/vxANSI.h:44,
> from include/stdio.h:66,
> from ../../gcc/gcc/tsystem.h:63,
> from ../../gcc/gcc/libgcc2.c:37:
> include/types/vxCpu.h:209:2: #error CPU is not defined correctly
> gnumake[3]: *** [libgcc/./_muldi3.o] Error 1
> gnumake[3]: Leaving directory `/data/mizar/kim/obj/gcc'
> gnumake[2]: *** [stmp-multilib] Error 2
> gnumake[2]: Leaving directory `/data/mizar/kim/obj/gcc'
> gnumake[1]: *** [stage1_build] Error 2
> gnumake[1]: Leaving directory `/data/mizar/kim/obj/gcc'
> gnumake: *** [bootstrap] Error 2
Earlier in the bootstrap is a possible culprit:
> constructing ../fixinc.sh for powerpc-wrs-vxworks to run on sparc-sun-solaris2.8
> gnumake TARGETS=oneprocess SHELL="/bin/sh" CC="cc" CFLAGS="-DIN_GCC -DCROSS_COMPILE -g -DHAVE_CONFIG_H -DGENERATOR_FILE" LDFLAGS="" install-bin
> gnumake[3]: Entering directory `/data/mizar/kim/obj/gcc/fixinc'
> /bin/sh ../../../gcc/gcc/fixinc/genfixes machname.h
> Forbidden identifiers: CPU CPU_FAMILY linux unix
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2002-04-23 5:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-22 22:06 kim [this message]
2002-04-22 22:31 zack
2002-04-22 22:36 Zack Weinberg
2003-04-04 1:07 zack
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=20020423045940.14020.qmail@sources.redhat.com \
--to=kim@mso.anu.edu.au \
--cc=gcc-gnats@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).