certi-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [certi-dev] Does CERTI compile at Solaris?


From: Eric Noulard
Subject: Re: [certi-dev] Does CERTI compile at Solaris?
Date: Wed, 18 Jun 2008 15:35:36 +0200

2008/6/18 Martin Spott <address@hidden>:
> "Eric Noulard" wrote:
>
>> This looks like a an autoconf build.
>> Would you try a CMake build?
>
> Hehe, swapping autoconf for cmake means swapping one compiler Error for
> another compiler Error _plus_ the usual CMake trouble  :-)


>
> foehn: 15:13:33 /usr/local/src/certi-3.2.7-Source> cmake -D 
> CMAKE_INSTALL_PREFIX=/opt/CERTI -D LibXml2_DIR=/usr/local/lib -D 
> LIB_POSTFIX="" -D CMAKE_VERBOSE_MAKEFILE=TRUE -D CMAKE_BUILD_TYPE=Release .

With current CMake build system for CERTI you usually only need to
specify CMAKE_INSTALL_PREFIX,
could you tell me why you need to  -D LIB_POSTFIX="" ?

Using CMake I advise you to separate source tree from build tree.

mkdir build
cd build

cmake  -DCMAKE_INSTALL_PREFIX:PATH=/opt/CERTI /path/to/certi-3.2.7-Source

> [...]
> [ 14%] Building CXX object libCERTI/CMakeFiles/CERTI.dir/ObjectClass.o
> /opt/SUNWspro/bin/CC  -xO3 -xtarget=ultra2 -xautopar -xprefetch=auto  
> -DCERTI_EXPORTS   -g -KPIC -I/usr/include/libxml2 
> -I/usr/local/src/certi-3.2.7-Source/include 
> -I/usr/local/src/certi-3.2.7-Source 
> -I/usr/local/src/certi-3.2.7-Source/libCERTI   -DHAVE_CONFIG_H=1 -DHAVE_XML 
> -DRTI_USES_STD_FSTREAM -o libCERTI/CMakeFiles/CERTI.dir/ObjectClass.o -c 
> /usr/local/src/certi-3.2.7-Source/libCERTI/ObjectClass.cc
> "/usr/local/src/certi-3.2.7-Source/libCERTI/ObjectClass.cc", line 869: Error: 
> __FUNCTION__ is not defined.
> "/usr/local/src/certi-3.2.7-Source/libCERTI/ObjectClass.cc", line 1757: 
> Error: __FUNCTION__ is not defined.
> 2 Error(s) detected.
>
>
> I'll check current CVS,

This should be debug message code
you may surround those using something like

#ifndef __SUNPRO_CC
something SUN CC don't like
#endif

I'll try to make the debug code "portable" later on unless you find
a replacement for the __FUNCTION__ predefined macro.

-- 
Erk




reply via email to

[Prev in Thread] Current Thread [Next in Thread]