From: Viji V Nair <viji@fedoraproject.org>
To: Edward Shishkin <edward.shishkin@gmail.com>
Cc: reiserfs-devel@vger.kernel.org
Subject: Re: reiser4progs-1.0.7 compilation error.
Date: Tue, 20 Oct 2009 17:12:57 +0530 [thread overview]
Message-ID: <84c89ac10910200442m404688e4jcd73173cb97fbbb3@mail.gmail.com> (raw)
In-Reply-To: <4ADD9904.4080202@gmail.com>
I have installed libaal already, it is installed on /usr/local. You
can see that the installer is finding libaal.h
checking for aal/libaal.h... yes
I think the installer is messed up with the version. I have downloaded
the libaal from the following location
http://www.kernel.org/pub/linux/utils/fs/reiser4/libaal/
Also, I am not trying grub with reiserfs4, I just want enable
reiserfs4 support in fedora. I have patched the upstream kernel and
installed the new kernel with reiserfs4 support. Now, I want the
utilities to manage the same file system.
On Tue, Oct 20, 2009 at 4:33 PM, Edward Shishkin
<edward.shishkin@gmail.com> wrote:
> Viji V Nair wrote:
>>
>> Hi,
>>
>
> Hello.
>
>> I am trying to compile reiser4progs-1.0.7 on a Fedora 11 64 bit
>> machine and it is throwing the following error.
>>
>> <snip>
>> 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>
>>
>
> make sure you have libaal installed
>
>> I was followed the step in the following URL except the "sed" part.
>> (even with sed it is showing the same error)
>>
>> http://reiser4.wiki.kernel.org/index.php/Reiser4_Howto/GRUB
>>
>
> I am sorry, but it is impossible to build grub with
> reiser4 support with reiser4progs-1.0.7: some
> fixups in configuration files are needed. Also the
> reiser4-grub patch is rather old and I guess we
> need to adjust it to the reiser4 format change that
> occurred 4 years ago, or so.. I still don't have a
> time to look at this.
>
> Thanks,
> Edward.
>
>> The command which I have run is "CFLAGS="-fno-stack-protector
>> -I/usr/local/include" LDFLAGS="-L/usr/local/lib" ./configure"
>>
>> I have installed libaal to /usr/local/ and there is no error while
>> compiling this, add lib path to ldconfig also
>>
>> While googling I have found some old bug releated to this.
>>
>> Any help on the same is greatly appreciated.
>>
>> Viji
>> --
>> To unsubscribe from this list: send the line "unsubscribe reiserfs-devel"
>> in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>>
>
>
--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-10-20 11:42 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 [this message]
2009-10-20 12:32 ` Edward Shishkin
2009-10-20 18:10 ` Viji V Nair
2009-10-20 18:13 ` Felix Zielcke
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=84c89ac10910200442m404688e4jcd73173cb97fbbb3@mail.gmail.com \
--to=viji@fedoraproject.org \
--cc=edward.shishkin@gmail.com \
--cc=reiserfs-devel@vger.kernel.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).