[MacPorts] #59753: gildas @201911b: does not build for the right C++ stdlib (undefined symbols)

MacPorts noreply at macports.org
Sat Jun 13 05:52:09 UTC 2020


#59753: gildas @201911b: does not build for the right C++ stdlib (undefined
symbols)
-------------------------+----------------------
  Reporter:  ryandesign  |      Owner:  bardeau
      Type:  defect      |     Status:  assigned
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:  2.6.2
Resolution:              |   Keywords:
      Port:  gildas      |
-------------------------+----------------------

Comment (by ryandesign):

 Replying to [comment:6 bardeau]:
 > Regarding the C++ link: I am a bit confused by all the information
 given, in particular in #51726. But as far as I understand, you suggest to
 use the MacPorts variable ${configure.cxxflags} to compile the C++ files.
 Under my environment, it resolves as "-Os -stdlib=libc++".

 Of course.

 > This is unfortunate as it provides a compilation flag (-Os) together
 with a link flag (-stdlib=libc++). In Gildas, compilation and link are 2
 clearly separated steps. Which configuration variable provides only the
 C++ **compilation** flags?

 As far as I know, having the optimization flag in there when linking
 should not be a problem. Thousands of other ports use it happily. But if
 it is a problem, you can clear it by clearing `configure.optflags`; it
 will then disappear from `configure.cxxflags` etc. In this case, make sure
 the build system already sets suitable optimization flags or make other
 arrangements for supplying them.

-- 
Ticket URL: <https://trac.macports.org/ticket/59753#comment:7>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list