Processed: Re: Bug#289494: sablevm: cannot create vm

2005-01-15 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

> severity 289494 important
Bug#289494: sablevm: cannot create vm
Severity set to `important'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#289494: sablevm: cannot create vm

2005-01-15 Thread Kurt Roeckx
severity 289494 important
thanks

It seems this is caused by the 2.6.10 amd64 kernel.  It
didn't enter sid yet (it's in NEW) so I can't reassign this to
kernel-image-2.6.10-amd64 yet.


Kurt



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#289494: sablevm: cannot create vm

2005-01-11 Thread Kurt Roeckx
On Wed, Jan 12, 2005 at 01:47:59AM -0500, Grzegorz B. Prokopski wrote:
> 
> But the configure itself (at least the one executed at the beginning,
> not sure that is the only one) seemed to execute properly.

And that is a current sid or sarge?  In that case, feel free to
lower the severity (and tag unreproducible?), and I'll look
closer to it on this side.


Kurt



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#289494: sablevm: cannot create vm

2005-01-11 Thread Grzegorz B. Prokopski
Hi,

I tried to reproduce the problem by building db4.2-4.2.52 source on a
sparc machine, but it failed after a few minutes, during the compilation
of native code:

/usr/lib/gcc-lib/sparc-linux/3.3.5/../../../../lib/crti.o(.init+0x0): In
function `_init':
/build/buildd/glibc-2.3.2.ds1/build-tree/sparc-libc/csu/crti.S:9:
multiple definition of `_init'
/usr/lib/gcc-lib/sparc-linux/3.3.5/../../../../lib/crti.o(.init
+0x0):/build/buildd/glibc-2.3.2.ds1/build-tree/sparc-libc/csu/crti.S:9:
first defined here
/usr/bin/ld: Disabling relaxation: it will not work with multiple
definitions
/usr/lib/gcc-lib/sparc-linux/3.3.5/../../../../lib/crti.o(.fini+0x0): In
function `_fini':
: multiple definition of `_fini'
/usr/lib/gcc-lib/sparc-linux/3.3.5/../../../../lib/crti.o(.fini+0x0):
first defined here
/usr/lib/gcc-lib/sparc-linux/3.3.5/crtbeginS.o(.data.rel+0x0): multiple
definition of `__dso_handle'
/usr/lib/gcc-lib/sparc-linux/3.3.5/crtbeginS.o(.data.rel+0x0): first
defined here
collect2: ld returned 1 exit status
make[1]: *** [libdb_cxx-4.2.la] Error 1
make[1]: Leaving directory `/tmp/db4.2-4.2.52/obj'
make: *** [build] Error 2

But the configure itself (at least the one executed at the beginning,
not sure that is the only one) seemed to execute properly.

On Sun, 2005-09-01 at 14:44 +0100, Kurt Roeckx wrote:
[...]
> public class Test {
> public static void main (String args[]) {
> System.exit (0);
> } }
> configure.mutexes-disabled:20854: error: The Java VM java failed
> (see config.log, check the CLASSPATH?)

Strange.  Such a simple program definitely should work.  Don't you
have LD_LIBRARY_PATH set to something strange?  Altough still,
it should give some more elaborate error message than that.

OTOH - whatever the actuall error was, it would be nice to know
how to reproduce it, so that I could add a more meaningful error
message to SableVM itself.

> Note that I have the same problem with the version in sarge
> (1.1.6-6) as in sid (1.1.8-1.1).
> 
> Those versions used to work 2 weeks ago, so I assume something
> external to sablevm has changed.

I might try on my x86 later, again.  Maybe I find something else,
or at least get the db4.2 sources built properly.

Let me know if I you have any ideas how I could help you.

Cheers,

Grzegorz B. Prokopski
-- 
Grzegorz B. Prokopski   <[EMAIL PROTECTED]>
SableVM - Free, LGPL'ed Java VM  http://sablevm.org
Why SableVM ?!?  http://sablevm.org/wiki/Features
Debian GNU/Linux - the Free OS   http://www.debian.org




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]