public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Anthony Green <green@cygnus.com>
To: gcc-gnats@gcc.gnu.org
Subject: java/5912: gcj -R doesn't work for mingw32 cross compiler
Date: Sun, 10 Mar 2002 11:46:00 -0000 [thread overview]
Message-ID: <200203101938.LAA04122@makita.cygnus.com> (raw)
>Number: 5912
>Category: java
>Synopsis: gcj -R doesn't work for mingw32 cross compiler
>Confidential: no
>Severity: critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: wrong-code
>Submitter-Id: net
>Arrival-Date: Sun Mar 10 11:46:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: Anthony Green
>Release: 3.1 20020309 (prerelease)
>Organization:
>Environment:
System: IA-32 Red Hat Linux 7.2
Architecture: i386
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-mingw32
configured with: ../gcc/configure --prefix=/usr/local/gcc --target=i686-pc-mingw32 --host=i686-pc-linux-gnu --enable-languages=c,c++,java --disable-nls --with-as=/usr/local/gcc/i686-pc-mingw32/bin/as --with-ld=/usr/local/gcc/i686-pc-mingw32/bin/ld --with-gnu-ld --with-gnu-as --enable-libgcj --enable-gc-type=boehm --disable-shared --enable-threads=win32 --disable-hash-synchronization --disable-interpreter --enable-sjlj-exceptions
>Description:
"gcj -R" appears to be creating two functions with the same name.
One of them does the right thing (registering the resource data with the
runtime). The other one is empty -- it just returns. The assembler barfs
on this.
>How-To-Repeat:
$ i686-pc-mingw32-gcj -R foo -S -o foo.s anyfile
The assembler will report an error about duplicate symbols.
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2002-03-10 19:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-10 11:46 Anthony Green [this message]
2002-03-15 9:07 green
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=200203101938.LAA04122@makita.cygnus.com \
--to=green@cygnus.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).