#48461: Installing caffe installs libgcc-devel despite not depending on it. --------------------------+-------------------- Reporter: jrd-freak@… | Owner: hum@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: invalid | Keywords: Port: caffe | --------------------------+-------------------- Changes (by ionic@…): * status: new => closed * resolution: => invalid Comment: Maybe you never had `libgcc` installed? What does `port installed libgcc` say? I'm not sure whether conflicting ports get automatically deactivated, AFAIK that's only true for `replaced` ports. GCC is a bit special, in that the libraries are split off into `libgcc*` ports. We currently have `libgcc` (which is the libraries taken off the current stable version - 5.2), `libgcc45` (from GCC 4.5, legacy) and `libgcc-devel` (from GCC 6 - currently unreleased.) Naturally, all GCC ports depend upon some `libgcc` port, but most are satisfied by both `libgcc` and `libgcc-devel`. `libgcc45` is special in the sense that it is co-installable with the other two and does not conflict with them, but it's also only needed for `gcc45` (and maybe other non-GCC ports, but I haven't checked.) `gcc6` currently (hard) depends on `libgcc-devel`. This will change once a stable version of `gcc6` is released. Once that's true, `libgcc` will be updated to provide the libraries of GCC 6, while `libgcc-devel` will be providing libraries of GCC 7. `gcc6` will depend on either `libgcc` or `libgcc-devel` and `gcc7` will depend on `libgcc-devel` only. -- Ticket URL: <https://trac.macports.org/ticket/48461#comment:6> MacPorts <https://www.macports.org/> Ports system for OS X