public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: ivan@vmfacility.fr To: gcc-gnats@gcc.gnu.org Subject: target/10743: Build error for CPP when building Cross compiler and host and target have diff character sets (i370) Date: Mon, 12 May 2003 09:36:00 -0000 [thread overview] Message-ID: <20030512093322.18329.qmail@sources.redhat.com> (raw) >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:
next reply other threads:[~2003-05-12 9:36 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-12 9:36 ivan [this message] 2003-05-14 6:36 Dara Hazeghi
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=20030512093322.18329.qmail@sources.redhat.com \ --to=ivan@vmfacility.fr \ --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: linkBe 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).