On Sun, 15 Jul 2001, Federico Sevilla III wrote:
> On Sun, 15 Jul 2001 at 10:58, Seth Mos wrote:
> > Even some SGI people run debian I guess :-)
>
> <smile> I'm glad to know of that. :)
>
> > can you locate libacl.a? Maybe the lib ended up in the wrong place.
>
> There are three instances of libacl.a in my system. One is in /usr/lib/
> which belongs to the acl-dev package. The other is in
> /usr/src/linux-2.4-xfs-20010715/cmd/acl/debian/acl-dev/usr/lib and the
> other is in /usr/src/linux-2.4-xfs/20010715/cmd/acl/libacl/.
>
> The libacl.a in /usr/lib is the same as the one in .../acl-dev/usr/lib but
> different from the one in .../libacl. I do not know why but this is what
> diff reported. Of course it didn't tell me what was different about them
> because they're binary files.
I thought they would/should have been the same.
> > You installed all the packages referenced above?
>
> I built all the abovementioned packages using my copy of the CVS tree
> which is exactly what I used to build the kernel I'm running on now. I
> also installed all the packages I mentioned by using 'dpkg --install'. :)
That should work.
> > If not you can decide to fix the packages or put the dir to the lib in
> > your /etc/ld.so.conf and run ldconfig.
>
> /etc/ld.so.conf already contains /usr/lib where libacl.a is.
And you ran ldconfig?
Are you sure the headers also got installed?
What does configure.log say about it.
I compiled a samba 2.2.1 on my testbox at work and I followed the exact
same steps and it compiled flawless after installing acl and acl-devel.
Cheers
Seth
|