public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: target/10743: Build error for CPP when building Cross compiler and host and target have diff character sets (i370)
@ 2003-05-14  6:36 Dara Hazeghi
  0 siblings, 0 replies; 2+ messages in thread
From: Dara Hazeghi @ 2003-05-14  6:36 UTC (permalink / raw)
  To: nobody; +Cc: gcc-prs

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

From: Dara Hazeghi <dhazeghi@yahoo.com>
To: ivan@vmfacility.fr, gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: target/10743: Build error for CPP when building Cross compiler and host and target have diff character sets (i370)
Date: Tue, 13 May 2003 23:29:16 -0700

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit- 
 trail&database=gcc&pr=10743
 
 Hello,
 
 looking at the "supported system" list for gcc, I see "This port is  
 very preliminary and has many known bugs.  We hope to have a  
 higher-quality port for this machine soon." Not very encouraging.  
 Still, if you want to pursue this bug, I suggest that you try out the  
 latest gcc cvs and see how it fairs. Neil Booth (our cpp maintainer)  
 has been doing a lot of work to make cpp more robust wrt character sets  
 and the like, and I suspect that if you try out mainline, and have  
 feedback to give him, he might be able to fix the issue. In any case,  
 3.2 branch is dead at this point, so you'll have to try a newer version  
 at some point anyway. Cheers,
 
 Dara
 


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

* target/10743: Build error for CPP when building Cross compiler and host and target have diff character sets (i370)
@ 2003-05-12  9:36 ivan
  0 siblings, 0 replies; 2+ messages in thread
From: ivan @ 2003-05-12  9:36 UTC (permalink / raw)
  To: gcc-gnats


>Number:         10743
>Category:       target
>Synopsis:       Build error for CPP when building Cross compiler and host and target have diff character sets (i370)
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon May 12 09:36:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Ivan Warren
>Release:        gcc 3.2.3
>Organization:
>Environment:
Host i686-linux, Target i370-ibm-mvs
>Description:
When attempting a cross compile build, cpp0 cannot be built because it is refereing to macro 'MVS_MAPCHAR' in cpplex.c which is mapped to mvs_map_char in gcc/config/i370.[ch] (which belongs in libbackend.a). Commenting out the ifdef/endif allows building the cpp, but resulting character constants are then ASCII (and not EBCDIC). My belief is that this will affect any attempt at creating a cross compiler when host and target need a backend specific character translator. I understand what I am attempting may not be supported, but this issue could affect any further attempts at building a clean cross compiler.
>How-To-Repeat:
../gcc-3.3.3/configure --target=i370-ibm-mvs --enable-languages=c
make

(note : the build errors I get on the C library are expected.. I am only interrested in the assembler output of the C compiler and do my own C Library - freestanding compiles, and my target is NOT a Un*x variant)..
>Fix:
I have no readilly available fix for this issue. The problem lies in the interdependance created by invoking MAP_CHARACTER from within cpplex.c which creates a dependance by cpplex.c for libbackend.a, while libbackend.a cannot be used on cpp0.
>Release-Note:
>Audit-Trail:
>Unformatted:


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

end of thread, other threads:[~2003-05-14  6:36 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-05-14  6:36 target/10743: Build error for CPP when building Cross compiler and host and target have diff character sets (i370) Dara Hazeghi
  -- strict thread matches above, loose matches on Subject: below --
2003-05-12  9:36 ivan

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