#48754: New port for newsbeuter -------------------------+-------------------------------- Reporter: macports@… | Owner: macports-tickets@… Type: submission | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: fixed | Keywords: Port: newsbeuter | -------------------------+-------------------------------- Changes (by cal@…): * status: new => closed * resolution: => fixed Comment: Committed in r150971 with the following changes: - Added missing json-c dependency identified by trace mode - Fixed build environment to make sure it is UsingTheRightCompiler - Added use of `[get_canonical_archflags]` to ensure the port builds for the architecture we expect it to (this probably fixes the universal variant, even though I didn't try that) - Fixed incorrect values of `$prefix` in the build phase and removed the unnecessary destroot workaround; the Makefile supports `$DESTDIR`. Do you not want to maintain this port? -- Ticket URL: <https://trac.macports.org/ticket/48754#comment:1> MacPorts <https://www.macports.org/> Ports system for OS X

#48754: New port for newsbeuter -------------------------+-------------------------------- Reporter: macports@… | Owner: macports-tickets@… Type: submission | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: fixed | Keywords: Port: newsbeuter | -------------------------+-------------------------------- Comment (by bernicecarisa@…): Setting the CC, CXX and CPP environment variables at configure time is all that most software needs in order to use the compiler we want. But some ports have unusual configure scripts that don't obey these settings, and some ports don't have a configure script at all[http://www.alwaysreview.net/reviews/apple-customer-service/ .] For such ports, it can be necessary to set the variables at build time: build.args-append CC=${configure.cc} \ CXX=${configure.cxx} \ CPP=${configure.cpp} Unless you look closely at the build output in debug mode, it can be hard to know whether a port is using ${configure.cc} as it should. Here is one way to make it obvious: Create a directory /opt/local/bin/no_default_gcc Create a script in that directory called "cc" that always prints an error message Create symlinks "c++", "cpp", "g++", and "gcc", all pointing to the "cc" script Edit the value of "binpath" in /opt/local/etc/macports/macports.conf so that it begins with "/opt/local/bin/no_default_gcc:" -- Ticket URL: <https://trac.macports.org/ticket/48754#comment:3> MacPorts <https://www.macports.org/> Ports system for OS X

#48754: New port for newsbeuter -------------------------+-------------------------------- Reporter: macports@… | Owner: macports-tickets@… Type: submission | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: fixed | Keywords: Port: newsbeuter | -------------------------+-------------------------------- Comment (by macports@…): Yes, please add my obfuscated email and openmaintainer. -- Ticket URL: <https://trac.macports.org/ticket/48754#comment:5> MacPorts <https://www.macports.org/> Ports system for OS X