[OpenAFS-devel] Re: how to use cacheout

[Jeffrey Hutzelman]

--On Wednesday, September 01, 2010 08:49:03 AM -0400 Derrick Brashear 
<shadow@gmail.com> wrote:

> On Wed, Sep 1, 2010 at 12:07 AM, Andrew Deason <adeason@sinenomine.net>
> wrote:
>> On Tue, 31 Aug 2010 22:09:17 -0400
>> Jason Edgecombe <jason@rampaginggeek.com> wrote:
>>
>>> > Try /afs/cs.cmu.edu/misc/afstools/src/afstools-head/util/flushcps.c
>>>
>>> It doesn't build on RHEL5.4 x86_64 with OpenAFS 1.4.11:
>>>
>>> % gcc flushcps.c
>>> /tmp/ccCasuK9.o: In function `main':
>>> flushcps.c:(.text+0x359): undefined reference to `rx_Init'
>>> flushcps.c:(.text+0x35e): undefined reference to
>>> `rxnull_NewClientSecurityObject'
>>> flushcps.c:(.text+0x386): undefined reference to `rx_NewConnection'
>>> flushcps.c:(.text+0x3b7): undefined reference to `RXAFS_FlushCPS'
>>> collect2: ld returned 1 exit status
>>>
>>> Any insights?
>>
>> There's a makefile in that directory, too. From it, it looks like you
>> need to link with libafsint, libcom_err, librx, liblwp, libsys, and
>> libutil.
>
> libafsutil, probably (I bet the makefile deals with how CMU SCS installs
> things)

Yes, afs/libafsutil.a and afs/util.a are the same thing.
That's not "how CMU SCS installs things"; it's how AFS has always installed 
things and still does.  This libafsutil.a thing is fairly new, in the grand 
scheme of things.

-- Jeff