Thank you for the help. Using LD_PRELOAD, I was able to change the error quite a bit. Now it fails after starting the JVM because the current stack is corrupt. I am not sure if this is an improvement or not, but it does mean I should be able to try various JVMs. Unfortunately, I have been building my code against 1.5 which is not rt.jar compatible with previous versions. In particular, there seems to be Byte.valueOf() now instead of new Byte -- at least I think that is one of the inconsistencies that I ran across. Because of it, I have moved all of my code forward to 1.5. I certainly did not foresee this as a problem.
Hopefully you all will have a 1.5 JVM soon... On Sat, 2005-04-09 at 04:47 +0200, Juergen Kreileder wrote: > Al Niessner <[EMAIL PROTECTED]> writes: > > > Since it works with a C++ main(), I am guessing that there is some > > symbol in Octave that is clashing with what libzip.so > > Probably, AFAIK Sun internalizes symbols in the i386 build but not in > the x86-64 and ia64 builds. Our 1.4.2-01 for x86-64 should be OK. > > If you have to use Sun's 1.5.0, you might be able to work around the > problem by LD_PRELOADing Java's libzip > > > Juergen > ---------------------------------------------------------------------- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
