On 17-jun-2005, at 20:25, Michèle Garoche wrote:
Le 17 juin 2005 à 15:13, Erick van Rijk a écrit :
Hi,
I'm having a bit of trouble getting a app to compile using
autoconf and ./configure.
I've set my paths according to the FAQ by setting the enviroment
variables like so:
##
# DELUXE-USR-LOCAL-BIN-INSERT
# (do not remove this comment)
##
echo $PATH | grep -q -s "/usr/local/bin"
if [ $? -eq 1 ] ; then
PATH=$PATH:/usr/local/bin:/usr/local/sbin:usr/local/lib:.
export PATH
fi
test -r /sw/bin/init.sh && . /sw/bin/init.sh
export CFLAGS=-I/sw/include
export LDFLAGS=-L/sw/lib
export CXXFLAGS=$CFLAGS
export CPPFLAGS=$CXXFLAGS
export ACLOCAL_FLAGS="-I /sw/share/aclocal"
export PKG_CONFIG_PATH="/sw/lib/pkgconfig"
for some reason autoconf ignores /sw/include/db4 path because I
get a false on the following autoconf statement:
AC_CHECK_HEADERS(db_cxx.h)
also when I check for pcre++ I will always get a no returned.
AC_CHECK_LIB( pcre++, pcre_fullinfo, [pcre=yes], [pcre=no] )
So my question is how do I tell autoconf that there are include
and libs in /sw/include and /sw/lib?
You need to install pcre-bin, the pcre-config script is within it.
Even with pcre-bin installed it will still return a no on the libs.
Any other ideas what might cause that?
I did a nm /sw/lib/libspcre++.dylib and pcre_fullinfo is specified as
_pcre_fullinfo. I don't think the _ matters (for libcurll it works
fine with _).
Then, if you're on 10.4, there is an autoconf in /usr/bin, which
may act differently as the one in fink, so it's better to install
autoconf2.5 via fink.
Did install autoconf2.5 via fink, didn't seem to matter. (even moved
the /usr/bin version to make sure it takes the /sw one)
For db4, I don't know but it's likely that you need to install
pkgconfig to detect it (check the info file - the dev splittoff if
any).
Could you be more specific with pkg-config? according the man its a
lib sorting tool?
Then if you try to compile it outside of fink, be aware that a
number of tools have been added (for example gettext, which is
different), so that you should sometimes prepend the path /sw/bin
explicitely before launching a tool, otherwise the preference is
given to /usr/bin.
Thanks
Erick
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click
_______________________________________________
Fink-beginners mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-beginners
