>Number: 4866
>Category: mod_imap
>Synopsis: Error during complilation and make: modules mod_include.c and
>util_md5.c
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: apache
>State: open
>Class: support
>Submitter-Id: apache
>Arrival-Date: Mon Aug 16 07:50:00 PDT 1999
>Last-Modified:
>Originator: [EMAIL PROTECTED]
>Organization:
apache
>Release: 1.3.2
>Environment:
operating system = Sun Solaris 2.6
compiler = SUNspro/SC4.2
uname -a = SunOS dmczz1002 5.6 Generic_105181-15 sun4u sparc
SUNW,Ultra-Enterprise
>Description:
We are trying to configure apache_1.3.2 with an IBM WebSphere Application
Server, but we are unable to get the two started together. We adding the
following lines to the http.conf file:
LoadModule app_server_module
/opt/WebSphere/AppServer/plugins/sun/mod_app_server.so
AddModule mod_app_server.c
Without success, we are eliminating possible problems and sources of errors.
Since we received 3 warnings during the apache make, we would like to get
confirmation that these warnings are not a part of our problem, and elimiate
them from the make to get a clean compile. The warnings we received are in
the modules mod_include.c and util_md5.c, but here is the make output:
===> src
===> src/os/unix
cc -c -I../../os/unix -I../../include -DSOLARIS2=260 `../../apaci` os.c
cc -c -I../../os/unix -I../../include -DSOLARIS2=260 `../../apaci`
os-inline.c
rm -f libos.a
ar cr libos.a os.o os-inline.o
ranlib libos.a
<=== src/os/unix
===> src/ap
cc -c -I../os/unix -I../include -DSOLARIS2=260 `../apaci` ap_execve.c
cc -c -I../os/unix -I../include -DSOLARIS2=260 `../apaci` ap_cpystrn.c
cc -c -I../os/unix -I../include -DSOLARIS2=260 `../apaci` ap_signal.c
cc -c -I../os/unix -I../include -DSOLARIS2=260 `../apaci` ap_slack.c
cc -c -I../os/unix -I../include -DSOLARIS2=260 `../apaci` ap_snprintf.c
cc -c -I../os/unix -I../include -DSOLARIS2=260 `../apaci` ap_fnmatch.c
rm -f libap.a
ar cr libap.a ap_execve.o ap_cpystrn.o ap_signal.o ap_slack.o ap_snprintf.o
ap_fnmatch.o
ranlib libap.a
<=== src/ap
===> src/main
cc -c -I../os/unix -I../include -DSOLARIS2=260 `../apaci` gen_test_char.c
cc -DSOLARIS2=260 `../apaci` -o gen_test_char gen_test_char.o -lsocket
-lnsl -ldl
./gen_test_char >test_char.h
cc -c -I../os/unix -I../include -DSOLARIS2=260 `../apaci` gen_uri_delims.c
cc -DSOLARIS2=260 `../apaci` -o gen_uri_delims gen_uri_delims.o -lsocket
-lnsl -ldl
./gen_uri_delims >uri_delims.h
cc -c -I../os/unix -I../include -DSOLARIS2=260 `../apaci` alloc.c
cc -c -I../os/unix -I../include -DSOLARIS2=260 `../apaci` buff.c
cc -c -I../os/unix -I../include -DSOLARIS2=260 `../apaci` http_config.c
cc -c -I../os/unix -I../include -DSOLARIS2=260 `../apaci` http_core.c
cc -c -I../os/unix -I../include -DSOLARIS2=260 `../apaci` http_log.c
cc -c -I../os/unix -I../include -DSOLARIS2=260 `../apaci` http_main.c
cc -c -I../os/unix -I../include -DSOLARIS2=260 `../apaci` http_protocol.c
cc -c -I../os/unix -I../include -DSOLARIS2=260 `../apaci` http_request.c
cc -c -I../os/unix -I../include -DSOLARIS2=260 `../apaci` http_vhost.c
cc -c -I../os/unix -I../include -DSOLARIS2=260 `../apaci` util.c
cc -c -I../os/unix -I../include -DSOLARIS2=260 `../apaci` util_date.c
cc -c -I../os/unix -I../include -DSOLARIS2=260 `../apaci` util_script.c
cc -c -I../os/unix -I../include -DSOLARIS2=260 `../apaci` util_uri.c
cc -c -I../os/unix -I../include -DSOLARIS2=260 `../apaci` util_md5.c
"util_md5.c", line 114: warning: argument #1 is incompatible with prototype:
prototype: pointer to const char : "/usr/include/string.h", line 64
argument : pointer to const uchar
cc -c -I../os/unix -I../include -DSOLARIS2=260 `../apaci` md5c.c
cc -c -I../os/unix -I../include -DSOLARIS2=260 `../apaci` rfc1413.c
rm -f libmain.a
ar cr libmain.a alloc.o buff.o http_config.o http_core.o http_log.o
http_main.o http_protocol.o http_request.o http_vhost.o util.o util_date.o
util_script.o util_uri.o util_md5.o md5c.o rfc1413.o
ranlib libmain.a
<=== src/main
===> src/modules
===> src/modules/standard
cc -c -I../../os/unix -I../../include -DSOLARIS2=260 `../../apaci` mod_env.c
cc -c -I../../os/unix -I../../include -DSOLARIS2=260 `../../apaci`
mod_log_config.c
cc -c -I../../os/unix -I../../include -DSOLARIS2=260 `../../apaci` mod_mime.c
cc -c -I../../os/unix -I../../include -DSOLARIS2=260 `../../apaci`
mod_negotiation.c
cc -c -I../../os/unix -I../../include -DSOLARIS2=260 `../../apaci`
mod_status.c
cc -c -I../../os/unix -I../../include -DSOLARIS2=260 `../../apaci`
mod_include.c
"mod_include.c", line 1475: warning: end-of-loop code not reached
"mod_include.c", line 1599: warning: end-of-loop code not reached
cc -c -I../../os/unix -I../../include -DSOLARIS2=260 `../../apaci`
mod_autoindex.c
cc -c -I../../os/unix -I../../include -DSOLARIS2=260 `../../apaci` mod_dir.c
cc -c -I../../os/unix -I../../include -DSOLARIS2=260 `../../apaci` mod_cgi.c
cc -c -I../../os/unix -I../../include -DSOLARIS2=260 `../../apaci` mod_asis.c
cc -c -I../../os/unix -I../../include -DSOLARIS2=260 `../../apaci` mod_imap.c
cc -c -I../../os/unix -I../../include -DSOLARIS2=260 `../../apaci`
mod_actions.c
cc -c -I../../os/unix -I../../include -DSOLARIS2=260 `../../apaci`
mod_userdir.c
cc -c -I../../os/unix -I../../include -DSOLARIS2=260 `../../apaci`
mod_alias.c
cc -c -I../../os/unix -I../../include -DSOLARIS2=260 `../../apaci`
mod_access.c
cc -c -I../../os/unix -I../../include -DSOLARIS2=260 `../../apaci` mod_auth.c
cc -c -I../../os/unix -I../../include -DSOLARIS2=260 `../../apaci` mod_so.c
cc -c -I../../os/unix -I../../include -DSOLARIS2=260 `../../apaci`
mod_setenvif.c
rm -f libstandard.a
ar cr libstandard.a mod_env.o mod_log_config.o mod_mime.o mod_negotiation.o
mod_status.o mod_include.o mod_autoindex.o mod_dir.o mod_cgi.o mod_asis.o
mod_imap.o mod_actions.o mod_userdir.o mod_alias.o mod_access.o mod_auth.o
mod_so.o mod_setenvif.o
ranlib libstandard.a
<=== src/modules/standard
<=== src/modules
cc -c -I./os/unix -I./include -DSOLARIS2=260 `./apaci` modules.c
cc -c -I./os/unix -I./include -DSOLARIS2=260 `./apaci` buildmark.c
cc -DSOLARIS2=260 `./apaci` \
-o httpd buildmark.o modules.o modules/standard/libstandard.a
main/libmain.a ./os/unix/libos.a ap/libap.a -lsocket -lnsl -ldl
===> src/support
cc -c -I../os/unix -I../include -DSOLARIS2=260 `../apaci` htpasswd.c
cc -DSOLARIS2=260 `../apaci` htpasswd.o -o htpasswd -L../os/unix -L../ap
-los -lap -lsocket -lnsl -ldl
cc -c -I../os/unix -I../include -DSOLARIS2=260 `../apaci` htdigest.c
cc -DSOLARIS2=260 `../apaci` htdigest.o -o htdigest -L../os/unix -L../ap
-los -lap -lsocket -lnsl -ldl
cc -c -I../os/unix -I../include -DSOLARIS2=260 `../apaci` rotatelogs.c
cc -DSOLARIS2=260 `../apaci` rotatelogs.o -o rotatelogs -L../os/unix -L../ap
-los -lap -lsocket -lnsl -ldl
cc -c -I../os/unix -I../include -DSOLARIS2=260 `../apaci` logresolve.c
cc -DSOLARIS2=260 `../apaci` logresolve.o -o logresolve -L../os/unix -L../ap
-los -lap -lsocket -lnsl -ldl
cc -c -I../os/unix -I../include -DSOLARIS2=260 `../apaci` ab.c
cc -DSOLARIS2=260 `../apaci` ab.o -o ab -L../os/unix -L../ap -los -lap
-lsocket -lnsl -ldl
sed <apxs.pl >apxs \
-e '[EMAIL PROTECTED]@%cc%g' \
-e '[EMAIL PROTECTED]@% -DSOLARIS2=260 `../apaci`%g' \
-e '[EMAIL PROTECTED]@%-KPIC -DSHARED_MODULE%g' \
-e '[EMAIL PROTECTED]@%ld%g' \
-e '[EMAIL PROTECTED]@%-G%g' \
-e '[EMAIL PROTECTED]@%%g' && chmod a+x apxs
<=== src/support
<=== src
Any help or information you could spare would be greatly appreciated. In
addition, if you know someone who has configured apache_1.3.2 with IBM Web
Sphere and would not mind being asked a few questions, we would like to have
there name. We have been spending days on this problem without IBM support.
Thanks, JP
>How-To-Repeat:
I don't think so.
>Fix:
No.
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, you need]
[to include <[EMAIL PROTECTED]> in the Cc line and make sure the]
[subject line starts with the report component and number, with ]
[or without any 'Re:' prefixes (such as "general/1098:" or ]
["Re: general/1098:"). If the subject doesn't match this ]
[pattern, your message will be misfiled and ignored. The ]
["apbugs" address is not added to the Cc line of messages from ]
[the database automatically because of the potential for mail ]
[loops. If you do not include this Cc, your reply may be ig- ]
[nored unless you are responding to an explicit request from a ]
[developer. Reply only with text; DO NOT SEND ATTACHMENTS! ]
