Date: Tue, 18 May 2010 12:10:10 -0400 (EDT) From: Benjamin Kaduk <kaduk@MIT.EDU> To: Jan Henrik Sylvester <me@janh.de> Cc: afs-list freebsd <freebsd-afs@freebsd.org> Subject: Re: AFS on FreeBSD 8? Message-ID: <alpine.GSO.1.10.1005181201010.29136@multics.mit.edu> In-Reply-To: <4BF2B962.50408@janh.de> References: <558186334.2619.1271175586732.JavaMail.root@thunderbeast.private.linuxbox.com> <alpine.GSO.1.10.1004131220540.29136@multics.mit.edu> <4BC4A5F1.6050406@janh.de> <alpine.GSO.1.10.1004131314070.29136@multics.mit.edu> <4BC5EEB5.5050109@janh.de> <alpine.GSO.1.10.1004141242470.29136@multics.mit.edu> <4BE01AF0.3080309@janh.de> <alpine.GSO.1.10.1005041225120.29136@multics.mit.edu> <4BF2B962.50408@janh.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 18 May 2010, Jan Henrik Sylvester wrote:
> On 05/04/10 18:45, Benjamin Kaduk wrote:
>> On Tue, 4 May 2010, Jan Henrik Sylvester wrote:
>>
> I have upgraded almost all of my machines from i386 to amd64 and would like
> to repeat the OpenAFS testing -- even though you suspect it is SMP, which
> applies to all machines available to me.
I expect that you will find AFS more usable if you set kern.smp.disabled=1
in /boot/loader.conf, which will make your machine effectively
single-processor.
>
> The port (that uses the master branch) currently only builds until:
[...]
> -fno-common -ffreestanding -I/usr/obj/usr/src/sys/GENERIC -include
> opt_global.h -fno-strict-aliasing -fPIC -O2 -o afs_atomlist.o -c
> /usr/ports/net/openafs-devel/work/openafs/src/util/afs_atomlist.c
> <command-line>:14600381:116: error: opt_global.h: No such file or directory
> *** Error code 1
> Stop in /usr/ports/net/openafs-devel/work/openafs/src/libafs/MODLOAD.
>
opt_global.h should be coming from your kernel's build tree ...
> Do you have a git tag (or whatever, I do not really know git) that is known
> to compile?
>
I compiled recently with head at commit af6b80f257
> How could I make the port use anything else but master? (Probably "make
> extract ; cd work/openafs/ ; SOME GIT COMMAND ; cd ../../ ; make" or
> something similar.)
I would change the makefile to have the do-patch: target actually do
something, i.e.:
--------------
do-patch:
cd ${WRKDIR} && git checkout af6b80f257
--------------
Note that that must be a tab character, as per all Makefiles.
I don't think any of the changes between af6b80f and the current master
could cause your build failure, though.
-Ben
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.GSO.1.10.1005181201010.29136>