[Bug 202901] games/qqwing configure narrowly searches for gcc or cc and Makefile hard-codes CC CXX CPP plus does not respect CFLAGS
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Sat Sep 5 06:00:25 UTC 2015
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202901
Bug ID: 202901
Summary: games/qqwing configure narrowly searches for gcc or cc
and Makefile hard-codes CC CXX CPP plus does not
respect CFLAGS
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: Individual Port(s)
Assignee: gnome at FreeBSD.org
Reporter: kennethsalerno at yahoo.com
Assignee: gnome at FreeBSD.org
Flags: maintainer-feedback?(gnome at FreeBSD.org)
QQWing uses a configure script that narrowly searches for literally "gcc" or
cc, but will never find "gcc5" or "gcc48" and "g++5" or "g++48" if that is what
the user has set his CC CXX and CPP flags to use for ports. On top of that, the
port's Makefile hard-codes CC, CXX and CPP to use clang (or gcc 4.2 on FreeBSD
version < 10).
The configure script should be patched to just use "cc" and "c++" if CC CXX and
CPP are not set by the user, which would obsolete the need to hard-code CC CXX
CPP flags in the port's Makefile while making it flexible to support gcc5/gcc48
without modification.
test -z "$CC" && CC=cc
test -z "$CXX" && CXX=c++
Another patch would be required of the automake files to respect CFLAGS
(hard-coded to -O2 -g), CXXFLAGS and LDFLAGS but first thing's first, need to
respect compiler chosen.
The reason I happened upon this issue is because my ports are compiled with
gcc5/g++5 and when qqwing got compiled with clang I ran into an ABI
incompatibility when linking gnome-sudoku (built with gcc5) forcing me to hack
the qqwing configure script to find g++5.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-gnome
mailing list