[Zoo-discuss] Problems on Mac OS X

[Fenoy Gerald]

Hi Thomas,
in my opinion, you did well trying to recompile the ZOO-Kernel source locally rather than using a old installer.

Before asking  details of your environment, I would like to ask you what is the version you tried to build locally ?

I've tried to build source from trunk on MacOS X and configure worked correctly. Note that I had to remove the "-arch i386" option from the generated Makefile to make it build successfully.
I got similar "no" result messages as you got so you should not worry about it.

I noticed some differences in messages outputted by configure script, so maybe we are not using the same version,  including this one:

"Using user-specified gdal-config file: /Library/Frameworks/GDAL.framework/Versions/Current/Programs/gdal-config"

Also, I didn't face any issue with the --with-java=macos flag, resulting in a zoo_loader.cgi linked against the following JVM:

/System/Library/Frameworks/JavaVM.framework/Versions/A/JavaVM

I would like you to run the following commands by replacing "/location/" by the path of the each files:

oTool -L /location/zoo_loader.cgi
oTool -L /location/translate_service.zo

To check respectively if your ZOO-Kernel and your ServiceProvider are correctly linked with relevant libraries.

Please send us the result if you're not sure of the result. Note that providing the location of each files can help also.

To come back on the request itself, the Gdal_Tranlaste Identifier should respect the upper/lower cases, so you should first start by trying with "Gdal_Translate" rather than "gdal_translate". Indeed the name of the function as its parameters (inputs or outputs) are case sensitives.

Hope this helps,
Best regards,


Gérald Fenoy
ZOO-PSC Chair

Le 1 juil. 2013 à 11:13, Thomas Tilak <thomas.tilak at gmail.com> a écrit :

> Hi everybody,
> 
> I got trouble using zoo_project on Mac OS X. I used the installer and the getCapabilities is working very well.
> I compiled the gdal translate service and tried to use with the following parameters : 
> http://localhost:8888/cgi-bin/zoo_loader.cgi?service=wps&version=1.0.0&request=execute&identifier=gdal_translate&dataInputs=Format=tiff;InputDSN=/********.TIF;OutputDataSourceName=/Users/***/Desktop/test.tif
> 
> The error is 
> <?xml version="1.0" encoding="utf-8"?>
> <ows:ExceptionReport xmlns:ows="http://www.opengis.net/ows/1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xlink="http://www.w3.org/1999/xlink" xsi:schemaLocation="http://www.opengis.net/ows/1.1 http://schemas.opengis.net/ows/1.1.0/owsExceptionReport.xsd" xml:lang="en-US" version="1.1.0">
>   <ows:Exception exceptionCode="NoApplicableCode">
>     <ows:ExceptionText>C Library can't be loaded  
> </ows:ExceptionText>
>   </ows:Exception>
> </ows:ExceptionReport>
> 
> So I tried to recompile the zoo_loader.cgi and doing so, I got the following for the configure command : 
> ./configure --with-python --with-gdal-config=/Library/Frameworks/GDAL.framework/Versions/Current/Programs/gdal-config 
> 
> checking for bison... bison -y
> checking for gcc... gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables... 
> checking whether we are cross compiling... no
> 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 ISO C89... none needed
> checking for flex... flex
> checking lex output file root... lex.yy
> checking lex library... -ll
> checking whether yytext is a pointer... yes
> checking for g++... g++
> checking whether we are using the GNU C++ compiler... yes
> checking whether g++ accepts -g... yes
> checking for a sed that does not truncate output... /usr/bin/sed
> checking for cgiMain in -lcgic... no
> checking for curl_easy_init curl_easy_setopt curl_easy_cleanup curl_easy_perform in -lcurl... no
> checking for dlopen dlsym dlerror dlclose in -ldl... no
> checking for main in -lfl... no
> checking for main in -lpthread... yes
> checking for main in -lfcgi... yes
> checking for main in -lssl... yes
> checking how to run the C preprocessor... gcc -E
> checking for grep that handles long lines and -e... /usr/bin/grep
> checking for egrep... /usr/bin/grep -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 for size_t... yes
> checking for working alloca.h... yes
> checking for alloca... yes
> checking fcntl.h usability... yes
> checking fcntl.h presence... yes
> checking for fcntl.h... yes
> checking for inttypes.h... (cached) yes
> checking libintl.h usability... yes
> checking libintl.h presence... yes
> checking for libintl.h... yes
> checking malloc.h usability... no
> checking malloc.h presence... no
> checking for malloc.h... no
> checking stddef.h usability... yes
> checking stddef.h presence... yes
> checking for stddef.h... yes
> checking for stdlib.h... (cached) yes
> checking for string.h... (cached) yes
> checking for unistd.h... (cached) yes
> checking for stdbool.h that conforms to C99... yes
> checking for _Bool... yes
> checking for int16_t... yes
> checking for int32_t... yes
> checking for int8_t... yes
> checking for pid_t... yes
> checking for size_t... (cached) yes
> checking for uint16_t... yes
> checking for uint32_t... yes
> checking for uint8_t... yes
> checking vfork.h usability... no
> checking vfork.h presence... no
> checking for vfork.h... no
> checking for fork... yes
> checking for vfork... yes
> checking for working fork... yes
> checking for working vfork... (cached) yes
> checking for stdlib.h... (cached) yes
> checking for GNU libc compatible malloc... yes
> checking for stdlib.h... (cached) yes
> checking for GNU libc compatible realloc... yes
> checking for dup2... yes
> checking for getcwd... yes
> checking for memset... yes
> checking for setenv... yes
> checking for strdup... yes
> checking for strstr... yes
> checking for gdal-config... /usr/local/bin/gdal-config
> checking for xml2-config... /usr/bin/xml2-config
> checking libxml/tree.h usability... yes
> checking libxml/tree.h presence... yes
> checking for libxml/tree.h... yes
> checking libxml/parser.h usability... yes
> checking libxml/parser.h presence... yes
> checking for libxml/parser.h... yes
> checking libxml/xpath.h usability... yes
> checking libxml/xpath.h presence... yes
> checking for libxml/xpath.h... yes
> checking libxml/xpathInternals.h usability... yes
> checking libxml/xpathInternals.h presence... yes
> checking for libxml/xpathInternals.h... yes
> checking for xmlInitParser in -lxml2... yes
> configure: creating ./config.status
> config.status: creating Makefile
> config.status: creating ZOOMakefile.opts
> 
> By the way, using the with-java=macos, I got "configure: error: could not find headers include related to libjava" so I removed the parameter for I do not intend to use java.
> 
> Anyway, I am worried about the "checking for cgiMain in -lcgic... no
> checking for curl_easy_init curl_easy_setopt curl_easy_cleanup curl_easy_perform in -lcurl... no
> checking for dlopen dlsym dlerror dlclose in -ldl... no". Is that normal, could it be the cause of my problem? How could I fix it? I checked for libcurl and dl files and I found them.
> 
> Hope you could help me.
> 
> Regards.
> 
> 
> 
> _______________________________________________
> Zoo-discuss mailing list
> Zoo-discuss at lists.osgeo.org
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/zoo-discuss