Re: compiling 2.0.5b1 on Solaris 8

[Jochen Reinwand]

Have you looked at config.log? I'm not sure if cfengine creates one, but it 
should give you a lot more information about what is going on.

Setting LD_LIBRARY_PATH and LD_RUN_PATH sometimes makes a lot of problems, 
because autoconf often thinks that it would be a nice idea to ignore them.
The best is to set LD_FLAGS or LIBS (sometimes better on Solaris) before 
running configure. autoconf will normally use them.

Just send me the interesting parts of config.log if you don't know how to deal 
with the problem and I will see what I can do. I'm currently compiling KDE 
3.1 for Solaris and, believe me, it really su...

regards
Jochen

On Monday 10 February 2003 19:53, Darren Nguyen wrote:
> So I tried exporting the LD_LIBRARY_PATH as you suggested but I still get
> the same problem
>
> Here's the output from my configure:
> ---------------------------------------------------------------------------
>-- checking build system type... sparc-sun-solaris2.8
> checking host system type... sparc-sun-solaris2.8
> checking target system type... sparc-sun-solaris2.8
> checking for a BSD compatible install... /usr/local/bin/install -c
> checking whether build environment is sane... yes
> checking for mawk... no
> checking for gawk... no
> checking for nawk... nawk
> checking whether make sets ${MAKE}... yes
> checking for gcc... gcc
> checking for C compiler default output... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... no
> checking for executable suffix...
> checking for object suffix... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for style of include used by make... GNU
> checking dependency style of gcc... gcc3
> checking for flex... flex
> checking for yywrap in -lfl... no
> checking for yywrap in -ll... yes
> checking lex output file root... lex.yy
> checking whether yytext is a pointer... yes
> checking for bison... bison -y
> checking for ranlib... ranlib
> checking for a BSD compatible install... /usr/local/bin/install -c
> checking for latex... false
> checking for texi2dvi... false
> checking for dvips... false
> checking for makeinfo... false
> checking for main in -lm... yes
> checking for door_create... no
> checking for setsockopt... no
> checking for setsockopt in -lsocket... no
> checking for gethostent... no
> checking for gethostent in -lnsl... no
> checking for getaddrinfo... no
> checking for getaddrinfo in -lsocket... no
> checking for library containing socket... no
> checking for socket in -lnsl... no
> checking for BerkeleyDB location... /usr/local/BerkeleyDB.4.0
> checking Berkeley DB Version... 4.0.14 OK
> checking Berkeley DB API... 4.0.14 checking for db_create in -ldb... yes
> checking for OpenSSL location... /usr/local/ssl
> checking OpenSSL Version... configure: error: This release of cfengine
> requires openssl 0.9.6b or later
>
> This is so strange since I have the openssl package. How is it checking for
> the Openssl version? I do have all the files that Thomas described in an
> earlier email. libcrypto.a, libssl.a, etc.
>
>
>
> -----Original Message-----
> From: Wheeler, John [mailto:JWheeler@us.britannica.com]
> Sent: Monday, February 10, 2003 6:58 AM
> To: help-cfengine@gnu.org
> Subject: RE: compiling 2.0.5b1 on Solaris 8
>
>
>
> I just went through my make file ( couldn't remember If I had to do this
> hack) several programs that I've had to compile for solaris require
> /usr/ucblib in the library path. mtr is one I can think of right away. You
> can accomplish this many different ways. First, just to see if this is your
> problem try exporting the LD_LIBRARY_PATH as follows:
>
> LD_LIBRARY_PATH=/usr/lib:/usr/ucblib;export LD_LIBRARY_PATH
>
> run configure.
>
> If configure succeeds, you could move forward with compilation. I think I
> passed configure some additional command line options to populate the
> LDFLAGS var in my make file, or I just edited the make file. Here is my
> final LDFLAGS line:
>
> LDFLAGS = -L/usr/local/BerkeleyDB.4.0/lib -R/usr/local/BerkeleyDB.4.0/lib
> -L/usr /local/openssl/lib -R/usr/local/openssl/lib -R/usr/ucblib
>
> You could also just rely on the environment ( I don't recommend) or use
> crle on all the 2.8 hosts ( don't think crle is on 2.6).
>
> Oh this was on 2.0.3. I haven't had time to upgrade, waiting on namespaces
> ;-)
>
> Hope this helps.
>
> -----Original Message-----
> From: Darren Nguyen [ mailto:dnguyen@talaris.com]
> Sent: Monday, February 10, 2003 12:36 AM
> To: Thomas Glanzmann; help-cfengine@gnu.org
> Subject: RE: compiling 2.0.5b1 on Solaris 8
>
>
> Hi Thomas,
>
> I looked at your posting. Still kind of lost about how to compile cfengine
> still. I have the Openssl and DB package installed already from
> sunfreeware. I run
>
> ./configure --with-berkeleydb=/usr/local/BerkeleyDB
> --with-openssl=/usr/local/ssl
>
> That should be correct. I have compile many different applications with
> berkeley db and ssl and they work. Is it something to do with static and
> dynamic libraries?
>
> Thanks
>
> -----Original Message-----
> From: Thomas Glanzmann [ mailto:sithglan@stud.uni-erlangen.de]
> Sent: Sunday, February 09, 2003 2:06 AM
> To: help-cfengine@gnu.org
> Subject: Re: compiling 2.0.5b1 on Solaris 8
>
> > I'm running
> > SMCossl 0.9.6g,       --> later than 0.9.6.b?????
> > BerkeleyDB 4.0.x.
> > Gcc 3.2.1
> > Solaris patch level: Generic_108528-16
> >
> > Thanks in advance
>
> Have a look at [1].
>
> [1] http://groups.google.com/groups?q=author:Glanzmann+cfengine+Solaris
> <http://groups.google.com/groups?q=author:Glanzmann+cfengine+Solaris&hl=en&;
>lr=&ie=UTF-8&oe=utf-8&safe=off&selm=mailman.431.1040318427.19936.help-cfengi
>ne%40gnu.org&rnum=1>
> &hl=en&lr=&ie=UTF-8&oe=utf-8&safe=off&selm=mailman.431.1040318427.19936.hel
>p-cfengine%40gnu.org&rnum=1
>
> Greetings,
>         Thomas