Date: Thu, 16 Oct 2008 15:05:11 -0000 From: "Jeremy Messenger" <mezz7@cox.net> To: "Desmond Chapman" <que_deseja@hotmail.com> Cc: freebsd-hackers@freebsd.org Subject: Re: need help with vbox Message-ID: <op.ui4hixu69aq2h7@localhost> In-Reply-To: <BLU126-W3895D1CBA824D05E30D5A2ED330@phx.gbl> References: <BLU126-W3895D1CBA824D05E30D5A2ED330@phx.gbl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 16 Oct 2008 05:17:47 -0000, Desmond Chapman <que_deseja@hotmail.com> wrote: > > It's dependent upon kbuild. Since the developers have no intention of > fixing the issue, I would like a tutorial on converting the kmk file to > a normal Makefile. I think you are barking at the wrong tree. :-) I don't think the issue is in kBuild. It looks like an issue is in devel/kbuild/Makefile in the do-install target part. http://pointyhat.freebsd.org/errorlogs/sparc64-errorlogs/e.6.20080731104323/kBuild-0.1.3.log ---------------------------------------- (cd ${WRKSRC}/out/freebsd.${MACHINE_ARCH}/release${PREFIX}/bin && ${COPYTREE_BIN} \* ${PREFIX}/bin) ---------------------------------------- ---------------------------------------- # make -V COPYTREE_BIN /bin/sh -c '(/usr/bin/find -d $0 $2 | /usr/bin/cpio -dumpl $1 >/dev/null 2>&1) && /usr/sbin/chown -R root:wheel $1 && /usr/bin/find $1 -type d -exec chmod 755 {} \; && /usr/bin/find $1 -type f -exec chmod 555 {} \;' -- ---------------------------------------- So.. See that $1, it is ${PREFIX}/bin. It's a bug. The COPYTREE_BIN can't have ${PREFIX}/bin. I suggest you to not use COPYTREE_BIN, so do the different method should solve kbuild ports problem. I personal haven't use COPYTREE_* before, so possible misuse COPYTREE_BIN or just can't have ${PREFIX}/bin (uncheck in bsd.port.mk/document). BTW: Add CC'ing to freebsd-ports@ to make its search useful. Cheers, Mezz -- mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.ui4hixu69aq2h7>