Re: Configuration files structure for openafs port(s)

On Sat, Dec 13, 2008 at 2:44 PM, Boris Samorodov <[email protected]> wrote:
> "Ben Kaduk" <[email protected]> writes:
>> On Sat, Dec 13, 2008 at 12:37 PM, Boris Samorodov <[email protected]> wrote:
>>> Hello List,
>>>
>>>
>>> here is a proposed coniguration files structure for openafs port(s):
>>> -----
>>> PREFIX=/usr/local
>>> ETCBASE=${PREFIX}/etc
>>> AFSCONFDIR=${ETCBASE}/openafs
>>> AFSCLIENTCONFDIR=${AFSCONFDIR}/client  #should this be named VICEETC?
>>> AFSSERVERCONFDIR=${AFSCONFDIR}/server  #is there a historical variable?
>>> -----
>>
>> That seems reasonable to me.
>
> OK.
>
>> I pulled your port from ftp://ftp.ipt.ru/pub/tmp/openafs.shar
>> and I removed "--disable-kernel-module" from the Makefile
>> on a recent -current system.
>
> I get an error on -current system when building client:
> -----
> ...
> touch MODLOAD/sec_net.h
> cd MODLOAD ;  echo make DESTDIR= single_compdir_libafs;  make DESTDIR=  single_compdir_libafs
> make DESTDIR= single_compdir_libafs
> ...
> cc -I. -I.. -I../nfs  -I/work/a/ports/net/openafs/work/openafs-1.4.8/src  -I/work/a/ports/net/openafs/work/openafs-1.4.8/src/afs  -I/work/a/ports/net/openafs/work/openafs-1.4.8/src/afs/FBSD  -I/work/a/ports/net/openafs/work/openafs-1.4.8/src/config  -I/work/a/ports/net/openafs/work/openafs-1.4.8/src/rx/FBSD  -I/work/a/ports/net/openafs/work/openafs-1.4.8/src/rxkad  -I/work/a/ports/net/openafs/work/openafs-1.4.8/src/rxkad/domestic  -I/work/a/ports/net/openafs/work/openafs-1.4.8/src/util  -I/work/a/ports/net/openafs/work/openafs-1.4.8/src  -I/work/a/ports/net/openafs/work/openafs-1.4.8/src/afs  -I/work/a/ports/net/openafs/work/openafs-1.4.8/src/afs/FBSD  -I/work/a/ports/net/openafs/work/openafs-1.4.8/src/util  -I/work/a/ports/net/openafs/work/openafs-1.4.8/src/rxkad  -I/work/a/ports/net/openafs/work/openafs-1.4.8/src/config  -I/work/a/ports/net/openafs/work/openafs-1.4.8/src/fsint  -I/work/a/ports/net/openafs/work/openafs-1.4.8/src/vlserver  -I/work/a/ports/net/openafs/work/openafs-1.4.8/include  -I/work/a/ports/net/openafs/work/openafs-1.4.8/include/afs  -O -I. -I.. -I/work/a/ports/net/openafs/work/openafs-1.4.8/src/config  -DAFSDEBUG -DKERNEL -DAFS -DVICE -DNFS -DUFS -DINET -DQUOTA -DGETMOUNT -Wall -nostdinc -I/usr/include -D_KERNEL -DKLD_MODULE  -elf  -mno-align-long-strings -fformat-extensions -fno-common -ffreestanding  -I/a/ports/net/openafs/files -include opt_global.h -fno-strict-aliasing  -O2  -o afs_vcache.o -c /work/a/ports/net/openafs/work/openafs-1.4.8/src/afs/afs_vcache.c
> /work/a/ports/net/openafs/work/openafs-1.4.8/src/afs/afs_vcache.c: In function 'afs_FlushReclaimedVcaches':
> /work/a/ports/net/openafs/work/openafs-1.4.8/src/afs/afs_vcache.c:602: warning: format '%x' expects type 'unsigned int', but argument 2 has type 'struct vcache *'
> /work/a/ports/net/openafs/work/openafs-1.4.8/src/afs/afs_vcache.c: In function 'afs_GetVCache':
> /work/a/ports/net/openafs/work/openafs-1.4.8/src/afs/afs_vcache.c:1840: warning: passing argument 3 of 'vinvalbuf' makes integer from pointer without a cast
> /work/a/ports/net/openafs/work/openafs-1.4.8/src/afs/afs_vcache.c:1840: error: too many arguments to function 'vinvalbuf'
> /work/a/ports/net/openafs/work/openafs-1.4.8/src/afs/afs_vcache.c: In function 'afs_NFSFindVCache':
> /work/a/ports/net/openafs/work/openafs-1.4.8/src/afs/afs_vcache.c:2820: warning: unused variable 'lock'
> *** Error code 1
>
> Stop in /work/a/ports/net/openafs/work/openafs-1.4.8/src/libafs/MODLOAD.
> *** Error code 1
> -----
>

Yes, I see that the prototype of vinvalbuf has changed in current,
recently --- the "curthread" argument should be removed.

>
>> but I did notice that we will probably need to add a
>> --with-bsd-kernel-build line in the Makefile that defaults to
>> /usr/obj/usr/src/sys/GENERIC but can be overridden for
>> those of use with custom kernel configs.
>
> Yes, I do it for experimental (not published yet) openafs port
> with client support.

Ah, thanks!


>
> Thanks for your feedback.

You're welcome;  thanks for working on the port, I'm really excited about it.


Hm, letting my compile continue, it seems that there will be more
errors to deal with.  I will try to batch future updates.

-Ben Kaduk
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-afs
To unsubscribe, send any mail to "[email protected]"