Re: bootstrap/3437: [vxworks] cross-compile problem because of fixincludes

Re: bootstrap/3437: [vxworks] cross-compile problem because of fixincludes

[giovannibajo]

Synopsis: [vxworks] cross-compile problem because of fixincludes

State-Changed-From-To: open->feedback
State-Changed-By: bajo
State-Changed-When: Wed May 14 10:56:19 2003
State-Changed-Why:
    See Dara's question.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=3437

Re: bootstrap/3437: [vxworks] cross-compile problem because of fixincludes

[Dara Hazeghi]

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

From: Dara Hazeghi <dhazeghi@yahoo.com>
To: alexsh@hectic.net, gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org,
   fsciarra@tin.it
Cc:  
Subject: Re: bootstrap/3437: [vxworks] cross-compile problem because of fixincludes
Date: Wed, 14 May 2003 01:30:45 -0700

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit- 
 trail&database=gcc&pr=3437
 
 Hello,
 
 I believe that the vxworks port has been reworked from scratch more or  
 less on the gcc cvs mainline. Would it be possible for someone to check  
 whether this problem still occurs when cross-compiling using cvs gcc?  
 Thanks,
 
 Dara
 

re: bootstrap/3437: [vxworks] cross-compile problem because of fixincludes

[fsciarra]

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
 

Re: bootstrap/3437: [vxworks] cross-compile problem because of fixincludes

[neroden]

Synopsis: [vxworks] cross-compile problem because of fixincludes

State-Changed-From-To: feedback->open
State-Changed-By: neroden
State-Changed-When: Thu Mar 27 20:21:50 2003
State-Changed-Why:
    No feedback 3 months, bootstrap problem with old version.
    But this one looks specific and testable.  Does anyone have a Vxworks system, so they can check that fixincludes does the right thing now?

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=3437

Re: bootstrap/3437: [vxworks] cross-compile problem because of fixincludes

[bangerth]

Old Synopsis: vxworks cross-compile problem because of fixincludes
New Synopsis: [vxworks] cross-compile problem because of fixincludes

State-Changed-From-To: open->feedback
State-Changed-By: bangerth
State-Changed-When: Tue Nov 19 12:24:59 2002
State-Changed-Why:
    This is a rather old bootstrap failure. Can you please
    check whether this still happens with newer versions of gcc
    and report your findings?
    
    Thanks
      Wolfgang

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=3437

bootstrap/3437: vxworks cross-compile problem because of fixincludes

[alexsh]

>Number:         3437
>Category:       bootstrap
>Synopsis:       vxworks cross-compile problem because of fixincludes
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Jun 27 06:36:02 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Alex Shnitman
>Release:        3.0
>Organization:
>Environment:
Host compiler gcc-2.95.3, Debian 2.2
>Description:
When cross-compiling gcc 3.0 for a vxworks target, it
copies the include files that come with VxWorks and runs
fixincludes on them. The latter changes all the occurrences
of "CPU" to "__CPU__" in those files. However, after this
change one of the files stops compiling. This file defines
CPU_FAMILY according to the definition of CPU. (The latter
is defined by the compiler -- it's in the spec file for the
platform.) Here's a snippet from vxCpu.h:

#if     (CPU==I80386 || CPU==I80486 || CPU==PENTIUM || CPU==PENTIUMPRO)
#define CPU_FAMILY      I80X86
#endif  /* CPU_FAMILY==I80X86 */

fixincludes changes "CPU" to "__CPU__", and the above code
naturally stops working. At the end of vxCpu.h, there's
this code:

#if !defined(CPU) || !defined(CPU_FAMILY)
#error CPU is not defined correctly
#endif

Due to the fixincludes "fixes", this error is always
triggered. The gcc build thus fails:

make[2]: Entering directory `/home/alexsh/gcc-3.0/gcc'
for d in libgcc nof libgcc/nof le libgcc/le ca libgcc/ca und libgcc/und le/und libgcc/le/und nof/le libgcc/nof/le nof/ca libgcc/nof/ca nof/und libgcc/nof/und nof/le/und libgcc/nof/le/und; do \
  if [ -d $d ]; then true; else mkdir $d; fi \
done
if [ -f stmp-dirs ]; then true; else touch stmp-dirs; fi
/home/alexsh/gcc-3.0/gcc/xgcc -B/home/alexsh/gcc-3.0/gcc/ -B/usr/local/vxworks/powerpc-wrs-vxworks/bin/ -B/usr/local/vxworks/powerpc-wrs-vxworks/lib/ -isystem /usr/local/vxworks/powerpc-wrs-vxworks/include -O2  -DCROSS_COMPILE -DIN_GCC    -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -isystem ./include   -g1 -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 /usr/local/vxworks/powerpc-wrs-vxworks/sys-include/types/vxANSI.h:44,
                 from /home/alexsh/gcc-3.0/gcc/include/stdio.h:66,
                 from tsystem.h:63,
                 from libgcc2.c:37:
/home/alexsh/gcc-3.0/gcc/include/types/vxCpu.h:209:2: #error CPU is not defined correctly
make[2]: *** [libgcc/./_muldi3.o] Error 1
make[2]: Leaving directory `/home/alexsh/gcc-3.0/gcc'
make[1]: *** [stmp-multilib] Error 2
make[1]: Leaving directory `/home/alexsh/gcc-3.0/gcc'
make: *** [all-gcc] Error 2
>How-To-Repeat:
cd gcc-3.0
./configure --target=powerpc-wrs-vxworks --with-headers=/net/tornado/c/Tornado/target/h
make

The same process works flawlessly when compiling gcc 2.95.3.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted: