[MacPorts] #56921: libgcc8 and libgcc-devel conflict

MacPorts noreply at macports.org
Tue Aug 7 14:56:38 UTC 2018


#56921: libgcc8 and libgcc-devel conflict
------------------------------------------+--------------------
  Reporter:  skymoo                       |      Owner:  (none)
      Type:  defect                       |     Status:  new
  Priority:  Normal                       |  Milestone:
 Component:  ports                        |    Version:
Resolution:                               |   Keywords:
      Port:  gcc8, libgcc8, libgcc-devel  |
------------------------------------------+--------------------

Comment (by cjones051073):

 Replying to [comment:4 skymoo]:
 > Replying to [comment:2 cjones051073]:
 > > libgcc8 now provides the default gcc runtime, via libgcc. Both thus
 intentionally conflict with libgcc-devel which is now based on gcc9.
 >
 > So we can no longer have the development version of `gcc` installed if
 we want stable versions as well?

 No. The situation is exactly the same as before. If you want the
 development gcc installed then you must have installed libgcc-devel
 instead of libgcc. If you do this, the ports that declare a dependency on
 libgcc will be satisfied.

 >
 > > I suggest you (forcibly) uninstall your current gcc ports, then
 reinstall them back. If you want to be able to use gcc9 you will need to
 first install this, so that libgcc-devel is installed before libgcc is.
 >
 > That's what I currently have, I installed `libgcc-devel` and then the
 other `gcc` ports. `libgcc-devel` is updated before attempting to install
 `gcc8`. Also this seems to conflict with your first statement?

 This is just a bug in the ports you have, that I fixed it the commit I
 referenced.

 The reason for issue this is there is a slight rearrangement of what the
 various ports provide. For details see

 https://github.com/macports/macports-ports/pull/2296

 So there is a little bit of dancing I needed to do when upgrading. I just
 missed the scenario you have.

 To fix the situation you now have, you need to just do the manual
 deactivation/activation. Or start again with your ports updated to include
 my latest fix.

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


More information about the macports-tickets mailing list