Hello everyone,
I would like to try and update an apache module (mod_tile for serving map tiles [1]) on Ptolemy, which still operates on Solaris. After fixing a bunch of standard portability issues with the source code, I have run into a problem that I am not sure about.
With the standard compile options, the build fails with: Undefined first referenced symbol in file __stack_chk_fail_local ./.libs/dir_utils.o (symbol scope specifies local binding) ld: fatal: Symbol referencing errors. No output written to ./.libs/mod_tile.so
The suggested fix for this issue seems to be to add -fno-stack-protector to the CFLAGS. After figuring out how to pass that to the apache build system it does now seem to compile fine. (if one tries to do that during the ./configure stage, ./configure fails by complaining that the C-compiler can't produce an executable. Possibly because ./configure uses the sun compiler rather than gcc which doesn't support -fno-stack-protector?)
However, the apache build system (apxs) claims that apache on ptolemy was built with stack protection. Does it matter if a module is built without stack protection while apache is? Is there a way to test out if the built module works correctly with the installed apache? Is there a better way to fix this compile issue?
Currently I just compiled it from source in the project home directory. Would it have to be "ported" to ts-spec to install it on ptolemy?
Thanks,
Kai
[1] http://svn.openstreetmap.org/applications/utils/mod_tile/
On 02/09/12 09:04, Kai Krueger wrote:
Hello everyone,
I would like to try and update an apache module (mod_tile for serving map tiles [1]) on Ptolemy, which still operates on Solaris. After fixing a bunch of standard portability issues with the source code, I have run into a problem that I am not sure about.
With the standard compile options, the build fails with: Undefined first referenced symbol in file __stack_chk_fail_local ./.libs/dir_utils.o (symbol scope specifies local binding) ld: fatal: Symbol referencing errors. No output written to ./.libs/mod_tile.so
The suggested fix for this issue seems to be to add -fno-stack-protector to the CFLAGS. After figuring out how to pass that to the apache build system it does now seem to compile fine. (if one tries to do that during the ./configure stage, ./configure fails by complaining that the C-compiler can't produce an executable. Possibly because ./configure uses the sun compiler rather than gcc which doesn't support -fno-stack-protector?)
However, the apache build system (apxs) claims that apache on ptolemy was built with stack protection. Does it matter if a module is built without stack protection while apache is? Is there a way to test out if the built module works correctly with the installed apache? Is there a better way to fix this compile issue?
Currently I just compiled it from source in the project home directory. Would it have to be "ported" to ts-spec to install it on ptolemy?
Thanks,
Kai
[1] http://svn.openstreetmap.org/applications/utils/mod_tile/
I'd clean all the .o files and rebuild. It's possible that you have some files built with gcc and others with cc, giving weird errors.
You should use the same compiler as the one used for apache (it may work with another, but it's better to play safe). If you run CC=<compiler> ./configure, it should pick the one you wanted.
toolserver-l@lists.wikimedia.org