#71028 closed defect (duplicate)
boehmgc: fatal error: 'new' file not found
Reported by: | mfacorcoran | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | sequoia | Cc: | |
Port: | boehmgc |
Description
Not sure why but "sudo port upgrade outdated" seems to be failing on all (or nearly all) outdated ports -
% sudo port upgrade outdated Warning: configured user/group mcorcora does not exist, will build as root ---> Building boehmgc Error: Failed to build boehmgc: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_github.com_macports_macports-ports_devel_boehmgc/boehmgc/main.log for details. Error: Problem while installing boehmgc Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug.
the failure seems to be of the form
info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_github.com_macports_macports-ports_devel_boehmgc/boehmgc/work/gc-8.2.8" && /usr/bin/make -j16 -w all
It's undoubtedly something in my setup but not sure what. I suspected and issue with /usr/bin/make but it seems to work (at least it returns the version):
% /usr/bin/make --version GNU Make 3.81 Copyright (C) 2006 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. This program built for i386-apple-darwin11.3.0
any help appreciated
Attachments (1)
Change History (3)
Changed 6 weeks ago by mfacorcoran
comment:1 Changed 6 weeks ago by ryandesign (Ryan Carsten Schmidt)
Keywords: | sequoia added |
---|---|
Port: | boehmgc added |
Resolution: | → duplicate |
Status: | new → closed |
Summary: | port upgrade failure → boehmgc: fatal error: 'new' file not found |
The relevant error in the log is:
gc_badalc.cc:29:10: fatal error: 'new' file not found 29 | #include <new> // for bad_alloc, precedes include of gc_cpp.h | ^~~~~
This is #70750. See the solution at ProblemHotlist#clts16.
Note: See
TracTickets for help on using
tickets.
main.log