|
From: Andreas W. <and...@em...> - 2005-02-28 09:13:34
|
Leif, unfortunately, I have no access to a A64 machine. But I found on Google, that you may have to add the '-m64' option to the link lines to force the compiler and linker to produce 64-bit binaries. If it still fails, I would enable the debug output of gcc to see, which other libraries it is trying to link into the JNI library. Perhaps one of them is not a 64-bit one. And they all should be shared libraries, not static ones. Cheers, Andreas > > Andreas, > Thanks, yes I got that far last night. But am now running into the > following error. > compile-c-unix: > if test ! -d .deps; then mkdir .deps; fi > gcc -O3 -fPIC -Wall --pedantic -pthread -DUSE_NANOSLEEP -lm wrapper.c > wrapperinfo.c wrappereventloop.c wrapper_unix.c property.c logger.c -o > ../../bin/wrapper > gcc -O3 -fPIC -Wall --pedantic -pthread -DUSE_NANOSLEEP -c wrapperinfo.c > gcc -O3 -fPIC -Wall --pedantic -pthread -DUSE_NANOSLEEP -shared > wrapperjni_unix.o wrapperinfo.o wrapperjni.o -o ../../lib/libwrapper.sl > /usr/bin/ld: wrapperjni_unix.o: relocation R_X86_64_32 can not be used > when making a shared object; recompile with -fPIC > wrapperjni_unix.o: could not read symbols: Bad value > collect2: ld returned 1 exit status > make: *** [libwrapper.sl] Error 1 > > From what little I have been able to find from Google, it appears to > be a linking problem > caused by a mismatch between libraries build with the -fPIC parameter > and one without. > Problem is that I think that all of the libraries being linked are being > build correctly. Still > investigating, but any ideas? > I also tried changing the target library name to .sl rather than .so > as is being done for > the HPUX-64 build. That appears to make no difference in the build, > didn't think it would. > I am still looking for the naming convention that is expected by the 64 > bit linux JVMs. > > The Wrapper binary is being built correctly, but the jni library is > not. Will post more if > I figure something out. > > Cheers, > Leif > > > Andreas Wendt wrote: > > >John, > > > >the function ceil is normally in the math library. > >Therefore, you should add a '-lm' to the link line in your Makefile: > > > >$(COMPILE) $(wrapper_SOURCE) -o $(BIN)/wrapper -lm > > > >Regards, > >Andreas > > > > > > > >>Hello Leif Mortenson, > >> > >>I have tried building this wrapper for a64 without much luck. It starts up > >>fine and finds ANT and JAVA_HOME but then it fails. I have tried with jvm > >>1.4.3 as well as 1.5. I've tried building it as user as well as root with > >>the source in /usr/src. > >> > >>The error I get: > >>Wrapper Build System > >>-------------------- > >>Buildfile: build.xml > >> > >>init: > >>OS='Linux' > >> > >>update-info: > >>Copying 1 file to > >>/usr/src/wrapper_3.1.2_src/src/java/org/tanukisoftware/wrapper > >>Copying 1 file to /usr/src/wrapper_3.1.2_src/src/c > >> > >>compile-java: > >>Compiling 1 source file to /usr/src/wrapper_3.1.2_src/build/classes > >> > >>compile-jni: > >>ClassArgument.name=org.tanukisoftware.wrapper.WrapperManager > >> > >>compile-c-unix: > >>if test ! -d .deps; then mkdir .deps; fi > >>gcc -O3 -Wall --pedantic -pthread -DUSE_NANOSLEEP wrapper.c wrapperinfo.c > >>wrappereventloop.c wrapper_unix.c property.c logger.c -o ../../bin/wrapper > >>/tmp/cces7BCe.o(.text+0x2f33): In function `wrapperStopPendingSignalled': > >>: undefined reference to `ceil' > >>/tmp/cces7BCe.o(.text+0x3064): In function `wrapperStartPendingSignalled': > >>: undefined reference to `ceil' > >>collect2: ld returned 1 exit status > >>make: *** [wrapper] Error 1 > >> > >>BUILD FAILED > >>/usr/src/wrapper_3.1.2_src/build.xml:328: exec returned: 2 > >> > >>Total time: 5 seconds > >> > >>Any suggestions? I currently don't have any production sites on this > >>server, could give you access if you want to give it a try. > >> > >>Thanks! > >> > >>John > >> > >> > >>------------------------------------------------------- > >>SF email is sponsored by - The IT Product Guide > >>Read honest & candid reviews on hundreds of IT Products from real users. > >>Discover which products truly live up to the hype. Start reading now. > >>http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > >>_______________________________________________ > >>Wrapper-user mailing list > >>Wra...@li... > >>https://lists.sourceforge.net/lists/listinfo/wrapper-user > >> > >> > > > > > > > > > > > >------------------------------------------------------- > >SF email is sponsored by - The IT Product Guide > >Read honest & candid reviews on hundreds of IT Products from real users. > >Discover which products truly live up to the hype. Start reading now. > >http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > >_______________________________________________ > >Wrapper-user mailing list > >Wra...@li... > >https://lists.sourceforge.net/lists/listinfo/wrapper-user > > > > > > > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user |
|
From: <b....@ve...> - 2005-02-28 09:26:24
|
Hi! I have a java client/server application client accessing to server over=20 RMI. As I want to start the server with wrapper, I get=20 java.security.AccessControlException: access denied=20 (java.net.SocketpermissionException 225.225.225.225=20 connect,accept,resolve). How must I configure the wrapper to read my=20 java.policy file. Should I do anything else? Please help! Mit freundlichen Gruessen / Best regards =20 Dipl.Ing. Bab=FCr Somer Entwicklung und Beratung =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F Vector SW DV GmbH=20 fon: +43 1 216 50 40 -146 | Lassallestrasse 7a A 1020 Wien fax: +43 1 216 50 40 -50 |=20 =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F =20 |
|
From: Bashiro <ba...@en...> - 2005-02-28 11:02:19
|
Hello, do you use proxy ? bashiro > Hi! > > I have a java client/server application client accessing to server over > RMI. As I want to start the server with wrapper, I get > java.security.AccessControlException: access denied > (java.net.SocketpermissionException 225.225.225.225 > connect,accept,resolve). How must I configure the wrapper to read my > java.policy file. Should I do anything else? > > Please help! > > Mit freundlichen Gruessen / Best regards > > Dipl.Ing. Babür Somer > Entwicklung und Beratung > _____________________________________________________ > Vector SW DV GmbH > fon: +43 1 216 50 40 -146 > | > Lassallestrasse 7a A 1020 Wien > fax: +43 1 216 50 40 -50 > | > _____________________________________________________ > > |
|
From: <b....@ve...> - 2005-02-28 14:03:38
|
Hello! i'm on the intranet behind the firewall. The server has nothing to do with = the proxy. Because I can start it normally telling it where to find the=20 java.policy file. My wrapper.config file is as follows: #******************************************************************** # TestWrapper Properties # # NOTE - Please use src/conf/wrapper.conf.in as a template for your # own application rather than the values used for the # TestWrapper sample. #******************************************************************** # Java Application wrapper.java.command=3Djava # Java Main class. This class must implement the WrapperListener=20 interface # or guarantee that the WrapperManager class is initialized. Helper # classes are provided to do this for you. See the Integration section # of the documentation for details. wrapper.java.mainclass=3Dat.vector.cdp4j.comm.Server # Java Classpath (include wrapper.jar) Add class path elements as # needed starting from 1 wrapper.java.classpath.1=3D../build/CDP4J=5Fserver-NIGHTLY.jar wrapper.java.classpath.2=3D../build/CDP4J=5Fcommon-NIGHTLY.jar wrapper.java.classpath.3=3D../libs/commons-lang-2.0.jar wrapper.java.classpath.4=3D../libs/jt400.jar wrapper.java.classpath.5=3D../libs/x4j400.jar wrapper.java.classpath.6=3D../libs/wrapper.jar # Java Library Path (location of Wrapper.DLL or libwrapper.so) wrapper.java.library.path.1=3D../build # Java Additional Parameters wrapper.java.additional.1=3D-cp wrapper.java.additional.2=3D-Djava.security.policy=3D../ressources/java.pol= icy wrapper.java.additional.3=3D-Dhome=3D../ wrapper.java.additional.4=3D-Dcdpworld.dir=3D. wrapper.java.additional.5=3D-Djava.rmi.server.hostname=3Dlocalhost # Initial Java Heap Size (in MB) wrapper.java.initmemory=3D64 # Maximum Java Heap Size (in MB) wrapper.java.maxmemory=3D256 # Application parameters. Add parameters as needed starting from 1 wrapper.app.parameter.1=3Dat.vector.cdp4j.comm.Server wrapper.app.parameter.2=3D-Djava.security.policy=3D../ressources/java.policy #******************************************************************** # Wrapper Logging Properties #******************************************************************** # Format of output for the console. (See docs for formats) wrapper.console.format=3DPM # Log Level for console output. (See docs for log levels) wrapper.console.loglevel=3DINFO # Log file to use for wrapper output logging. wrapper.logfile=3D../logs/wrapper.log # Format of output for the log file. (See docs for formats) wrapper.logfile.format=3DLPTM # Log Level for log file output. (See docs for log levels) wrapper.logfile.loglevel=3DINFO # Maximum size that the log file will be allowed to grow to before # the log is rolled. Size is specified in bytes. The default value # of 0, disables log rolling. May abbreviate with the 'k' (kb) or # 'm' (mb) suffix. For example: 10m =3D 10 megabytes. wrapper.logfile.maxsize=3D0 # Maximum number of rolled log files which will be allowed before old # files are deleted. The default value of 0 implies no limit. wrapper.logfile.maxfiles=3D0 # Log Level for sys/event log output. (See docs for log levels) wrapper.syslog.loglevel=3DNONE #******************************************************************** # Wrapper Windows Properties #******************************************************************** # Title to use when running as a console wrapper.console.title=3DTest Wrapper for CDPworld Server Application #******************************************************************** # Wrapper Windows NT/2000/XP Service Properties #******************************************************************** # WARNING - Do not modify any of these properties when an application # using this configuration file has been installed as a service. # Please uninstall the service before modifying this section. The # service can then be reinstalled. # Name of the service wra...@ap...@ # Display name of the service wrapper.ntservice.displayname=3DCDPworld Server # Description of the service wrapper.ntservice.description=3DCDPworld Server Application as service # Service dependencies. Add dependencies as needed starting from 1 wrapper.ntservice.dependency.1=3D # Mode in which the service is installed. AUTO=5FSTART or DEMAND=5FSTART wrapper.ntservice.starttype=3DAUTO=5FSTART # Allow the service to interact with the desktop. wrapper.ntservice.interactive=3Dfalse Mit freundlichen Gruessen / Best regards =20 Dipl.Ing. Bab=FCr Somer Entwicklung und Beratung =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F Vector SW DV GmbH=20 fon: +43 1 216 50 40 -146 | Lassallestrasse 7a A 1020 Wien fax: +43 1 216 50 40 -50 |=20 Besuchen Sie uns auf der Vienna Autoshow! 15.-18. J=E4nner 2004, Halle D, Stand 524 =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F =20 "Bashiro" <ba...@en...>=20 Sent by: wra...@li... 28.02.2005 12:02 Please respond to wra...@li... To wra...@li... cc Subject Re: [Wrapper-user] Access Denied problem Hello, do you use proxy ? bashiro > Hi! > > I have a java client/server application client accessing to server over > RMI. As I want to start the server with wrapper, I get > java.security.AccessControlException: access denied > (java.net.SocketpermissionException 225.225.225.225 > connect,accept,resolve). How must I configure the wrapper to read my > java.policy file. Should I do anything else? > > Please help! > > Mit freundlichen Gruessen / Best regards > > Dipl.Ing. Bab=FCr Somer > Entwicklung und Beratung > =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F > Vector SW DV GmbH > fon: +43 1 216 50 40 -146 > | > Lassallestrasse 7a A 1020 Wien > fax: +43 1 216 50 40 -50 > | > =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F > > ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad=5Fid=3D6595&alloc=5Fid=3D14396&op=3Dclick =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user ForwardSourceID:NT00008942=20 |
|
From: <mai...@st...> - 2005-03-03 20:36:14
|
Hello Leif, Any luck with the A64? Im beginning to wonder if i should have stuck with the Xeons. John > Leif, > > unfortunately, I have no access to a A64 machine. > But I found on Google, that you may have to add the '-m64' option to the > link lines to force the compiler and linker to produce 64-bit binaries. > If it still fails, I would enable the debug output of gcc to see, which > other libraries it is trying to link into the JNI library. > Perhaps one of them is not a 64-bit one. And they all should be shared > libraries, not static ones. > > Cheers, > Andreas > >> >> Andreas, >> Thanks, yes I got that far last night. But am now running into the >> following error. >> compile-c-unix: >> if test ! -d .deps; then mkdir .deps; fi >> gcc -O3 -fPIC -Wall --pedantic -pthread -DUSE_NANOSLEEP -lm wrapper.c >> wrapperinfo.c wrappereventloop.c wrapper_unix.c property.c logger.c -o >> ../../bin/wrapper >> gcc -O3 -fPIC -Wall --pedantic -pthread -DUSE_NANOSLEEP -c wrapperinfo.c >> gcc -O3 -fPIC -Wall --pedantic -pthread -DUSE_NANOSLEEP -shared >> wrapperjni_unix.o wrapperinfo.o wrapperjni.o -o ../../lib/libwrapper.sl >> /usr/bin/ld: wrapperjni_unix.o: relocation R_X86_64_32 can not be used >> when making a shared object; recompile with -fPIC >> wrapperjni_unix.o: could not read symbols: Bad value >> collect2: ld returned 1 exit status >> make: *** [libwrapper.sl] Error 1 >> >> From what little I have been able to find from Google, it appears to >> be a linking problem >> caused by a mismatch between libraries build with the -fPIC parameter >> and one without. >> Problem is that I think that all of the libraries being linked are being >> build correctly. Still >> investigating, but any ideas? >> I also tried changing the target library name to .sl rather than .so >> as is being done for >> the HPUX-64 build. That appears to make no difference in the build, >> didn't think it would. >> I am still looking for the naming convention that is expected by the 64 >> bit linux JVMs. >> >> The Wrapper binary is being built correctly, but the jni library is >> not. Will post more if >> I figure something out. >> >> Cheers, >> Leif >> >> >> Andreas Wendt wrote: >> >> >John, >> > >> >the function ceil is normally in the math library. >> >Therefore, you should add a '-lm' to the link line in your Makefile: >> > >> >$(COMPILE) $(wrapper_SOURCE) -o $(BIN)/wrapper -lm >> > >> >Regards, >> >Andreas >> > >> > >> > >> >>Hello Leif Mortenson, >> >> >> >>I have tried building this wrapper for a64 without much luck. It >> starts up >> >>fine and finds ANT and JAVA_HOME but then it fails. I have tried with >> jvm >> >>1.4.3 as well as 1.5. I've tried building it as user as well as root >> with >> >>the source in /usr/src. >> >> >> >>The error I get: >> >>Wrapper Build System >> >>-------------------- >> >>Buildfile: build.xml >> >> >> >>init: >> >>OS='Linux' >> >> >> >>update-info: >> >>Copying 1 file to >> >>/usr/src/wrapper_3.1.2_src/src/java/org/tanukisoftware/wrapper >> >>Copying 1 file to /usr/src/wrapper_3.1.2_src/src/c >> >> >> >>compile-java: >> >>Compiling 1 source file to /usr/src/wrapper_3.1.2_src/build/classes >> >> >> >>compile-jni: >> >>ClassArgument.name=org.tanukisoftware.wrapper.WrapperManager >> >> >> >>compile-c-unix: >> >>if test ! -d .deps; then mkdir .deps; fi >> >>gcc -O3 -Wall --pedantic -pthread -DUSE_NANOSLEEP wrapper.c >> wrapperinfo.c >> >>wrappereventloop.c wrapper_unix.c property.c logger.c -o >> ../../bin/wrapper >> >>/tmp/cces7BCe.o(.text+0x2f33): In function >> `wrapperStopPendingSignalled': >> >>: undefined reference to `ceil' >> >>/tmp/cces7BCe.o(.text+0x3064): In function >> `wrapperStartPendingSignalled': >> >>: undefined reference to `ceil' >> >>collect2: ld returned 1 exit status >> >>make: *** [wrapper] Error 1 >> >> >> >>BUILD FAILED >> >>/usr/src/wrapper_3.1.2_src/build.xml:328: exec returned: 2 >> >> >> >>Total time: 5 seconds >> >> >> >>Any suggestions? I currently don't have any production sites on this >> >>server, could give you access if you want to give it a try. >> >> >> >>Thanks! >> >> >> >>John >> >> >> >> >> >>------------------------------------------------------- >> >>SF email is sponsored by - The IT Product Guide >> >>Read honest & candid reviews on hundreds of IT Products from real >> users. >> >>Discover which products truly live up to the hype. Start reading now. >> >>http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >> >>_______________________________________________ >> >>Wrapper-user mailing list >> >>Wra...@li... >> >>https://lists.sourceforge.net/lists/listinfo/wrapper-user >> >> >> >> >> > >> > >> > >> > >> > >> >------------------------------------------------------- >> >SF email is sponsored by - The IT Product Guide >> >Read honest & candid reviews on hundreds of IT Products from real >> users. >> >Discover which products truly live up to the hype. Start reading now. >> >http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >> >_______________________________________________ >> >Wrapper-user mailing list >> >Wra...@li... >> >https://lists.sourceforge.net/lists/listinfo/wrapper-user >> > >> > >> > >> >> >> >> ------------------------------------------------------- >> SF email is sponsored by - The IT Product Guide >> Read honest & candid reviews on hundreds of IT Products from real users. >> Discover which products truly live up to the hype. Start reading now. >> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >> _______________________________________________ >> Wrapper-user mailing list >> Wra...@li... >> https://lists.sourceforge.net/lists/listinfo/wrapper-user > > > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |
|
From: Leif M. <le...@ta...> - 2005-03-11 07:33:48
|
John and I have been talking off line but wanted to post on the list as well. After playing with trying to get a 64-bit native version of the Wrapper working for a while, I had realized that the JVM being run was 32-bit. I tried the regular 32-bit version of the Wrapper with that JVM and it works file out of the box. The 64-bit version of the Wrapper does not of course work with the 32-bit JVM. But I have not yet had the opportunity to try it with a 64-bit JVM on the A64 system. It is building however. Cheers, Leif mai...@st... wrote: >Hello Leif, > >Any luck with the A64? Im beginning to wonder if i should have stuck with >the Xeons. > >John > > > >>Leif, >> >>unfortunately, I have no access to a A64 machine. >>But I found on Google, that you may have to add the '-m64' option to the >>link lines to force the compiler and linker to produce 64-bit binaries. >>If it still fails, I would enable the debug output of gcc to see, which >>other libraries it is trying to link into the JNI library. >>Perhaps one of them is not a 64-bit one. And they all should be shared >>libraries, not static ones. >> >>Cheers, >>Andreas >> >> >> >>>Andreas, >>> Thanks, yes I got that far last night. But am now running into the >>>following error. >>>compile-c-unix: >>>if test ! -d .deps; then mkdir .deps; fi >>>gcc -O3 -fPIC -Wall --pedantic -pthread -DUSE_NANOSLEEP -lm wrapper.c >>>wrapperinfo.c wrappereventloop.c wrapper_unix.c property.c logger.c -o >>>../../bin/wrapper >>>gcc -O3 -fPIC -Wall --pedantic -pthread -DUSE_NANOSLEEP -c wrapperinfo.c >>>gcc -O3 -fPIC -Wall --pedantic -pthread -DUSE_NANOSLEEP -shared >>>wrapperjni_unix.o wrapperinfo.o wrapperjni.o -o ../../lib/libwrapper.sl >>>/usr/bin/ld: wrapperjni_unix.o: relocation R_X86_64_32 can not be used >>>when making a shared object; recompile with -fPIC >>>wrapperjni_unix.o: could not read symbols: Bad value >>>collect2: ld returned 1 exit status >>>make: *** [libwrapper.sl] Error 1 >>> >>> From what little I have been able to find from Google, it appears to >>>be a linking problem >>>caused by a mismatch between libraries build with the -fPIC parameter >>>and one without. >>>Problem is that I think that all of the libraries being linked are being >>>build correctly. Still >>>investigating, but any ideas? >>> I also tried changing the target library name to .sl rather than .so >>>as is being done for >>>the HPUX-64 build. That appears to make no difference in the build, >>>didn't think it would. >>>I am still looking for the naming convention that is expected by the 64 >>>bit linux JVMs. >>> >>> The Wrapper binary is being built correctly, but the jni library is >>>not. Will post more if >>>I figure something out. >>> >>>Cheers, >>>Leif >>> >>> >>>Andreas Wendt wrote: >>> >>> >>> >>>>John, >>>> >>>>the function ceil is normally in the math library. >>>>Therefore, you should add a '-lm' to the link line in your Makefile: >>>> >>>>$(COMPILE) $(wrapper_SOURCE) -o $(BIN)/wrapper -lm >>>> >>>>Regards, >>>>Andreas >>>> >>>> >>>> >>>> >>>> >>>>>Hello Leif Mortenson, >>>>> >>>>>I have tried building this wrapper for a64 without much luck. It >>>>> >>>>> >>>starts up >>> >>> >>>>>fine and finds ANT and JAVA_HOME but then it fails. I have tried with >>>>> >>>>> >>>jvm >>> >>> >>>>>1.4.3 as well as 1.5. I've tried building it as user as well as root >>>>> >>>>> >>>with >>> >>> >>>>>the source in /usr/src. >>>>> >>>>>The error I get: >>>>>Wrapper Build System >>>>>-------------------- >>>>>Buildfile: build.xml >>>>> >>>>>init: >>>>>OS='Linux' >>>>> >>>>>update-info: >>>>>Copying 1 file to >>>>>/usr/src/wrapper_3.1.2_src/src/java/org/tanukisoftware/wrapper >>>>>Copying 1 file to /usr/src/wrapper_3.1.2_src/src/c >>>>> >>>>>compile-java: >>>>>Compiling 1 source file to /usr/src/wrapper_3.1.2_src/build/classes >>>>> >>>>>compile-jni: >>>>>ClassArgument.name=org.tanukisoftware.wrapper.WrapperManager >>>>> >>>>>compile-c-unix: >>>>>if test ! -d .deps; then mkdir .deps; fi >>>>>gcc -O3 -Wall --pedantic -pthread -DUSE_NANOSLEEP wrapper.c >>>>> >>>>> >>>wrapperinfo.c >>> >>> >>>>>wrappereventloop.c wrapper_unix.c property.c logger.c -o >>>>> >>>>> >>>../../bin/wrapper >>> >>> >>>>>/tmp/cces7BCe.o(.text+0x2f33): In function >>>>> >>>>> >>>`wrapperStopPendingSignalled': >>> >>> >>>>>: undefined reference to `ceil' >>>>>/tmp/cces7BCe.o(.text+0x3064): In function >>>>> >>>>> >>>`wrapperStartPendingSignalled': >>> >>> >>>>>: undefined reference to `ceil' >>>>>collect2: ld returned 1 exit status >>>>>make: *** [wrapper] Error 1 >>>>> >>>>>BUILD FAILED >>>>>/usr/src/wrapper_3.1.2_src/build.xml:328: exec returned: 2 >>>>> >>>>>Total time: 5 seconds >>>>> >>>>>Any suggestions? I currently don't have any production sites on this >>>>>server, could give you access if you want to give it a try. >>>>> >>>>>Thanks! >>>>> >>>>>John >>>>> >>>>> >>>>>------------------------------------------------------- >>>>>SF email is sponsored by - The IT Product Guide >>>>>Read honest & candid reviews on hundreds of IT Products from real >>>>> >>>>> >>>users. >>> >>> >>>>>Discover which products truly live up to the hype. Start reading now. >>>>>http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >>>>>_______________________________________________ >>>>>Wrapper-user mailing list >>>>>Wra...@li... >>>>>https://lists.sourceforge.net/lists/listinfo/wrapper-user >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> >>>>------------------------------------------------------- >>>>SF email is sponsored by - The IT Product Guide >>>>Read honest & candid reviews on hundreds of IT Products from real >>>> >>>> >>>users. >>> >>> >>>>Discover which products truly live up to the hype. Start reading now. >>>>http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >>>>_______________________________________________ >>>>Wrapper-user mailing list >>>>Wra...@li... >>>>https://lists.sourceforge.net/lists/listinfo/wrapper-user >>>> >>>> >>>> >>>> >>>> >>> >>>------------------------------------------------------- >>>SF email is sponsored by - The IT Product Guide >>>Read honest & candid reviews on hundreds of IT Products from real users. >>>Discover which products truly live up to the hype. Start reading now. >>>http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >>>_______________________________________________ >>>Wrapper-user mailing list >>>Wra...@li... >>>https://lists.sourceforge.net/lists/listinfo/wrapper-user >>> >>> >> >> >> >>------------------------------------------------------- >>SF email is sponsored by - The IT Product Guide >>Read honest & candid reviews on hundreds of IT Products from real users. >>Discover which products truly live up to the hype. Start reading now. >>http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >>_______________________________________________ >>Wrapper-user mailing list >>Wra...@li... >>https://lists.sourceforge.net/lists/listinfo/wrapper-user >> >> >> > > >------------------------------------------------------- >SF email is sponsored by - The IT Product Guide >Read honest & candid reviews on hundreds of IT Products from real users. >Discover which products truly live up to the hype. Start reading now. >http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >_______________________________________________ >Wrapper-user mailing list >Wra...@li... >https://lists.sourceforge.net/lists/listinfo/wrapper-user > > > |
|
From: <mai...@st...> - 2005-03-11 19:09:21
|
Hello Leif, No, I was running the 64bit JVM versions until I found out through researching a JBOSS issue that 64bit jvm has problems, I think especially on the AMD64. But yeah the 32bit wrapper works nicely with the 32bit JVM. Thanks! John > John and I have been talking off line but wanted to post on the list as > well. > After playing with trying to get a 64-bit native version of the Wrapper > working for a while, > I had realized that the JVM being run was 32-bit. I tried the regular > 32-bit version of > the Wrapper with that JVM and it works file out of the box. > > The 64-bit version of the Wrapper does not of course work with the > 32-bit JVM. But > I have not yet had the opportunity to try it with a 64-bit JVM on the > A64 system. It is > building however. > > Cheers, > Leif > > > mai...@st... wrote: > >>Hello Leif, >> >>Any luck with the A64? Im beginning to wonder if i should have stuck with >>the Xeons. >> >>John >> >> >> >>>Leif, >>> >>>unfortunately, I have no access to a A64 machine. >>>But I found on Google, that you may have to add the '-m64' option to the >>>link lines to force the compiler and linker to produce 64-bit binaries. >>>If it still fails, I would enable the debug output of gcc to see, which >>>other libraries it is trying to link into the JNI library. >>>Perhaps one of them is not a 64-bit one. And they all should be shared >>>libraries, not static ones. >>> >>>Cheers, >>>Andreas >>> >>> >>> >>>>Andreas, >>>> Thanks, yes I got that far last night. But am now running into the >>>>following error. >>>>compile-c-unix: >>>>if test ! -d .deps; then mkdir .deps; fi >>>>gcc -O3 -fPIC -Wall --pedantic -pthread -DUSE_NANOSLEEP -lm wrapper.c >>>>wrapperinfo.c wrappereventloop.c wrapper_unix.c property.c logger.c -o >>>>../../bin/wrapper >>>>gcc -O3 -fPIC -Wall --pedantic -pthread -DUSE_NANOSLEEP -c >>>> wrapperinfo.c >>>>gcc -O3 -fPIC -Wall --pedantic -pthread -DUSE_NANOSLEEP -shared >>>>wrapperjni_unix.o wrapperinfo.o wrapperjni.o -o ../../lib/libwrapper.sl >>>>/usr/bin/ld: wrapperjni_unix.o: relocation R_X86_64_32 can not be used >>>>when making a shared object; recompile with -fPIC >>>>wrapperjni_unix.o: could not read symbols: Bad value >>>>collect2: ld returned 1 exit status >>>>make: *** [libwrapper.sl] Error 1 >>>> >>>> From what little I have been able to find from Google, it appears >>>> to >>>>be a linking problem >>>>caused by a mismatch between libraries build with the -fPIC parameter >>>>and one without. >>>>Problem is that I think that all of the libraries being linked are >>>> being >>>>build correctly. Still >>>>investigating, but any ideas? >>>> I also tried changing the target library name to .sl rather than >>>> .so >>>>as is being done for >>>>the HPUX-64 build. That appears to make no difference in the build, >>>>didn't think it would. >>>>I am still looking for the naming convention that is expected by the 64 >>>>bit linux JVMs. >>>> >>>> The Wrapper binary is being built correctly, but the jni library is >>>>not. Will post more if >>>>I figure something out. >>>> >>>>Cheers, >>>>Leif >>>> >>>> >>>>Andreas Wendt wrote: >>>> >>>> >>>> >>>>>John, >>>>> >>>>>the function ceil is normally in the math library. >>>>>Therefore, you should add a '-lm' to the link line in your Makefile: >>>>> >>>>>$(COMPILE) $(wrapper_SOURCE) -o $(BIN)/wrapper -lm >>>>> >>>>>Regards, >>>>>Andreas >>>>> >>>>> >>>>> >>>>> >>>>> >>>>>>Hello Leif Mortenson, >>>>>> >>>>>>I have tried building this wrapper for a64 without much luck. It >>>>>> >>>>>> >>>>starts up >>>> >>>> >>>>>>fine and finds ANT and JAVA_HOME but then it fails. I have tried with >>>>>> >>>>>> >>>>jvm >>>> >>>> >>>>>>1.4.3 as well as 1.5. I've tried building it as user as well as root >>>>>> >>>>>> >>>>with >>>> >>>> >>>>>>the source in /usr/src. >>>>>> >>>>>>The error I get: >>>>>>Wrapper Build System >>>>>>-------------------- >>>>>>Buildfile: build.xml >>>>>> >>>>>>init: >>>>>>OS='Linux' >>>>>> >>>>>>update-info: >>>>>>Copying 1 file to >>>>>>/usr/src/wrapper_3.1.2_src/src/java/org/tanukisoftware/wrapper >>>>>>Copying 1 file to /usr/src/wrapper_3.1.2_src/src/c >>>>>> >>>>>>compile-java: >>>>>>Compiling 1 source file to /usr/src/wrapper_3.1.2_src/build/classes >>>>>> >>>>>>compile-jni: >>>>>>ClassArgument.name=org.tanukisoftware.wrapper.WrapperManager >>>>>> >>>>>>compile-c-unix: >>>>>>if test ! -d .deps; then mkdir .deps; fi >>>>>>gcc -O3 -Wall --pedantic -pthread -DUSE_NANOSLEEP wrapper.c >>>>>> >>>>>> >>>>wrapperinfo.c >>>> >>>> >>>>>>wrappereventloop.c wrapper_unix.c property.c logger.c -o >>>>>> >>>>>> >>>>../../bin/wrapper >>>> >>>> >>>>>>/tmp/cces7BCe.o(.text+0x2f33): In function >>>>>> >>>>>> >>>>`wrapperStopPendingSignalled': >>>> >>>> >>>>>>: undefined reference to `ceil' >>>>>>/tmp/cces7BCe.o(.text+0x3064): In function >>>>>> >>>>>> >>>>`wrapperStartPendingSignalled': >>>> >>>> >>>>>>: undefined reference to `ceil' >>>>>>collect2: ld returned 1 exit status >>>>>>make: *** [wrapper] Error 1 >>>>>> >>>>>>BUILD FAILED >>>>>>/usr/src/wrapper_3.1.2_src/build.xml:328: exec returned: 2 >>>>>> >>>>>>Total time: 5 seconds >>>>>> >>>>>>Any suggestions? I currently don't have any production sites on this >>>>>>server, could give you access if you want to give it a try. >>>>>> >>>>>>Thanks! >>>>>> >>>>>>John >>>>>> >>>>>> >>>>>>------------------------------------------------------- >>>>>>SF email is sponsored by - The IT Product Guide >>>>>>Read honest & candid reviews on hundreds of IT Products from real >>>>>> >>>>>> >>>>users. >>>> >>>> >>>>>>Discover which products truly live up to the hype. Start reading now. >>>>>>http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >>>>>>_______________________________________________ >>>>>>Wrapper-user mailing list >>>>>>Wra...@li... >>>>>>https://lists.sourceforge.net/lists/listinfo/wrapper-user >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>>>------------------------------------------------------- >>>>>SF email is sponsored by - The IT Product Guide >>>>>Read honest & candid reviews on hundreds of IT Products from real >>>>> >>>>> >>>>users. >>>> >>>> >>>>>Discover which products truly live up to the hype. Start reading now. >>>>>http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >>>>>_______________________________________________ >>>>>Wrapper-user mailing list >>>>>Wra...@li... >>>>>https://lists.sourceforge.net/lists/listinfo/wrapper-user >>>>> >>>>> >>>>> >>>>> >>>>> >>>> >>>>------------------------------------------------------- >>>>SF email is sponsored by - The IT Product Guide >>>>Read honest & candid reviews on hundreds of IT Products from real >>>> users. >>>>Discover which products truly live up to the hype. Start reading now. >>>>http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >>>>_______________________________________________ >>>>Wrapper-user mailing list >>>>Wra...@li... >>>>https://lists.sourceforge.net/lists/listinfo/wrapper-user >>>> >>>> >>> >>> >>> >>>------------------------------------------------------- >>>SF email is sponsored by - The IT Product Guide >>>Read honest & candid reviews on hundreds of IT Products from real users. >>>Discover which products truly live up to the hype. Start reading now. >>>http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >>>_______________________________________________ >>>Wrapper-user mailing list >>>Wra...@li... >>>https://lists.sourceforge.net/lists/listinfo/wrapper-user >>> >>> >>> >> >> >>------------------------------------------------------- >>SF email is sponsored by - The IT Product Guide >>Read honest & candid reviews on hundreds of IT Products from real users. >>Discover which products truly live up to the hype. Start reading now. >>http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >>_______________________________________________ >>Wrapper-user mailing list >>Wra...@li... >>https://lists.sourceforge.net/lists/listinfo/wrapper-user >> >> >> > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |