public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Haley <aph@redhat.com>
To: David Michel <dmichel76@googlemail.com>
Cc: java@gcc.gnu.org
Subject: Re: converting a jar into a shared lib - requirements ?
Date: Mon, 27 Jul 2009 16:56:00 -0000	[thread overview]
Message-ID: <4A6DDC1E.4060304@redhat.com> (raw)
In-Reply-To: <b5bf7a380907270902m712cff52j133a3a9b4feccc51@mail.gmail.com>

On 07/27/2009 06:02 PM, David Michel wrote:
> Hi All,
> 
> While it works fine most of the tine, I have trouble converting some
> jar files into shared lib where I get errors like:
> 
> $ gcj -O0 -g0 -shared java-getopt-1.0.13.jar -o libgetopt-1.0.13.so
> gnu/getopt/LongOpt.java: In class 'gnu.getopt.LongOpt':
> gnu/getopt/LongOpt.java: In constructor
> '(java.lang.String,int,java.lang.StringBuffer,int)':
> gnu/getopt/LongOpt.java:103: internal compiler error: Segmentation fault
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <URL:http://gcc.gnu.org/bugs.html> for instructions.
> For Debian GNU/Linux specific bug reporting instructions,
> see <URL:file:///usr/share/doc/gcc-4.2/README.Bugs>.
> 
> What are the requirements for a jar to be "convertible" into shared
> lib ? I must be missing something trivial there !....

Maybe.  If you can make an easily reproducible test case from this I'll
have a look.  You must supply all the files involved, the exact command used,
the exact version of gccj, tec.

Andrew.

      reply	other threads:[~2009-07-27 16:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-27 16:02 David Michel
2009-07-27 16:56 ` Andrew Haley [this message]

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=4A6DDC1E.4060304@redhat.com \
    --to=aph@redhat.com \
    --cc=dmichel76@googlemail.com \
    --cc=java@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).