From: Peter Klotz <peter.klotz@aon.at>
To: reiserfs-list@namesys.com, "Vanuxem Grégory" <g.vanuxem@wanadoo.fr>
Subject: Re: reiser4progs 1.0.5 configure script and libaal 1.0.5
Date: Sun, 14 Aug 2005 09:20:46 +0200 [thread overview]
Message-ID: <42FEF0CE.5090001@aon.at> (raw)
In-Reply-To: <1123948023.17483.6.camel@localhost.localdomain>
Hello
> The lastest reiser4progs (1.0.5) can't find libaal
> in configure script.
>
> More precisely it doesn't find libaal because of version problem
>
>
Maybe it is a permission problem caused by SELinux. I had similar
troubles myself. Disabling SELinux in /etc/selinux/config helped.
Take a look at /var/log/messages if there are any SELinux related
access-denied messages. On my system it seemed that ldconfig was not
able to generate symbolic links for libaal and therefore reiser4progs
were not able to find the required libaal version.
Here are two mailing list entries dealing with ldconfig/SELinux problems:
http://lists.freshrpms.net/pipermail/freshrpms-list/2004-December/011960.html
https://www.redhat.com/archives/fedora-test-list/2004-December/msg00275.html
Best regards, Peter.
next prev parent reply other threads:[~2005-08-14 7:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1123947554.11989.ezmlm@namesys.com>
2005-08-13 15:47 ` reiser4progs 1.0.5 configure script and libaal 1.0.5 Vanuxem Grégory
2005-08-13 16:22 ` Vladimir V. Saveliev
2005-08-13 16:26 ` Vanuxem Grégory
2005-08-15 13:25 ` Vitaly Fertman
2005-08-15 13:56 ` Vanuxem Grégory
2005-08-15 13:48 ` Vitaly Fertman
2005-08-15 14:11 ` Vanuxem Grégory
2005-08-15 14:13 ` Vitaly Fertman
2005-08-14 7:20 ` Peter Klotz [this message]
2005-08-14 15:45 ` Vanuxem Grégory
[not found] ` <1124116832.24528.13.camel@localhost.localdomain>
[not found] ` <1124116956.24528.15.camel@localhost.localdomain>
[not found] ` <200508151921.08622.vitaly@namesys.com>
2005-08-15 20:25 ` Vanuxem Grégory
2005-08-16 20:10 ` Hans Reiser
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=42FEF0CE.5090001@aon.at \
--to=peter.klotz@aon.at \
--cc=g.vanuxem@wanadoo.fr \
--cc=reiserfs-list@namesys.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.