Re: Does -fjni work with recent builds?

[Barnet Wagman <wagman at enteract dot com>]

Alexandre Petit-Bianco wrote:

Barnet Wagman writes:

> gcj -fjni -c Locfit.java
> /tmp/ccwnIIQ4.s: Assembler messages:
> /tmp/ccwnIIQ4.s:1546: Error: Ignoring attempt to re-define symbol
> /tmp/ccwnIIQ4.s:1546: Error: Rest of line ignored. First ignored
> character is `,'.

You need to either provide us with a test case, or maybe the actual
line gas doesn't like.

Thanks.

./A

Here's an example:

---

public class JniTest {

    public native void jni_test();
    public static native void jniSetup();

    static {
        System.loadLibrary("locfit");
        jniSetup();
    }

    public JniTest() {}
}

---

Without the -fjni switch gcj (version 2.97 20010117) compiles it without complaint.  With -fjni

bash-2.03$ gcj -fjni -c JniTest.java
/tmp/ccq7mFeP.s: Assembler messages:
/tmp/ccq7mFeP.s:417: Error: Ignoring attempt to re-define symbol
/tmp/ccq7mFeP.s:417: Error: Rest of line ignored. First ignored character is `,'.

(FYI my assembler is GNU assembler version 2.10.91 (i686-pc-linux-gnu) using BFD version 2.10.91  I'm running Linux 2.2.14 (SuSE 6.4), ix86 hardware.)

As far as I know, the 'static native' declaration is legitimate.   It works with a various jvms.

Regards,

Barnet