Date: Sat, 22 Jul 2006 10:36:52 GMT From: Dominic Fandrey <lon_kamikaze@gmx.de> To: freebsd-gnats-submit@FreeBSD.org Subject: ports/100712: [bsd.port.mk] -j with install target totally BROKEN Message-ID: <200607221036.k6MAaq20066836@www.freebsd.org> Resent-Message-ID: <200607221040.k6MAeFps050564@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 100712 >Category: ports >Synopsis: [bsd.port.mk] -j with install target totally BROKEN >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Jul 22 10:40:13 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Dominic Fandrey >Release: Releng_6 >Organization: private >Environment: FreeBSD mobileKamikaze.norad 6.1-STABLE FreeBSD 6.1-STABLE #0: Wed Jul 19 14:54:04 CEST 2006 root@mobileKamikaze.norad:/mnt/vault/obj/mnt/vault/src/sys/TPR40-6 i386 >Description: The install target, combined with the -j option is totally broken. This is troublesome, because if a port installs dependencies you cannot use -j to build the port. I have tried to find out what happens in bsd.port.mk, but all I can say is, that with -j defined the port omits all such important targets as do-extract, do-patch, do-configure or do-build and heads right to do-install, even though nothing has been built. The -j flag would be useful for SMP systems or those who use distcc. >How-To-Repeat: Go to a ports folder and run: # make -j 4 install Or go to a a ports folder that also installs build dependencies and run: # make -j 4 >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200607221036.k6MAaq20066836>