Date: Sat, 31 Jan 2015 07:34:00 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 197219] Insufficient compiler information provided by Uses/compiler.mk Message-ID: <bug-197219-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197219 Bug ID: 197219 Summary: Insufficient compiler information provided by Uses/compiler.mk Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Ports Framework Assignee: freebsd-ports-bugs@FreeBSD.org Reporter: FreeBSD@ShaneWare.Biz CC: portmgr@FreeBSD.org Currently Uses/compiler.mk provides COMPILER_TYPE ALT_COMPILER_TYPE COMPILER_VERSION and ALT_COMPILER_VERSION which covers the one(or two) compilers installed in the base system. Between 9.x and 10.x we have gcc as default and clang as default, with the user having buildworld options to switch that and to not install the second compiler. Then we have CHOSEN_COMPILER_TYPE which is fine as we can tell which compiler will be used to build our port, but we don't know what version it is or what features it has. The variable COMPILER_FEATURES is set using the default compiler. Obviously this list needs to be generated to decide if the default compiler is up to building the port, but within a port Makefile we really only want to know about the compiler that will be used to build the port. Sometimes the features of the compiler and or it's version may be wanted to choose which CXXFLAGS to be used, or choose patches that need to be done based on the version of the compiler. While source files can easily be patched to handle this, the build structure used for the port may not be that easy. Also pointing out at this stage that there is no feature list for the alt compiler, which may be able to fulfil the requested compiler features without needing a compiler from ports. Sometimes it would be helpful to know the version and features of the compiler that will be used when building the port, adding the variables CHOSEN_COMPILER_VERSION and CHOSEN_COMPILER_FEATURES would fulfil that need. I am inclined to think that a db of compiler/version/features may need to be put together and used to set these variables rather than testing if a compiler works with xxx options sent to it. -- 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-197219-13>