Re: libunistring.m4 macro does not support --with-libunistring

[Christian Grothoff]

Just FYI, amatus (the reporter) now writes: "Nevermind. I got confused." and 
marked the bug as resolved...

So I assume the problem was between keyboard and monitor ;-)

Happy hacking!

Christian


On Saturday, January 07, 2012 02:16:19 AM you wrote:
> Hi Christian,
> 
> > We're using the libunistring.m4 macro from gnulib to test for
> > libunistring.
> > 
> > However, I get user complaining that it doesn't support specifying an
> > install path for the library:
> > 
> > https://gnunet.org/bugs/view.php?id=2060
> > 
> > The reporter writes:
> > 
> > My command line: ./configure --prefix=/home/gnunet
> > --with-extractor=/home/gnunet --with-libmicrohttpd=/home/gnunet
> > --with-libunistring-prefix=/usr/local
> > The error in config.log:
> > configure:22576: checking for libunistring
> > configure:22595: gcc -o conftest -fno-strict-aliasing -Wall -g -O2
> > -I/home/gnunet/include -L/home/gnunet/lib conftest.c -lm -ldl
> > -lunistring >&5
> > conftest.c:83:21: error: uniconv.h: No such file or directory
> > conftest.c: In function 'main':
> > conftest.c:87: warning: implicit declaration of function
> > 'u8_strconv_from_locale'
> > configure:22595: $? = 1
> > 
> > As you can see there is no -I/usr/local/include -L/usr/local/lib like
> > you would expect.
> > <<
> > 
> > The macro is from:
> > http://www.gnu.org/software/gnulib/MODULES.html#module=libunistring
> 
> Can you please ask the original reporter ('amatus') to send
>   1) The complete config.log (there ought to be more references to
>      libunistring in there),
>   2) The configure file,
>   3) The output of
>        ls -l /usr/locale/include/uniconv.h /usr/local/lib*/libunistring*
> 
> Also, the platform is a FreeBSD/x86_64 system. Is it a bi-arch system
> (both x86 and x86_64 libraries installed)? If so, what's the convention
> for separating x86 and x86_64 libraries on this platform? So far, the
> macros support bi-arch only for glibc and Solaris platforms.
> 
> In any case, the user can work around the problem by specifying
> the -I option in the CPPFLAGS variable and the -L option in the LDFLAGS
> variable while configuring. The --with-...-prefix option is a handy
> shortcut.
> 
> Bruno