Re: [Fwd: Re: Unresolved symbols on Solaris]

2003-11-26 Thread Lars Hecking
Jeff Trawick writes: see attached file let us know how it turns out... also, maybe some of the west coast folks will have a clue once they wake up I have not found a real solution yet, and it seems that my posting to comp.unix.solaris didn't make it. However, I have a preliminary

Unresolved symbols on Solaris

2003-11-24 Thread Lars Hecking
This appers to be too difficult for the users list ... can anyone here help? Solaris 9 8/03 SPARC gcc 2.95.3 Solaris /usr/ccs/bin compiler tools apache 1.3.29/mod_ssl-2.8.16-1.3.29/openssl-0.9.7c/mm-1.3.0 I am using the same build procedure and sources as on Solaris 8 machines. All works

Re: Unresolved symbols on Solaris

2003-11-24 Thread Jeff Trawick
Lars Hecking wrote: # ./apachectl configtest Syntax error on line 205 of /usr/local/apache/conf/httpd.conf: Cannot load /usr/local/apache/libexec/mod_mime_magic.so into server: ld.so.1: /usr/local/apache/bin/httpd: fatal: relocation error: file /usr/local/apache/libexec/mod_mime_magic.so:

Re: Unresolved symbols on Solaris

2003-11-24 Thread Lars Hecking
mm library is compiled statically only, and I have verified during make that the correct cpp/ld paths are used. Can you do a test build with pure, unpatched Apache 1.3.latest and see if you hit the same error? Plain, unpatched 1.3.29 without mod_ssl and mm gives the same error. #

Re: Unresolved symbols on Solaris

2003-11-24 Thread Jeff Trawick
Lars Hecking wrote: Plain, unpatched 1.3.29 without mod_ssl and mm gives the same error. # ./apachectl configtest Syntax error on line 205 of /WWWserv/conf/httpd.conf: Cannot load /WWWserv/libexec/mod_mime_magic.so into server: ld.so.1: /WWWserv/bin/httpd: fatal: relocation error: file

Re: Unresolved symbols on Solaris

2003-11-24 Thread Lars Hecking
latest == 29 is a sufficient approximation :) (I don't recall any build changes whatsoever recently) I can try it on a Solaris 9 box. What configure invocation are you using and which compiler? gcc 2.95.3, no GNU binutils. apache is configured with OPTIM=-O2 \ ./configure \

Re: Unresolved symbols on Solaris

2003-11-24 Thread Jeff Trawick
Lars Hecking wrote : gcc 2.95.3, no GNU binutils. apache is configured with OPTIM=-O2 \ ./configure \ I tweaked only the prefix option and it appears to work fine for me. I too have gcc 2.95.3 (from Sun freeware CD I'd guess) and AFAIK I'm not using GNU binutils either. What does this show

Re: Unresolved symbols on Solaris

2003-11-24 Thread Lars Hecking
I tweaked only the prefix option and it appears to work fine for me. I too have gcc 2.95.3 (from Sun freeware CD I'd guess) and AFAIK I'm not using GNU binutils either. What does this show for your build? $ nm /usr/local/apache/bin/httpd | grep alloc [403] | 0| 0|FILE

Re: Unresolved symbols on Solaris

2003-11-24 Thread Jeff Trawick
Lars Hecking wrote: $ nm /usr/local/apache/bin/httpd | grep alloc [403] | 0| 0|FILE |LOCL |0|ABS|alloc.c [406] |518516| 4|OBJT |LOCL |0|13 |alloc_mutex [1675] |156472| 8|FUNC |GLOB |0|10 |ap_cleanup_alloc [1332] |156420|

Re: Unresolved symbols on Solaris

2003-11-24 Thread Lars Hecking
Your libc references have that SYSVABI_1.3 tag, which mine done. My Solaris 9 is a bit older. I have no idea what the problem is. Hhm. I'll take this to the sunmanagers list then ... $ cat /etc/release Solaris 9 12/02 s9s_u2wos_10a SPARC Copyright

Re: Unresolved symbols on Solaris

2003-11-24 Thread Lars Hecking
Hhm. I'll take this to the sunmanagers list then ... Jeff, one more thing: Could you email me, off-list, the output of truss /usr/local/apache/bin/httpd -t? You can use -o to capture the output into a file.

Re: Unresolved symbols on Solaris

2003-11-24 Thread Jeff Trawick
Lars Hecking wrote: Jeff, one more thing: Could you email me, off-list, the output of truss /usr/local/apache/bin/httpd -t? You can use -o to capture the output into a file. done

Re: Unresolved symbols on Solaris

2003-11-24 Thread Dale Ghent
On Nov 24, 2003, at 9:04 AM, Jeff Trawick wrote: Your libc references have that SYSVABI_1.3 tag, which mine done. My Solaris 9 is a bit older. I have no idea what the problem is. I've run into this exact issue before, as well. Only, on Solaris 8 servers, and the offending modules being