From: Felix Zielcke <fzielcke@z-51.de>
To: Viji V Nair <viji@fedoraproject.org>
Cc: Edward Shishkin <edward.shishkin@gmail.com>,
reiserfs-devel@vger.kernel.org
Subject: Re: reiser4progs-1.0.7 compilation error.
Date: Tue, 20 Oct 2009 20:13:13 +0200 [thread overview]
Message-ID: <1256062393.3234.0.camel@fz.local> (raw)
In-Reply-To: <84c89ac10910201110o5613a6edv259018698f77e285@mail.gmail.com>
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.
--
Felix Zielcke
Proud Debian Maintainer and GNU GRUB developer
next prev parent reply other threads:[~2009-10-20 18:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-20 8:35 reiser4progs-1.0.7 compilation error Viji V Nair
2009-10-20 11:03 ` Edward Shishkin
2009-10-20 11:42 ` Viji V Nair
2009-10-20 12:32 ` Edward Shishkin
2009-10-20 18:10 ` Viji V Nair
2009-10-20 18:13 ` Felix Zielcke [this message]
2009-10-20 18:55 ` Viji V Nair
2009-10-20 19:01 ` Felix Zielcke
2009-10-20 19:23 ` Edward Shishkin
2009-10-20 19:29 ` Viji V Nair
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1256062393.3234.0.camel@fz.local \
--to=fzielcke@z-51.de \
--cc=edward.shishkin@gmail.com \
--cc=reiserfs-devel@vger.kernel.org \
--cc=viji@fedoraproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).