Bug 196852 - devel/libcwd fails to build with GCC 4.9, USE_GCC=any is a lie
Summary: devel/libcwd fails to build with GCC 4.9, USE_GCC=any is a lie
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-18 22:47 UTC by Gerald Pfeifer
Modified: 2015-05-19 09:47 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gerald Pfeifer freebsd_committer freebsd_triage 2015-01-18 22:47:04 UTC
http://package18.nyi.freebsd.org/data/101amd64-default-PR196712/2015-01-16_07h05m42s/logs/errors/libcwd-1.0.4_1.log

libtool: compile:  g++49 -DHAVE_CONFIG_H -I./include -I./include -DCWDEBUG -ggdb -Wl,-rpath=/usr/local/lib/gcc49 -Wl,-rpath=/usr/local/lib/gcc49 -O2 -pipe -D__GNU_LIBRARY__ -fstack-protector -fno-strict-aliasing -c demangle3.cc  -fPIC -DPIC -o .libs/libcwd_la-demangle3.o
In file included from demangle3.cc:112:0:
./include/demangle.h:465:35: error: redeclaration of 'void __gnu_cxx::demangler::session<Allocator>::add_substitution(int, __gnu_cxx::demangler::substitution_nt, int)' may not have default arguments [-fpermissive]
         int number_of_prefixes = 0)
                                   ^
./include/demangle.h:1739:53: error: redeclaration of 'void __gnu_cxx::demangler::qualifier_list<Allocator>::decode_qualifiers(__gnu_cxx::demangler::qualifier_list<Allocator>::string_type&, __gnu_cxx::demangler::qualifier_list<Allocator>::string_type&, bool) const' may not have default arguments [-fpermissive]
    bool member_function_pointer_qualifiers = false) const
                                                     ^
Makefile:646: recipe for target 'libcwd_la-demangle3.lo' failed
gmake[3]: *** [libcwd_la-demangle3.lo] Error 1
Comment 2 John Marino freebsd_committer freebsd_triage 2015-02-18 15:52:13 UTC
sorry, I didn't notice this port was already locked to gcc 4.8 since there was no commit attached to the PR.

Ignore my log.
Comment 3 Gerald Pfeifer freebsd_committer freebsd_triage 2015-02-18 19:17:30 UTC
Sorry John, I thought I had replayed all of the lost Bugzilla
comments after the Bugzilla data loss in January, but apparently
not this one:


r377368 | gerald | 2015-01-18 22:49:05 +0000 (Sun, 18 Jan 2015) | 5 lines

Fails to build with newer versions of GCC (4.9 and above) due to
non-compliant C++ code.

PR:             196852, 196712
Comment 4 John Marino freebsd_committer freebsd_triage 2015-05-19 09:47:11 UTC
There is no maintainer for the port.  USE_GCC is set so there isn't anything else to do.