Re: AFS install
On Wed, 16 May 2012, Jerry McAllister wrote:
On Tue, May 15, 2012 at 12:51:04AM -0400, Benjamin Kaduk wrote:
Hello Ben,
Thank you for your response.
I cleaned and then copied the 82 file to 83 and then edited it
to replace all 82-s with 83 or added it where there seemed to be
a list of versions. It got a lot further, but now dies not finding
another file.
../rpc/types.h:77:27: error: rpc/netconfig.h: No such file or directory
Ah, I see what is going on. This is an artifact of the old build system I
inherited, which is no longer used for OpenAFS git master; unfortunately,
the new code (which uses FreeBSD's standard kernel module building
infrastructure) is not directly mergable to the OpenAFS 1.6.x branch, so
the release version is still using the old build system.
The proper way to fix it is to clean the work tree, redo the copying
param.amd64_fbsd_82.h file, and then find this part of
openafs-1.6.0/src/libafs/MakefileProto.FBSD.in:
%-ln -fs ${KSRC}/nfs nfs
%all -fbsd_71 -fbsd_72 -fbsd_72 -fbsd_73 -fbsd_74 -fbsd_80 -fbsd_81 -fbsd_82
-fbsd_90
%-ln -fs /usr/include/rpc rpc
%fbsd_71 fbsd_72 fbsd_73 fbsd_74 fbsd_80 fbsd_81 fbsd_82 fbsd_90
%-ln -fs ${KSRC}/rpc rpc
%all
which is doing conditionals on the particular FreeBSD version to account
for moved headers, instead of a more intelligent version number
comparison. Add -fbsd_83 to the first line (all -fbsd_71 [...])
and fbsd_83 to the second one (fbsd_71 fbsd_72 [...]), and then a
build should get past this issue.
However, if you just want it to build now, I think there is an easier fix.
(I'm not 100% sure, since there are some ... weird ... things going on in
this build system, and I haven't played with it recently.)
Edit openafs-1.6.0/src/libafs/Makefile and find the line that has
-ln -fs /usr/include/rpc rpc
and change that to be
-ln -fs ${KSRC}/rpc rpc
instead (preserving the tab character at the beginning of the line). I
expect that to let the build continue.
Again, sorry for all these troubles; I'll bump up the priority of getting
the port updated.
-Ben Kaduk
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: AFS install
Hi Jerry, On Mon, 14 May 2012, Jerry McAllister wrote: Hi, I installed AMD64 FreeBSD 8.3 on a new machine a couple of days ago. It seems fine so far. This afternoon I tried to install OpenAFS 1.6.0 on it from /usr/ports/net/openafs The configure ran happily and I didn't notice any errors. But, the make died soon after starting with the following complaints. make: don't know how to make ./param.amd64_fbsd_83.h. stop *** Error code 2 Stop in /usr/ports/net/openafs/work/openafs-1.6.0. ** Error code 1 I presume that means that it does not know about FreeBSD 8.3 yet. That's right; the OpenAFS build system has lots of history behind it, which means that it is not particularly elegant at handling this sort of thing. I rummaged around in the README it left in the ../work directory and saw a bunch of AMD64 versions up to 8.1 (and even 9.0) but not 8.2 or 8.3. I noticed in the Makefile where it says: IGNORE= Supports FreeBSD 8.0 and later I am not sure how that plays in it. I am definitely not a make hacker. Anyway, is there a good tinker to get past this or do I have to wait until something gets updated in the port? Or, did I just do something stupid? No fault on your end; I need to push in updates for 8.3 and 10.0 support but have been busy with schoolwork. For now, if you're up for a little bit of tinkering, you could go in to /usr/ports/net/openafs and 'make clean make extract', then: cd work/openafs-1.6.0/src/config cp param.amd64_fbsd_82.h param.amd64_fbsd_83.h and continue with the usual make install, etc., in /usr/ports/net/openafs/. If that still does not compile/run, please send me the build log (or dmesg -a output if a runtime failure) and I will look at it. By the way, I need just the client. I do not intend to start a server or a cell on this machine. I just need to talk to the cell at work. Is there a way of only installing the client? (I think the client is the biggest part, but still, do not need the server part hanging around if it would work happily that way) The upstream OpenAFS build system is not condusive to just building the client; I have asked about this. It is fairly easy to just build the server, but since my interest was mostly in the client I did not add an option for doing so. Thanks for the report, and sorry to have been so slow at catching up to 8.3/10.0. -Ben Kaduk ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 10.0-CURRENT/AMD64 (CLANG): lang/gcc46 fails to build
[-questions to bcc] On Sat, 10 Dec 2011, O. Hartmann wrote: On 12/07/11 07:11, Steve Kargl wrote: On Wed, Dec 07, 2011 at 05:56:31AM +0100, O. Hartmann wrote: config.status: creating ada/Makefile config.status: creating auto-host.h config.status: executing default commands gmake[2]: Leaving directory `/usr/ports/lang/gcc46/work/build' gmake[1]: *** [stage1-bubble] Error 2 gmake[1]: Leaving directory `/usr/ports/lang/gcc46/work/build' gmake: *** [bootstrap-lean] Error 2 *** Error code 1 Stop in /usr/ports/lang/gcc46. *** Error code 1 Stop in /usr/ports/lang/gcc46. === make failed for lang/gcc46 === Aborting update See if setting DISABLE_MAKE_JOBSi helps. This doesn't work, either. The end of the build log from that case should be more enlightening than the one you originally posted, as it is more likely to actually contain the actual error (which is not present in the snippet above). In /etc/src.conf, I use WITH_ICONV=YES and _WITH_BSD_GREP=YES. Switching off WITH_ICONV seems to solve the problem on FreeBSD 10.0-CURRENT/amd64. I do not know whether OS versions below 10.0 do support the WITH_ICONV knob. This maybe is a hint to the problem. iconv was only added to base in r219019 | gabor | 2011-02-24 19:04:39 -0500 (Thu, 24 Feb 2011) so it will first appear in the imminent 9.0 release. Assuming that the error remains reproducible with an up-to-date tree, the end of the build log from the DISABLE_MAKE_JOBS case would be useful to see. I've added gabor as a cc, since he seems to be doing most of the iconv work. -Ben Kaduk ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
how to make devfs show fdisk updates?
Dear all, I have recently been using fdisk(8) to activate additional partitions, but have been unable to cause the device nodes corresponding to the new partition to appear in /dev other than by rebooting. (This is on the device which contains the root filesystem, so kern.geom.debugflags=16 is necessary to perform the fdisk.) Please advise on how to effect the creation of the device node(s) in a non-disruptive fashion. Thanks, Ben Kaduk ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
