Re: Can't compile jk nativ connector under Suse 9.3
William A. Rowe, Jr. wrote: At 01:32 AM 4/27/2005, Mladen Turk wrote: William A. Rowe, Jr. wrote: ... Thank you; but the other half of my question... It was my fault. SD_SEND is defined only on winsock. On other platforms it is 1. Already committed a fix. Why a Win32 fix rather than a proper posix fix? I suspect you were looking for SHUT_WR in sys/socket.h. Even my most crufty 2.95 gcc compilers offer it. SHUT_WR and other are also in the sys/socket.h of Solaris and BS2000 ;-) Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Can't compile jk nativ connector under Suse 9.3
At 11:02 PM 4/26/2005, Peter Rossbach wrote: here the configure output ... Thank you; but the other half of my question... make[1]: Entering directory `/home/peter/develop/tomcat/jakarta-tomcat-connectors/jk/native/common' /bin/sh /home/peter/server/apache2/build/libtool --silent --mode=compile gcc -I/home/peter/server/apache2/include -g -O2 -g -O2 -pthread -DHAVE_APR -I/home/peter/server/httpd-2.0.54/srclib/apr/include -g -O2 -DLINUX=2 -D_REENTRANT -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -I /usr/java/jdk1.5.0_02/include -I /usr/java/jdk1.5.0_02/include/ -c jk_connect.c jk_connect.c: In function `jk_shutdown_socket': jk_connect.c:485: error: `SD_SEND' undeclared (first use in this function) jk_connect.c:485: error: (Each undeclared identifier is reported only once jk_connect.c:485: error: for each function it appears in.) William A. Rowe, Jr. schrieb: grep -r SD_SEND /usr/include/* grep -r SD_SEND /usr/local/include/* ? Tell us where it's hidden and it's more likely we can come up with an appropriate patch. You seem to presume I run your version of suse here. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Can't compile jk nativ connector under Suse 9.3
William A. Rowe, Jr. wrote: here the configure output ... Thank you; but the other half of my question... It was my fault. SD_SEND is defined only on winsock. On other platforms it is 1. Already committed a fix. Regards, Mladen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Can't compile jk nativ connector under Suse 9.3
At 01:32 AM 4/27/2005, Mladen Turk wrote: William A. Rowe, Jr. wrote: ... Thank you; but the other half of my question... It was my fault. SD_SEND is defined only on winsock. On other platforms it is 1. Already committed a fix. Why a Win32 fix rather than a proper posix fix? I suspect you were looking for SHUT_WR in sys/socket.h. Even my most crufty 2.95 gcc compilers offer it. Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Can't compile jk nativ connector under Suse 9.3
I have a jk native compilation problem at suse 9.3 with the current CVS HEAD. Can't compile jk_connect.c jk_connect.c: In function 'jk_shutdown_socket' : jk_connect.c:485: error 'SD_SEND' undeclared (first use in this function) jk_connect.c:485: error (Each unde ... How can I find the missing SD_SEND declaration? Peter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Can't compile jk nativ connector under Suse 9.3
Peter Rossbach wrote: I have a jk native compilation problem at suse 9.3 with the current CVS HEAD. According to posix: If how is 0, further receives will be disallowed. If how is 1, further sends will be disallowed. If how is 2, further sends and receives will be disallowed. So ... #ifnedf SD_SEND #define SD_SEND 1 #endif Should do the trick. Regards, Mladen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Can't compile jk nativ connector under Suse 9.3
grep -r SD_SEND /usr/include/* grep -r SD_SEND /usr/local/include/* ? Tell us where it's hidden and it's more likely we can come up with an appropriate patch. Any ./configure output would also be helpful. At 01:01 PM 4/26/2005, Peter Rossbach wrote: I have a jk native compilation problem at suse 9.3 with the current CVS HEAD. Can't compile jk_connect.c jk_connect.c: In function 'jk_shutdown_socket' : jk_connect.c:485: error 'SD_SEND' undeclared (first use in this function) jk_connect.c:485: error (Each unde ... How can I find the missing SD_SEND declaration? Peter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Can't compile jk nativ connector under Suse 9.3
Hey, here the configure output [EMAIL PROTECTED]:~/develop/tomcat/jakarta-tomcat-connectors/jk/native ./configure --with-apxs=/home/peter/server/apache2/bin/apxs checking build system type... i686-suse-linux checking host system type... i686-suse-linux checking target system type... i686-suse-linux checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes 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 style of include used by make... GNU checking dependency style of gcc... none checking for a sed that does not truncate output... /usr/bin/sed checking for egrep... grep -E checking for ld used by gcc... /usr/i586-suse-linux/bin/ld checking if the linker (/usr/i586-suse-linux/bin/ld) is GNU ld... yes checking for /usr/i586-suse-linux/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -B checking whether ln -s works... yes checking how to recognise dependent libraries... pass_all checking how to run the C preprocessor... gcc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking dependency style of g++... none checking how to run the C++ preprocessor... g++ -E checking for g77... no checking for f77... no checking for xlf... no checking for frt... no checking for pgf77... no checking for fort77... no checking for fl32... no checking for af77... no checking for f90... no checking for xlf90... no checking for pgf90... no checking for epcf90... no checking for f95... no checking for fort... no checking for xlf95... no checking for ifc... no checking for efc... no checking for pgf95... no checking for lf95... no checking for gfortran... no checking whether we are using the GNU Fortran 77 compiler... no checking whether accepts -g... no checking the maximum length of command line arguments... 32768 checking command to parse /usr/bin/nm -B output from gcc object... ok checking for objdir... .libs checking for ar... ar checking for ranlib... ranlib checking for strip... strip checking if gcc static flag works... yes checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC checking if gcc PIC flag -fPIC works... yes checking if gcc supports -c -o file.o... yes checking whether the gcc linker (/usr/i586-suse-linux/bin/ld) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... cat: /etc/ld.so.conf.d/*.conf: No such file or directory GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking for shl_load... no checking for shl_load in -ldld... no checking for dlopen... no checking for dlopen in -ldl... yes checking whether a program can dlopen itself... yes checking whether a statically linked program can dlopen itself... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes configure: creating libtool appending configuration tag CXX to libtool checking for ld used by g++... /usr/i586-suse-linux/bin/ld checking if the linker (/usr/i586-suse-linux/bin/ld) is GNU ld... yes checking whether the g++ linker (/usr/i586-suse-linux/bin/ld) supports shared libraries... yes checking for g++ option to produce PIC... -fPIC checking if g++ PIC flag -fPIC works... yes checking if g++ supports -c -o file.o... yes checking whether the g++ linker (/usr/i586-suse-linux/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... cat: /etc/ld.so.conf.d/*.conf: No such file or directory GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking for shl_load... (cached) no checking for shl_load in -ldld... (cached) no checking for dlopen... (cached) no checking for dlopen in -ldl... (cached) yes checking whether a program can dlopen itself... (cached) yes checking whether a statically linked program can dlopen itself...
