On 9 March 2010 13:26, Yves Caniou <yves.can...@ens-lyon.fr> wrote: > Le Tuesday 09 March 2010 14:12:50 Alan Woodland, vous avez écrit : >> On 9 March 2010 11:29, Yves Caniou <yves.can...@ens-lyon.fr> wrote: >> > Le Tuesday 09 March 2010 12:21:49 Alan Woodland, vous avez écrit : >> >> On 9 March 2010 02:24, Yves Caniou <yves.can...@ens-lyon.fr> wrote: >> >> > Package: blcr-dkms >> >> > Version: 0.8.2-9 >> >> > Severity: normal >> >> > >> >> > Compilation with the line provided in the package (but with full path >> >> > for the manually installed and running kernel) cd >> >> > /var/lib/dkms/blcr/0.8.2/build && env -i >> >> > PATH=.:..:/sbin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/usr/local/bi >> >> >n:/ usr/sbin:/usr/bin:/sbin:/bin:/usr/sbin:/sbin:/usr/lib/dkms >> >> > ./configure --disable-maintainer-mode >> >> > --with-linux=/usr/src/linux-2.6.33 >> >> > --with-installed-libcr --with-installed-util --with-components=modules >> >> > --prefix=/usr && touch /var/lib/dkms/blcr/0.8.2/build/config-stamp >> >> > >> >> > makes the following error: >> >> > configure: error: Directory /usr/src/linux-2.6.33 does not appear to >> >> > contain a Linux kernel build >> >> >> >> Hmm not quite sure what's going on there. Is /usr/src/linux-2.6.33 >> >> literally the directory you built the kernel image in? (i.e. wget >> >> source, extract, configure, build, boot?) >> >> >> >> 2.6.33 isn't supported by BLCR yet, but this hasn't hit the point >> >> where I'd expect to be seeing the unsupported error message. I'll take >> >> a look at reproducing this situation so it works correctly for no >> >> Debian package kernels with DKMS. It may take a while for me to get >> >> around to it though. >> >> >> >> Alan >> > >> > /usr/src/linux-2.6.33 is the directory where I made (make oldconfig && >> > make bzImage && make modules && make modules_install && make install). I >> > also have the symbolic link /usr/src/linux as shown there: >> > /usr/src $>l /usr/src/linux >> > lrwxrwxrwx 1 root root 12 févr. 25 06:15 /usr/src/linux -> linux-2.6.33 >> > Tell me if I can help... >> >> What does config.log say? Normally there will be something more >> explicit about the configuration error in there. > > The first error appears 2 times with: > configure:7917: gcc -E conftest.c > conftest.c:15:28: error: ac_nonexistent.h: No such file or directory > > Then a warning: > configure:8616: gcc -c -g -O2 -fno-rtti -fno-exceptions conftest.c >&5 > cc1: warning: command line option "-fno-rtti" is valid for C++/ObjC++ but not > for C > > Then again the error with the missing file with: > configure:13576: g++ -E conftest.cpp > conftest.cpp:28:28: error: ac_nonexistent.h: No such file or directory > > And finally with: > configure:18642: result: no UTS_RELEASE could be extracted > configure:18656: error: Directory /usr/src/linux-2.6.33 does not appear to > contain a Linux kernel build Is it possible to see the whole config.log from this? There's something weird there, but I can't say what so far.
Alan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org