|
From: Andreas W. <and...@em...> - 2004-04-21 08:46:50
|
Prashant,
to verify, which additional libraries a shared library or an executable depend on, you may issue the command "ldd" on it.
So "ldd wrapper" gives me on a SuSE Linux Enterprise 8 (I have no RedHat here):
libc.so.6 => /lib/i686/libc.so.6 (0x40022000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
For libwrapper.so I get:
statically linked
(Leif: was the static linking for the JNI library intentional?)
The binaries are not linked with explicit library dependency, so the GNU linker decides which libraries to link in my default (libc.so in this case; ld-linux.so is linked in by libc.so and is no direct dependency).
ldd will also show you if there are missing dependencies.
Hope it helps,
Andreas
>
> I am trying to get Wrapper(3.0.5) work on Red Hat Linux Adv Server.
>
> 1.What version of glibc is required to get the shipped libraries running.
> - This may be stupid but Is libc the only dependency?
>
> Thanks
> Prashant
>
> Andreas Wendt wrote:
>
> > Leif,
> >
> > when running the testwrapper, clicking on the "System.out deadlock"
> > button causes the JVM to hang without the wrapper recognizing it (at
> > least on MacOSX, OSF1, and Irix).
> > What should really happen?
> > And what is the purpose of this test? It is not explained in the manual.
> >
> > Cheers,
> > Andreas
> >
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by: IBM Linux Tutorials
> > Free Linux tutorial presented by Daniel Robbins, President and CEO of
> > GenToo technologies. Learn everything from fundamentals to system
> > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> > _______________________________________________
> > Wrapper-user mailing list
> > Wra...@li...
> > https://lists.sourceforge.net/lists/listinfo/wrapper-user
> >
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
|
|
From: Andreas W. <and...@em...> - 2004-04-21 09:24:21
|
Leif, a patch is very simple. You should simply replace the occurance of "ld" with "$(COMPILE)" in the Makefile.linux. It is always better to link also with gcc (it calls ld with the proper options) when using it for compilation. A quite good overview of tools and its options for creating libraries on a variety of platforms is here: http://www.fortran-2000.com/ArnaudRecipes/sharedlib.html. Cheers, Andreas > > Andreas, > > Andreas Wendt wrote: > > >Prashant, > > > >to verify, which additional libraries a shared library or an executable depend on, you may issue the command "ldd" on it. > >So "ldd wrapper" gives me on a SuSE Linux Enterprise 8 (I have no RedHat here): > > > > libc.so.6 => /lib/i686/libc.so.6 (0x40022000) > > /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) > > > >For libwrapper.so I get: > > statically linked > > > >(Leif: was the static linking for the JNI library intentional?) > > > > > No it was not intentional. As it long as it does not increase the > possibility of users > having compatibility problems, I would be happy to apply any patches to > clean this > up. :-) > > >The binaries are not linked with explicit library dependency, so the GNU linker decides which libraries to link in my default (libc.so in this case; ld-linux.so is linked in by libc.so and is no direct dependency). > > > >ldd will also show you if there are missing dependencies. > > > > > Cheers, > Leif > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user |
|
From: Leif M. <le...@ta...> - 2004-04-21 15:25:52
|
Andreas, Thanks, I modified both the Linux and Solaris versions so that they now dynamically link their libraries. Tested it with ldd. This will be in 3.1.1 Cheers, Leif Andreas Wendt wrote: >Leif, > >a patch is very simple. You should simply replace the occurance of "ld" with "$(COMPILE)" in the Makefile.linux. It is always better to link also with gcc (it calls ld with the proper options) when using it for compilation. > >A quite good overview of tools and its options for creating libraries on a variety of platforms is here: http://www.fortran-2000.com/ArnaudRecipes/sharedlib.html. > >Cheers, >Andreas > > |
|
From: Andy B. <aba...@ca...> - 2004-04-21 15:58:31
|
"The ldd command is not available in Mac OS X; however, you can use the command otool -L to get the same functionality that ldd does." - http://developer.apple.com/technotes/tn2002/tn2071.html Here's the results for the Mac OS X files: > % otool -L bin/wrapper > bin/wrapper: > /usr/lib/libcrypto.0.9.dylib (compatibility version 0.9.0, > current version 0.9.6) > /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, > current version 63.0.0) > % otool -L lib/libwrapper.jnilib > lib/libwrapper.jnilib: > /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, > current version 63.0.0) > I'm not an expert, but that appears to me to indicate that the Mac OS X files are not statically linked, so no change should be required for the Mac version. Cheers, ~Andy On Apr 21, 2004, at 10:25 AM, Leif Mortenson wrote: > Andreas, > Thanks, I modified both the Linux and Solaris versions so that they > now dynamically > link their libraries. Tested it with ldd. This will be in 3.1.1 > > Cheers, > Leif > > Andreas Wendt wrote: > >> Leif, >> >> a patch is very simple. You should simply replace the occurance of >> "ld" with "$(COMPILE)" in the Makefile.linux. It is always better to >> link also with gcc (it calls ld with the proper options) when using >> it for compilation. >> >> A quite good overview of tools and its options for creating libraries >> on a variety of platforms is here: >> http://www.fortran-2000.com/ArnaudRecipes/sharedlib.html. >> >> Cheers, >> Andreas |
|
From: Leif M. <le...@ta...> - 2004-04-21 16:05:10
|
Andy,
Thanks for checking. Both of the OSX files look like they have been
built correctly.
Cheers,
Leif
Andy Barnett wrote:
> "The ldd command is not available in Mac OS X; however, you can use
> the command otool -L to get the same functionality that ldd does." -
> http://developer.apple.com/technotes/tn2002/tn2071.html
>
> Here's the results for the Mac OS X files:
>
>> % otool -L bin/wrapper
>> bin/wrapper:
>> /usr/lib/libcrypto.0.9.dylib (compatibility version 0.9.0,
>> current version 0.9.6)
>> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0,
>> current version 63.0.0)
>
>
>> % otool -L lib/libwrapper.jnilib
>> lib/libwrapper.jnilib:
>> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0,
>> current version 63.0.0)
>>
>
> I'm not an expert, but that appears to me to indicate that the Mac OS
> X files are not statically linked, so no change should be required for
> the Mac version.
>
> Cheers,
> ~Andy
>
> On Apr 21, 2004, at 10:25 AM, Leif Mortenson wrote:
>
>> Andreas,
>> Thanks, I modified both the Linux and Solaris versions so that they
>> now dynamically
>> link their libraries. Tested it with ldd. This will be in 3.1.1
>>
>> Cheers,
>> Leif
>>
>> Andreas Wendt wrote:
>>
>>> Leif,
>>>
>>> a patch is very simple. You should simply replace the occurance of
>>> "ld" with "$(COMPILE)" in the Makefile.linux. It is always better to
>>> link also with gcc (it calls ld with the proper options) when using
>>> it for compilation.
>>>
>>> A quite good overview of tools and its options for creating
>>> libraries on a variety of platforms is here:
>>> http://www.fortran-2000.com/ArnaudRecipes/sharedlib.html.
>>>
>>> Cheers,
>>> Andreas
>>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
|
|
From: Mikko V. <mik...@so...> - 2004-04-21 19:27:31
|
Hi, Some of our clients are still using Win98 systems (!). We've built a small application which runs a HSQL database with Wrapper on win2k, but I was now wondering if it's possible to run Wrapper on win98 at all, or if it requires NT based operating systems or for example Linux to run? - mikko |
|
From: Sal I. <sal...@vo...> - 2004-04-21 20:22:09
|
i use wrapper 3.0 on win98 at a client installation. they've been running for 9 months without reporting any problems. using the wrapper is the closest thing to simulate an NT-service. when i reboot my machine i see wrapper starting up before the login prompt! btw, win98 has a cmd bug which prevents from assigning -D variables in .bat files: it doesn't like the equal signs of -Dprop=value, so running through the wrapper was the ONLY way i could get my app to work because the -D variables are in wrapper.conf, so win98 .bat files are not used!!! -----Original Message----- From: wra...@li... [mailto:wra...@li...]On Behalf Of Mikko Valjento Sent: Wednesday, April 21, 2004 12:27 PM To: wra...@li... Subject: [Wrapper-user] windows 98 Hi, Some of our clients are still using Win98 systems (!). We've built a small application which runs a HSQL database with Wrapper on win2k, but I was now wondering if it's possible to run Wrapper on win98 at all, or if it requires NT based operating systems or for example Linux to run? - mikko ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user |
|
From: Mikko V. <mik...@so...> - 2004-04-21 21:16:39
|
Sal, Thank you for the reply. That's good news. I will get my hands on a win98 system and try it out myself. - mikko -----Alkuperäinen viesti----- Lähettäjä: wra...@li... [mailto:wra...@li...]Puolesta Sal Ingrilli Lähetetty: 21. huhtikuuta 2004 23:21 Vastaanottaja: wra...@li... Aihe: RE: [Wrapper-user] windows 98 i use wrapper 3.0 on win98 at a client installation. they've been running for 9 months without reporting any problems. using the wrapper is the closest thing to simulate an NT-service. when i reboot my machine i see wrapper starting up before the login prompt! btw, win98 has a cmd bug which prevents from assigning -D variables in .bat files: it doesn't like the equal signs of -Dprop=value, so running through the wrapper was the ONLY way i could get my app to work because the -D variables are in wrapper.conf, so win98 .bat files are not used!!! -----Original Message----- From: wra...@li... [mailto:wra...@li...]On Behalf Of Mikko Valjento Sent: Wednesday, April 21, 2004 12:27 PM To: wra...@li... Subject: [Wrapper-user] windows 98 Hi, Some of our clients are still using Win98 systems (!). We've built a small application which runs a HSQL database with Wrapper on win2k, but I was now wondering if it's possible to run Wrapper on win98 at all, or if it requires NT based operating systems or for example Linux to run? - mikko ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user |
|
From: Leif M. <le...@ta...> - 2004-04-21 09:06:16
|
Andreas, Andreas Wendt wrote: >Prashant, > >to verify, which additional libraries a shared library or an executable depend on, you may issue the command "ldd" on it. >So "ldd wrapper" gives me on a SuSE Linux Enterprise 8 (I have no RedHat here): > > libc.so.6 => /lib/i686/libc.so.6 (0x40022000) > /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) > >For libwrapper.so I get: > statically linked > >(Leif: was the static linking for the JNI library intentional?) > > No it was not intentional. As it long as it does not increase the possibility of users having compatibility problems, I would be happy to apply any patches to clean this up. :-) >The binaries are not linked with explicit library dependency, so the GNU linker decides which libraries to link in my default (libc.so in this case; ld-linux.so is linked in by libc.so and is no direct dependency). > >ldd will also show you if there are missing dependencies. > > Cheers, Leif |