tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From vicky <>
Subject Re: JSVC error
Date Thu, 02 Jan 2014 17:06:20 GMT
I'm compiling & running JSVC on Linux machine ==>Red Hat Enterprise Linux Server release
6.3 (Santiago)

I tried the below steps but still i'm getting the segmetation error.

1. export CFLAGS=-m64
2.  ./configure
3.   make

Can somebody pls  share the source link for JSVC ,from where I can try downloading &
compiling the binaries again


On Thursday, 2 January 2014 10:06 PM, Mark Eggers <> wrote:
On 1/1/2014 11:02 PM, vicky wrote:
> I've build the JSVC on same machine over which I m running my tomcat instance
> I have compiled the JSVC in the following manner but still i'm getting the  Segmentation
fault  exception while executing the startup script, please suggest how to fix this:-
> Step1:
>   export CFLAGS="-arch i386 -arch x86_64"
>   export LDFLAGS="-arch i386 -arch x86_64"
> Step2:
> cd /root/test/commons-daemon-1.0.14-native-src/unix
>   ./configure
> ++++++++++++++++++++++++++++++++++++++++++++++=
> *** Current host ***
> checking build system type... x86_64-unknown-linux-gnu
> checking host system type... x86_64-unknown-linux-gnu
> checking cached host system type... ok
> *** C-Language compilation tools ***
> checking for gcc... gcc
> checking for C compiler default output file name... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... no
> checking for suffix of executables...
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ANSI C... none needed
> checking for ranlib... ranlib
> checking for strip... strip
> *** Host support ***
> checking C flags dependant on host system type... ok
> *** Java compilation tools ***
> checking for JDK os include directory...  linux
> gcc flags added
> checking for cap_init in -lcap... no
> *** Writing output files ***
> configure: creating ./config.status
> config.status: creating Makefile
> config.status: creating Makedefs
> config.status: creating native/Makefile
> *** All done ***
> Now you can issue "make"
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Step3:
> make
>   +++++++++++++++++++++command output +++++++++++++++++=
> (cd native; make  all)
> make[1]: Entering directory `/root/test/commons-daemon-1.0.14-native-src/unix/native'
> gcc -m64  jsvc-unix.o libservice.a -ldl -lpthread -o ../jsvc
> make[1]: Leaving directory `/root/test/commons-daemon-1.0.14-native-src/unix/native'
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>   Vicky
> From: André Warnier <>
> To: Tomcat Users List <>
> Sent: Tuesday, 31 December 2013 8:34 PM
> Subject: Re: JSVC error
> vicky wrote:
>> Even after defining the $CATALINA_PID & $JAVA_HOME variable , i'm still the getting
segmentation error(detailed error mentioned below)
> In my experience, a "segmentation fault" often occurs when the *binary* that you are
> trying to run, is not made for the platform on which you are trying to run it.
> For example, you try to use under Solaris a binary made for Linux; or trying to run a
> 64-bit binary on a 32-bit platform.  Stuff of that kind.
> So, are you sure that the "jsvc" that you're using matches your platform ?
> What about "file (path_to)/jsvc" ? what does it say ?


Your CFLAGS and LDFLAGS settings appear that you're trying to compile a 
"fat" binary on MacOS. Is this true?

If so, I don't think MacOS supports a 32 bit JRE any more. I'm not 
certain, since I don't have a Macintosh, but some people at $work do. 
They indicate that they can no longer run applets in Chrome (32 bit) but 
require Firefox or Safari (64 bit).

What happens when you don't use those flags (or at least not the -arch 
386 for those flags)?

. . . just my two cents

To unsubscribe, e-mail:
For additional commands, e-mail:
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message