From: <mail@viliar.net.ru>
To: reiserfs-list@namesys.com
Subject: Re: reiser4progs+libaal 1.0.5
Date: Sat, 27 May 2006 01:18:03 +0400 [thread overview]
Message-ID: <web-8690434@inc.ru> (raw)
In-Reply-To: <1148636819.6436.21.camel@tribesman.namesys.com>
I should apologize. Having looked closely config.log I have
found the following:
configure:24301: gcc -o conftest -static conftest.c
-laal >&5
/usr/bin/ld: cannot find -lc
collect2: ld returned 1 exit status
configure:24304: $? = 1
configure: program exited with status 1
Google + installing glibc-static-devel-2.3.5-5mdk.i586.rpm
resolve this problem.
Thanks to all for help!
On Fri, 26 May 2006 13:46:59 +0400
"Vladimir V. Saveliev" <vs@namesys.com> wrote:
> Hello
>
> On Thu, 2006-05-25 at 21:18 +0400, mail@viliar.net.ru
> wrote:
> > Hi all!
> >
> > I have same problem, as at topic
> >
>
http://www.nabble.com/reiser4progs+1.0.5+configure+script+and+libaal+1.0.5-t221999.html
> >
> > The reiser4progs 1.0.5 can't find libaal 1.0.5, which
> > installed in /usr/local
>
> ls /usr/local/lib/libaal*
> ?
>
> > (this path is in /etc/ld.so.conf
> > and ldconfig was made)
> >
> > 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
> >
> > But glibc not 2.3.2, as in that case.
> >
> > # rpm -qa | grep glibc
> > glibc-2.3.5-5mdk
> > glibc-devel-2.3.5-5mdk
> >
> > distro - Mandriva 2006 (kernel 2.6.16.18)
> >
> > How can I trace an error?
> >
> > Any help would be appreciated...
> >
> > Thank you.
> >
> >
> >
> > A.
> >
> > --------------
> >
> > "Hic Jacet Ego"
> >
>
A.
--------------
"Hic Jacet Ego"
next prev parent reply other threads:[~2006-05-26 21:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-25 17:18 reiser4progs+libaal 1.0.5 mail
2006-05-26 9:46 ` Vladimir V. Saveliev
2006-05-26 21:18 ` mail [this message]
2006-05-28 2:33 ` Compression Plugin Hönsch Roland
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=web-8690434@inc.ru \
--to=mail@viliar.net.ru \
--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.