public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "steve.reinke at iws dot fraunhofer.de" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/47456] internal compiler error: Segmentation fault while using jna
Date: Wed, 26 Jan 2011 06:32:00 -0000	[thread overview]
Message-ID: <bug-47456-8172-VysOCVJ86k@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47456-8172@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47456

--- Comment #2 from steve.reinke at iws dot fraunhofer.de 2011-01-26 06:32:43 UTC ---
the out put of "gcj -v" is the following:

C:\Dokumente und
Einstellungen\reinke\Desktop\JavaNativeCompiler-1.1.1\libs\win\
gcc-122233-win\bin>gcj -v
Using built-in specs.
Reading specs from c:/dokumente und
einstellungen/reinke/desktop/javanativecompi
ler-1.1.1/libs/win/gcc-122233-win/bin/../lib/gcc/i686-pc-mingw32/4.3.0/../../../
libgcj.spec
rename spec startfile to startfileorig
rename spec lib to liborig
Target: i686-pc-mingw32
Configured with: /usr/local/src/gcc/configure
--prefix=/home/Marco/Desktop/compi
le-win-win/gcc-XYZXYZ-win
--with-sysroot=/home/Marco/Desktop/compile-win-win/gcc
-XYZXYZ-win/sys-root --build=i686-pc-linux-gnu --host=i686-pc-mingw32
--target=i
686-pc-mingw32 --enable-languages=c,c++,java --enable-libgcj --disable-shared
--
with-gnu-as --with-gnu-ld --disable-nls --disable-debug --disable-checking
--ena
ble-threads=win32 --disable-win32-registry --enable-java-gc=boehm
--enable-java-
maintainer-mode --with-gmp=/home/Marco/Desktop/compile-win-win/gmp-out
--with-mp
fr=/home/Marco/Desktop/compile-win-win/mpfr-out --enable-sjlj-exceptions
--with-
build-sysroot=/home/Marco/Desktop/compile-win-win/gcc-XYZXYZ-win/sys-root
--with
-gcj=i686-pc-mingw32-gcj
Thread model: win32
gcc version 4.3.0 20070222 (experimental)


  parent reply	other threads:[~2011-01-26  6:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-25 11:20 [Bug java/47456] New: " steve.reinke at iws dot fraunhofer.de
2011-01-25 11:21 ` [Bug java/47456] " steve.reinke at iws dot fraunhofer.de
2011-01-26  0:20 ` pinskia at gcc dot gnu.org
2011-01-26  6:32 ` steve.reinke at iws dot fraunhofer.de [this message]
2011-01-26  6:57 ` steve.reinke at iws dot fraunhofer.de
2011-01-27 11:31 ` steve.reinke at iws dot fraunhofer.de
2011-01-27 12:05 ` mikpe at it dot uu.se
2011-02-01  7:52 ` steve.reinke at iws dot fraunhofer.de
2011-02-01  9:40 ` mikpe at it dot uu.se
2011-02-01 13:14 ` steve.reinke at iws dot fraunhofer.de
2011-02-01 14:12 ` mikpe at it dot uu.se
2011-12-13  9:14 ` ktietz at gcc dot gnu.org
2012-01-10 16:58 ` ktietz at gcc dot gnu.org

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=bug-47456-8172-VysOCVJ86k@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=java-prs@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).