problems building 1.7.1 and 1.7.2
Craig Askings
haakon@themadship.dhs.org
Mon, 04 Nov 2002 08:38:24 +1000
Hi Derek,
That find command did the trick. It turns out the borked .la file was
part of my install of gwrap 1.3.2.
Now I just have to work out how to make it generate the correct .la
files as the make of gnucash fails without them.
Making all in core-utils
make[3]: Entering directory `/usr/src/gnucash-1.7.2/src/core-utils'
FLAVOR=gnome guile -c \
"(set! %load-path (cons \"/usr/share/guile\" %load-path)) \
(primitive-load \"./gw-core-utils-spec.scm\") \
(gw:generate-wrapset \"gw-core-utils\")"
**** NOTE: this wrapset appears to be empty !?
ERROR: Unbound variable: gw:new-wrapset
make[3]: *** [gw-core-utils.c] Error 2
Regards,
Craig Askings.
Derek Atkins wrote:
>Craig Askings <haakon@themadship.dhs.org> writes:
>
>
>
>>Hi,
>>
>>
>
>Hi again...
>
>
>
>>I'm unable to build 1.7.1 or 1.7.2. ./configure runs ok but when I run
>>make I get
>>
>>make[3]: Entering directory `/usr/src/gnucash-1.7.1/src/core-utils'
>>/bin/sh ../../libtool --mode=link gcc -I/usr/local/include/g-wrap
>>-I/usr/include/glib-1.2 -I/usr/lib/glib/include -g -O2 -Wall
>>-Wno-unused -Wno-uninitialized -Wmissing-prototypes
>>-Wmissing-declarations -Werror-implicit-function-declaration -Wall
>>-Wunused -o libgw-core-utils.la -rpath /usr/local/lib -module
>>-L/usr/local/lib -lgwrap-wct -lgwrap-glib -L/usr/lib -lguile
>>-lqthreads -lpthread -lm gw-core-utils.lo libcore-utils.la -lpopt -lm
>>-lm
>>grep: /tmp/buildd/libtool-1.4.2/debian/tmp/usr/lib/libltdl.la: No such
>>file or directory
>>sed: can't read
>>/tmp/buildd/libtool-1.4.2/debian/tmp/usr/lib/libltdl.la: No such file
>>or directory
>>libtool: link:
>>`/tmp/buildd/libtool-1.4.2/debian/tmp/usr/lib/libltdl.la' is not a
>>valid libtool archive
>>make[3]: *** [libgw-core-utils.la] Error 1
>>
>>
>
>As I said on IRC, the problem is that _some_ .la on your system is
>corrupt. You might want to do something like:
>
>find / -name \*.la -print | xargs grep /tmp/buildd/libtool-1.4.2/debian/tmp/usr/lib/libltdl.la
>
>This will tell you which package is broken so you can report it to
>Debian. This is probably related to the "libtool relinking problem"
>(I don't have the Debian bugID handy) -- some people figured the right
>way to fix libtool was to get it not to relink, and well that isn't
>really the right answer. Similarly, some people think the right way
>to "install" is to use --prefix=, instead of using DESTDIR, and that
>screws up libtool, too.
>
>
>
>>I'm running Debian Testing with bits of unstable and g-wrap 1.3.2
>>manually installed.
>>Am I missing a program or something?
>>
>>
>
>No, you've got a program that was built (well, installed) poorly.
>That 'find' command will tell you which package(s) is(are) broken.
>Once you find that, you can rename the XXX.la out of the way (I would
>recommend XXX.la.b0rked).
>
>Good Luck,
>
>
>
>>Regrads,
>>Craig Askings
>>
>>
>
>-derek
>
>
>