commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DAEMON-45) [daemon] jsvc links to 32-bit JVM when compiled for (64-bit) sparcv9
Date Fri, 26 Feb 2010 17:05:28 GMT

     [ https://issues.apache.org/jira/browse/DAEMON-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sebb updated DAEMON-45:
-----------------------

    Fix Version/s: 1.0.2

> [daemon] jsvc links to 32-bit JVM when compiled for (64-bit) sparcv9
> --------------------------------------------------------------------
>
>                 Key: DAEMON-45
>                 URL: https://issues.apache.org/jira/browse/DAEMON-45
>             Project: Commons Daemon
>          Issue Type: Bug
>         Environment: Operating System: Solaris
> Platform: Sun
>            Reporter: Jeff Carroll
>             Fix For: 1.0.2
>
>         Attachments: ls.out
>
>
> This is a report on misbehavior of the search algorithm in native/location.c.
> I am building from the source included in the binary distribution of Tomcat 5.5.16.
> uname -a reports:
> SunOS iempsoa1 5.10 Generic_118822-27 sun4u sparc SUNW,Sun-Fire-880
> config.guess reports sparc-sun-solaris2.10. 
> ls -laR runs to 4k lines of text, so I will attach the file separately if I can
> figure out how. I'm not sure it's relevant, though.
> configure is identifying $host_cpu as "sparc", and thus location.c finds the
> jvm.cfg for the 32-bit JVM, terminating with the messages
> 18/04/2006 15:35:12 7724 jsvc64 debug: Using default JVM in /usr/java/jre/lib/sp
> arc/client/libjvm.so
> 18/04/2006 15:35:12 7724 jsvc64 debug: Attemtping to load library /usr/java/jre/
> lib/sparc/client/libjvm.so
> 18/04/2006 15:35:12 7724 jsvc64 error: Cannot dynamically link to /usr/java/jre/
> lib/sparc/client/libjvm.so
> 18/04/2006 15:35:12 7724 jsvc64 error: ld.so.1: jsvc64: fatal: /usr/java/jre/lib
> /sparc/client/libjvm.so: wrong ELF class: ELFCLASS32
> I intend to fix the problem for my purposes by hacking location_jvm_cfg[], but I
> know that's not a good solution for the general case.
> Everything works flawlessly on the 32-bit JVM. Given that, and given the
> disclaimers all over jvm.cfg, I don't know whether you'll consider this worth
> fixing or not.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message