net/libdnet does not build inside of a jail. I believe this is because the configure script looks for /dev/bpf0 and builds eth-bsd.c if it exists. In the case of a jail /dev/bpf0 does not exist so the post-build step fails. The only reference I could find to this problem is at: http://lists.freebsd.org/pipermail/freebsd-ports/2006-November/037099.html and has no solution. I've attached a port which marks the port as broken in the case of /dev/bpf0 not existing. A better solution would be to patch configure to still build eth-bsd.c but I hesitate to do that since building it anyways means it will just error out when running. I've CC'ed the maintainer on this. How-To-Repeat: Attempt to build net/libdnet in a jail. You will get the same error message as referenced in the thread above.
State Changed From-To: open->feedback Awaiting maintainers feedback http://www.freebsd.org/cgi/query-pr.cgi?pr=113893 Adding to audit trail from misfiled PR ports/113899: Date: Thu, 21 Jun 2007 04:44:05 +0000
Jonatan, how should we resolve this PR? http://www.freebsd.org/cgi/query-pr.cgi?pr=113893 Should we go with the patch included? -- Pav Lucistnik <pav@oook.cz> <pav@FreeBSD.org> Geography is only physics slowed down, with a few trees stuck on it... -- Terry Pratchett
On 7/16/07, Pav Lucistnik <pav@freebsd.org> wrote: > Jonatan, how should we resolve this PR? > > http://www.freebsd.org/cgi/query-pr.cgi?pr=113893 > > Should we go with the patch included? Yes, please do.
miwi 2007-07-16 07:12:54 UTC FreeBSD ports repository Modified files: net/libdnet Makefile Log: - Marked BROKEN Does not build properly without /dev/bpf0. PR: 113893 Submitted by: Wesley Shields <wxs@atarininja.org> Approved by: maintainer Revision Changes Path 1.28 +4 -0 ports/net/libdnet/Makefile _______________________________________________ cvs-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org"
State Changed From-To: feedback->closed Committed. Thanks!
Hiya, I just came across this. I do pkg builds all the time, and I own my buildboxens (all other users are trusted), my fix would be to just add a devfs ruleset to unhide the /dev/bpf0 on the jail, somethin like: root@firstcut:~# devfs -m /usr/jails/spryjail/dev/ rule show 100 include 1 200 include 2 300 include 3 root@firstcut:~# devfs -m /usr/jails/spryjail/dev rule add path 'bpf*' unhide root@firstcut:~# devfs -m /usr/jails/spryjail/dev/ rule show 100 include 1 200 include 2 300 include 3 400 path bpf* unhide root@firstcut:~# devfs -m /usr/jails/spryjail/dev rule apply 400 root@firstcut:~# devfs -m /usr/jails/spryjail/dev/ rule show 100 include 1 200 include 2 300 include 3 400 path bpf* unhide root@firstcut:~# dir /usr/jails/spryjail/dev/bpf0 total 1 crw------- 1 root wheel - 0, 105 Mar 26 17:40 bpf0 then go back to the jail and build libdnet. Of course, bpf0 shouldn't be on the jail for security reasons, but like I said, I own the box and want to get done w/ my pkg builds. Hope this is of any use to anyone encountering this problem ;-)