On Tue, Oct 20, 2009 at 11:43 PM, Felix Zielcke <fzielcke@xxxxxxx> wrote: > Am Dienstag, den 20.10.2009, 23:40 +0530 schrieb Viji V Nair: >> Hello >> >> I have followed the the documentation you have provided, got the same >> result, version issue, here is the exact procedure I have followed. >> >> 1. Downloaded the latest stable kernel from kernel.org and applied the >> reiser4 patch. >> 2. Used the existing fedora config file as .config and added >> "CONFIG_REISER4_FS=y" in the filesystem section of the .config file >> 3. Complied and installed the new kernel without any error. >> 4. Rebooted the system from the newly installed kernel >> # uname -a >> Linux test01 2.6.31.4 #2 SMP Tue Oct 20 02:35:04 IST 2009 x86_64 >> x86_64 x86_64 GNU/Linux >> # cat /etc/fedora-release >> Fedora release 11 (Leonidas) >> >> 5. Downloaded the libaal from the following link >> >> http://www.kernel.org/pub/linux/utils/fs/reiser4/libaal/libaal-1.0.5.tar.bz2 >> >> installed to /usr/local and added the lib path to ld.so.conf, the did >> an ldconfig >> >> 6. Downloaded reiser4progs from the following link >> >> http://www.kernel.org/pub/linux/utils/fs/reiser4/reiser4progs/reiser4progs-1.0.7.tar.bz2 >> >> tried to install, >> >> CFLAGS="-fno-stack-protector -I/usr/local/include" >> LDFLAGS="-L/usr/local/lib" ./configure >> >> got the same result (simple ./configure is also giving the same result) >> >> <snip> >> checking for special C compiler options needed for large files... no >> checking for _FILE_OFFSET_BITS value needed for large files... no >> configure: WARNING: Can't detect right _FILE_OFFSET_BITS. Will be >> forced to 64bit. >> checking for off_t... yes >> checking size of off_t... 8 >> checking for aal_device_open in -laal... yes >> checking aal/libaal.h usability... yes >> checking aal/libaal.h presence... yes >> checking for aal/libaal.h... yes >> checking for libaal version = 1.0.5... no >> </snip> >> >> I am running the latest updated fedora 11, x86_64. There is a fresh >> installation, after that did a yum update. >> >> Did i miss anything? >> > > Maybe config.log tells something useful why the check for libaal failed. > Here is the config.log <snip> configure:23922: checking for aal_device_open in -laal configure:23957: gcc -o conftest -fno-stack-protector -I/usr/local/include -L/usr/local/lib conftest.c -laal >&5 configure:23963: $? = 0 configure:23981: result: yes configure:24011: checking aal/libaal.h usability configure:24028: gcc -c -fno-stack-protector -I/usr/local/include conftest.c >&5 configure:24034: $? = 0 configure:24048: result: yes configure:24052: checking aal/libaal.h presence configure:24067: gcc -E conftest.c configure:24073: $? = 0 configure:24087: result: yes configure:24115: checking for aal/libaal.h configure:24122: result: yes configure:24137: checking for libaal version = 1.0.5 configure:24168: gcc -o conftest -fno-stack-protector -I/usr/local/include -L/usr/local/lib conftest.c -laal >&5 configure:24174: $? = 0 configure:24261: gcc -o conftest -fno-stack-protector -I/usr/local/include -static -L/usr/local/lib conftest.c -laal >&5 /usr/bin/ld: cannot find -lc collect2: ld returned 1 exit status configure:24264: $? = 1 configure: program exited with status 1 configure: failed program was: | /* confdefs.h. */ | #define PACKAGE_NAME "" | #define PACKAGE_TARNAME "" | #define PACKAGE_VERSION "" </snip> > > -- > Felix Zielcke > Proud Debian Maintainer and GNU GRUB developer > > -- To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
