From: Steven Cole <elenstev@mesatop.com>
To: Tupshin Harper <tupshin@tupshin.com>
Cc: Reiserfs List <reiserfs-list@namesys.com>
Subject: Re: small problem configuring and installing reiser4progs
Date: 26 Aug 2003 22:16:09 -0600 [thread overview]
Message-ID: <1061957769.3567.6.camel@spc> (raw)
In-Reply-To: <3F4C052A.2010200@tupshin.com>
On Tue, 2003-08-26 at 19:11, Tupshin Harper wrote:
> I just downloaded and installed reiser4progs-0.4.12 and libaal-0.4.9.
> This was the first install of either of these, and I ran into the
> following problem:
> configured and make installed libaal-0.4.9
> configure of reiser4progs ends with the following:
> checking whether -falign-loops works... yes
> checking for aal_device_open in -laal... yes
> checking aal/aal.h usability... yes
> checking aal/aal.h presence... yes
> checking for aal/aal.h... yes
> checking for libaal version = 0.4.9... no
>
> It ends there, without any indication that there was a fatal error, but
> it didn't build the Makefiles. So, two problems...insufficient error
> reporting, as well as a slight problem with the process. After running
> ldconfig, configure works just fine.
>
> -Tupshin
>
Yeah, I flailed around with this problem for a couple of minutes too.
I also ran /sbin/ldconfig, but still got the above, so I added the
install directory for libaal (I think it is /usr/local/bin, but I don't
have it here) to /etc/ld.so.conf, and ran ldconfig again, and after that
everything worked. I guess if I really understood this better, it
wouldn't have been even that hard, but general users shouldn't have to
jump through these hoops.
Steven
next prev parent reply other threads:[~2003-08-27 4:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-27 1:11 small problem configuring and installing reiser4progs Tupshin Harper
2003-08-27 4:16 ` Steven Cole [this message]
2003-08-27 5:23 ` Yury Umanets
2003-08-27 5:47 ` Tupshin Harper
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=1061957769.3567.6.camel@spc \
--to=elenstev@mesatop.com \
--cc=reiserfs-list@namesys.com \
--cc=tupshin@tupshin.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.