[MacPorts] #48647: `port select gcc` sets default C++ compiler

MacPorts noreply at macports.org
Thu Aug 20 22:30:15 PDT 2015


#48647: `port select gcc` sets default C++ compiler
-------------------------+--------------------------------
  Reporter:  john@…      |      Owner:  macports-tickets@…
      Type:  defect      |     Status:  new
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:  2.3.3
Resolution:              |   Keywords:
      Port:  gcc_select  |
-------------------------+--------------------------------
Changes (by ryandesign@…):

 * cc: ryandesign@… (added)


Comment:

 I think I agree. It was previously brought up in #30434 where it was
 requested that "port select gcc" should also make a symlink
 /opt/local/bin/cc. This was rejected. So, correspondingly, we should also
 not be setting /opt/local/bin/c++, as you say.

 Perhaps the reason why this discrepancy exists in the first place is that
 the gcc ports do actually install programs with "gcc", "g++" and "c++" in
 the name (where the "g++" and "c++" programs are identical), but do not
 install a program with just "cc" in the name.

 Usually, changing the list of files "port select" affects involves
 changing and increasing the revision of every port that can be selected.
 That would mean revbumping every gcc port, which would be a shame because
 that would be a lot of unnecessary rebuilding to just change a couple
 lines in a text file. It would be great if we could avoid that.

 I imagine the gcc_select port will need to be updated and revbumped as
 well. But I'm not sure if we have a good way to handle this for existing
 users. I don't think the select portgroup anticipated the situation where
 a file is removed from the set of selected files. We may have to have a
 post-activate block that deletes /opt/local/bin/c++ if it exists and is
 not registered to a port.

 I'm not certain what we should be doing about /opt/local/bin/cpp, since
 there is no GNU-specific equivalent (there is no "gpp"). Some ports may be
 running the C preprocessor as "$CC -E", but some may expect "cpp" to
 exist. Maybe it should be a handled by a separate "cpp_select" port?

-- 
Ticket URL: <https://trac.macports.org/ticket/48647#comment:1>
MacPorts <https://www.macports.org/>
Ports system for OS X


More information about the macports-tickets mailing list