From: Alan Woodland (alan.woodland_at_gmail_dot_com)
Date: Mon Nov 02 2009 - 03:49:19 PST
2009/11/2 Stefan Kluth <[email protected]>: > > Hi Alan, > > I tried unsuccessfully the following: > > 1) > > get blcr-source (0.8.2-4) from http://packages.debian.org/sid/blcr-source > and try in the official debian/ubuntu way with module-assistant: configure > steps works, but build fails, logs attached Looks like the m-a on ubuntu is either behaving differently than the Debian one, or I introduced a regression in -4. Either way that's Debian package specific, I'm looking into it. > > 2) > > get https://ftg.lbl.gov/CheckpointRestart/downloads/blcr-0.8.2.tar.gz, > unpack, build a la > https://upc-bugs.lbl.gov//blcr/doc/html/BLCR_Admin_Guide.html with the known > result that the configure step fails > > 3) > > as in 2), but replace configure with configure from 1), i.e. from the debian > package. The configure step works, but the build fails with an interesting > process spawning loop in > > ... > Making all in libcr > make[2]: Entering directory `/home/skluth/blcr/blcr-0.8.2/builddir/libcr' > if /bin/bash ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../libcr > -I.. -D_GNU_SOURCE -D_REENTRANT -I../include -I../../include > -I../../libcr/arch/i386/ -Wall -Wno-unused-function -g -O2 -MT > libcr_la-cr_async.lo -MD -MP -MF ".deps/libcr_la-cr_async.Tpo" -c -o > libcr_la-cr_async.lo `test -f 'cr_async.c' || echo > '../../libcr/'`cr_async.c; \ > then mv -f ".deps/libcr_la-cr_async.Tpo" > ".deps/libcr_la-cr_async.Plo"; else rm -f ".deps/libcr_la-cr_async.Tpo"; > exit 1; fi > ^Cmake[2]: *** [libcr_la-cr_async.lo] Interrupt > ^C^Cmake[1]: *** [all-recursive] Interrupt > make: *** [all] Interrupt > > fortunately I issued the ^C while my system was still responsive That's a bit strange, but probably not too surprising given that there's almost certainly a version mis-match between the output of various autotools involved -- the Debian package uses a run of autoreconf -f -i, which updates quite a lot more than just configure > > 4) as 3), but with > > $ ../configure --with-installed-libcr --with-installed-util > > because the problem in 3) was for libcr AFAICT, but this fails in a similar > way to 1) (make seems to go fine, but modules are not found) > > BTW, the libcr and blcr-util 0.8.2-4 packages from debian installed fine on > karmic. You might have more luck with the -3 package for now, -4 introduced a few changes designed to streamline providing binaries for all the pre-build kernels shipped in Debian, which could have broken m-a. I'm looking into it :) DKMS support is also on my TODO list before squeeze ships. Alan