Date: Fri, 17 Apr 2015 15:59:57 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 199500] [patch] lang/clang35 (all clang actually) : fails to set environment Message-ID: <bug-199500-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199500 Bug ID: 199500 Summary: [patch] lang/clang35 (all clang actually) : fails to set environment Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Keywords: patch Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: brooks@FreeBSD.org Reporter: marino@FreeBSD.org Assignee: brooks@FreeBSD.org Flags: maintainer-feedback?(brooks@FreeBSD.org) Keywords: patch Each port needs to set the enviroment. This is handled by the Mk framework, but when the build targets are customized, those targets need to handle it. The build problem on DragonFly with the new compiler was escaping me for a long time until I really that _ALL_ clang ports are failing to set the environment. It was failing on unit tests. The attached patch will fix this problem. It also makes additional changes: * Changes two commands to one by using -C argument for the MAKE_CMD * unsuppresses the build commands (build commands are always supposed to be shown) It also sets the environment in the post-build target although this is less critical. I did not set the environment in the post-install target that uses MAKE_CMD because it was just installing FYI -- this isn't just pedantic, DragonFly toolchain relies on the environment to switch between the two base compilers and the two sets of binutils (and the two linkers). A similar change needs to be made to all clang ports. I can provide patches if necessary. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-199500-13>