Re: I think I'm ready to give up on x86_64

["dj_segfault" <user=60@nabble.blu.org>]

 Nathan Meyers wrote: 
> David Kramer wrote: 
>> Nathan Meyers wrote: 
>> 
>>> J2EE works fine on 64-bit. The only Java libraries that need 32- and 
>>> 64-bit versions are those with underlying dependencies on the native 
>>> word lengths. J2SE defines the fundamental data types and object 
>>> addressing, so it naturally needs different versions. Pure-Java 
>>> libraries, like J2EE, shouldn't need different versions. 
>> 
>> ...But I couldn't even install it.  I think what it was missing was 
>> libstdc++.5.s0, when my system had .6.so.  I found a compat rpm with 
>> .5.so, but it was 64 bit, so even after I installed it, and ran 
>> ldconfig for good measure, it still gave the same error. 
> 
> Got it... taking a closer look, I see there are some architectural 
> dependencies that I don't encounter in my day-to-day J2EE work (it's not 
> all quite as pure-Java as I believed). 
> 
> The first architectural dependency is the installer executable, in which 
> Sun makes you agree to a license before unpacking. That's probably where 
> you're hitting the libstdc++ dependency. Beyond that, Sun delivers a few 
> native-code utilities, plus a native "update center" application you can 
> use for managing automatic updates, and a number of native libraries - 
> probably for use by the various utilities. I've never encountered 
> platform dependencies in the J2EE libs themselves, but clearly there are 
> parts of the installation that are platform dependent.