[oe] config/compile problem with apr-1.2.12

Richard Purdie rpurdie at rpsys.net
Mon Feb 2 17:59:47 UTC 2009


On Mon, 2009-02-02 at 16:35 +0100, Sledz, Steffen wrote:
> I'm not really sure what's the problem here, maybe it has the same background like <http://bugs.gentoo.org/show_bug.cgi?id=226577>. Can someone help?
> 
> ERROR: log data follows (/home/sledz/oe/tmp.1/work/i486-angstrom-linux/apr-1.2.12-r0/temp/log.do_compile.30454)
> | NOTE: make
> | make[1]: Entering directory `/home/sledz/oe/tmp.1/work/i486-angstrom-linux/apr-1.2.12-r0/apr-1.2.12'
> | /bin/bash /home/sledz/oe/tmp.1/work/i486-angstrom-linux/apr-1.2.12-r0/apr-1.2.12/libtool --silent --mode=compile i486-angstrom-linux-gcc -march=i486   -isystem/home/sledz/oe/tmp.1/staging/i486-angstrom-linux/usr/include -fexpensive-optimizations -frename-registers -fomit-frame-pointer -O2 -DHAVE_CONFIG_H -DLINUX=2 -D_REENTRANT -D_GNU_SOURCE  -isystem/home/sledz/oe/tmp.1/staging/i486-angstrom-linux/usr/include -I./include -I/home/sledz/oe/tmp.1/work/i486-angstrom-linux/apr-1.2.12-r0/apr-1.2.12/include/arch/unix -I./include/arch/unix -I/home/sledz/oe/tmp.1/work/i486-angstrom-linux/apr-1.2.12-r0/apr-1.2.12/include  -o passwd/apr_getpass.lo -c passwd/apr_getpass.c && touch passwd/apr_getpass.lo
> | /home/sledz/oe/tmp.1/work/i486-angstrom-linux/apr-1.2.12-r0/apr-1.2.12/libtool: line 460: CDPATH: command not found
> | /home/sledz/oe/tmp.1/work/i486-angstrom-linux/apr-1.2.12-r0/apr-1.2.12/libtool: line 1138: func_opt_split: command not found
> | libtool: Version mismatch error.  This is libtool 2.2.4, but the
> | libtool: definition of this LT_INIT comes from an older release.
> | libtool: You should recreate aclocal.m4 with macros from libtool 2.2.4
> | libtool: and run autoconf again.
> | make[1]: *** [passwd/apr_getpass.lo] Error 63
> | make[1]: Leaving directory `/home/sledz/oe/tmp.1/work/i486-angstrom-linux/apr-1.2.12-r0/apr-1.2.12'
> | make: *** [all-recursive] Error 1
> | FATAL: oe_runmake failed

I'd try the recipes in Poky for apr and apr-utils as they have fixes for
a load of issues like this...

Cheers,

Richard





More information about the Openembedded-devel mailing list