public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: nikolay.igotti@sun.com
To: gcc-gnats@gcc.gnu.org
Subject: c/6777: can't cross-compile latest CVS GCC for linux-arm on linux-x86
Date: Wed, 22 May 2002 18:36:00 -0000	[thread overview]
Message-ID: <20020523013436.15028.qmail@sources.redhat.com> (raw)


>Number:         6777
>Category:       c
>Synopsis:       can't cross-compile latest CVS GCC for linux-arm on linux-x86
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed May 22 18:36:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Nikolay Igotti
>Release:        unknown-1.0
>Organization:
>Environment:
Redhat Linux 7.1, x86
>Description:
trying to cross-compile gcc/g++ for linux-arm on linux-x86
I'm getting following error:
./../gcc/gcc/crtstuff.c:195: warning: `__EH_FRAME_BEGIN__' defined but not used
/homes/nike/work/gcc-cvs/gcc-arm/gcc/xgcc -B/homes/nike/work/gcc-cvs/gcc-arm/gcc/ -B/homes/nike/work/gcc-cvs/build/arm-linux/bin/ -B/homes/nike/work/gcc-cvs/build/arm-linux/lib/ -isystem /homes/nike/work/gcc-cvs/build/arm-linux/include -O2 -DIN_GCC -DCROSS_COMPILE   -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -isystem ./include  -I. -I. -I../../gcc/gcc -I../../gcc/gcc/. -I../../gcc/gcc/config -I../../gcc/gcc/../include  -g0 -finhibit-size-directive -fno-inline-functions -fno-exceptions -fno-zero-initialized-in-bss -fPIC \
   -c ../../gcc/gcc/crtstuff.c -DCRT_BEGIN -DCRTSTUFFS_O \
  -o crtbeginS.o
cc1: RTL flag check: CONSTANT_POOL_ADDRESS_P used with unexpected rtx code `const_int' in nonmemory_operand, at recog.c:1222
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
make[1]: *** [crtbeginS.o] Error 1
make[1]: Leaving directory `/homes/nike/work/gcc-cvs/gcc-arm/gcc'
make: *** [all-gcc] Error 2
>How-To-Repeat:

>Fix:

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


                 reply	other threads:[~2002-05-23  1:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20020523013436.15028.qmail@sources.redhat.com \
    --to=nikolay.igotti@sun.com \
    --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).