Re: [GNUnet-developers] Problem in "make install" on GNUnet 0.6.2b and GNUnet CVS

[Christian Grothoff]

On Tuesday 13 Jul 2004 8:04 am, Daniel Alexandre wrote:
> Hi there, i'm trying to install gnunet in my computer but it gives me
> an error at the make install stage. With configure and make everything
> goes right, but when i try to make install it gives-me the following
> error:
>
> Making install in esed2
> /bin/sh ../../../../libtool --mode=link gcc  -no-cpp-precomp
> -fno-strict-aliasing -Wall -g -O2  -L/usr/lib  -flat_namespace
> -undefined suppress  -o libgnunet_afs_esed2.la -rpath /usr/local/lib
> block.lo contentencoding.lo deleteutil.lo directory.lo downloadutil.lo
> insertutil.lo keywords.lo policy.lo pseudonym.lo requestmanager.lo
> sblock.lo searchutil.lo priority.lo uri.lo
> ../../../../src/util/libgnunetutil.la -lextractor  -lgettextlib -lm
> -lkvm -lpthread
> gcc -dynamiclib -flat_namespace -undefined suppress -o
> .libs/libgnunet_afs_esed2.0.0.0.dylib  .libs/block.o
> .libs/contentencoding.o .libs/deleteutil.o .libs/directory.o
> .libs/downloadutil.o .libs/insertutil.o .libs/keywords.o .libs/policy.o
> .libs/pseudonym.o .libs/requestmanager.o .libs/sblock.o
> .libs/searchutil.o .libs/priority.o .libs/uri.o  -L/usr/lib
> ../../../../src/util/.libs/libgnunetutil.dylib
> /usr/lib/libltdl.3.1.0.dylib /usr/lib/libdl.dylib
> /usr/lib/libcrypto.dylib /usr/local/lib/libintl.dylib
> /usr/lib/libiconv.dylib /usr/lib/libc.dylib /usr/lib/libm.dylib
> /usr/lib/libkvm.dylib /usr/lib/libpthread.dylib
> /usr/local/lib/libextractor.dylib /usr/local/lib/libgettextlib.dylib
> -lm -lkvm -lpthread -install_name
> /usr/local/lib/libgnunet_afs_esed2.0.dylib -compatibility_version 1
> -current_version 1.0
> ld: multiple definitions of symbol _OPEN
> /usr/bin/libtool: internal link edit command failed
> ../../../../src/util/.libs/libgnunetutil.dylib(io.o) definition of _OPEN
> /usr/local/lib/libextractor.dylib(libextractor.0.0.0.dylib-master.o)
> definition of _OPEN
> make[4]: *** [libgnunet_afs_esed2.la] Error 1
> make[3]: *** [install-recursive] Error 1
> make[2]: *** [install-recursive] Error 1
> make[1]: *** [install-recursive] Error 1
> make: *** [install-recursive] Error 1
>
> What could it be? Also. Seems like configure is adding the flag
> "-Lyes/lib" to every Makefile which causes an error when compiling
> (make) the program saying that the directory yes doesn't exist. I had
> to use the --with-extractor=/usr option and then remove the -Lyes/lib
> from every Makefile and let the -L/usr which was specified with the
> --with-extractor option remain to build the application successfully.

The "-Lyes" is a known problem that should be fixed by some configure-hackery. 
As for the _OPEN, what platform are you using?  The ".dylib" makes the whole 
thing look like OSX to me, which is so far not supported and problems must 
kind of be expected (it's probably something simple, but I can't tell).

I would look at _OPEN in libextractor and _OPEN in GNUnet, both were used to 
help portability to Cygwin/MinGW.  Maybe there are some #defines which break 
things on your platform.  Please report what contrib/report.sh says for your 
system, maybe then we can investigate.

Christian [ leaving for Ladakh for a week, so I'll not be able to help for a 
few days... ]