Hi all,
Is there some reason that the libgcc ports are not named liked the gcc ports? In particular, shouldn't there be a libgcc6, libgcc7 and a new libgcc8 port? Cheers! Frank > On Jun 30, 2017, at 8:08 AM, Michael Dickens <[email protected]> wrote: > > Back on-list again: > > As noted by Ryan, GCC6 and prior use libgcc from GCC6. There is(are) ABI > change(s) in libgcc from GCC6 to GCC7 (e.g., some different compatibility > versions for libraries; some different symbols in libraries; some different > version in filenames). I don't know about GCC8 yet. > > Thus, moving to the current libgcc-devel (GCC7) from libgcc (GCC6) requires > rebuilding all dependent ports, which for me is about 11 ports & most are > pretty quick to rebuild. > > Given that Ryan is on top of this, I'll defer to him. I'm happy to help out, > but I'll not update GCC7 any longer (to snapshots or the latest release). > > Cheers! - MLD > > On Thu, Jun 29, 2017, at 06:03 PM, Chris Jones wrote: >> On 29 Jun 2017, at 10:48 pm, Ken Cunningham <[email protected] >> <mailto:[email protected]>> wrote: >>> The plan in the libgcc Portfile says to keep moving libgcc along until >>> there is an incompatible ABI change, and then when that happens, spin off >>> the last compatible version as a separate port (like this one libgcc45 >>> @4.5.4_12 (lang)) to support all the gcc versions that can't move past that >>> version of libgcc, and then move the rest along. >>> >>> So long as gcc 5 / 6 are compatible with libgcc 7 or even libgcc 8 , should >>> be no problem. >>> >>> To install libgcc-devel you need to uninstall or deactivate libgcc first, >>> of course, as they overwrite each other's files. >> >> Yes, of course, i understand this. My point was really unless there is a >> reason not to the default libgcc port should be kept up to date with the >> latest stable release, which is as of now gcc7. I have no interest to work >> with a real devel release, so have no plans to update my libgcc port to >> libgcc-devel. >> >> Chris >> >>> >>> At some point, bootstrapping gets to be a concern. >>> >>> K >>> On 2017-06-29, at 1:16 PM, Christopher Jones wrote: >>> >>>> Hi, >>>> >>>> In my opinion libgcc should be based on the latest stable gcc release, >>>> which is now gcc7. Right now, if I try and install gcc 7 I get >>>> >>>>> Oberon ~ > sudo port install gcc7 >>>>> Portfile changed since last build; discarding previous state. >>>>> ---> Computing dependencies for gcc7 >>>>> Error: Can't install libgcc-devel because conflicting ports are active: >>>>> libgcc >>>>> Error: Follow https://guide.macports.org/#project.tickets >>>>> <https://guide.macports.org/#project.tickets> to report a bug. >>>>> Error: Processing of port gcc7 failed >>>> >>>> which in my opinion should be resolved. >>>> >>>> Chris >>>> >>>>> On 29 Jun 2017, at 8:49 pm, Michael Dickens <[email protected] >>>>> <mailto:[email protected]>> wrote: >>>>> >>>>> I recently noticed that gcc7 had an update, and so I've started updating >>>>> it. I'll move it to the 7.1 release shortly. There's also a new gcc8 >>>>> snapshot that I'll look into getting up for folks on the bleeding edge >>>>> to try out (as I'm often asked to do for UHD / Volk / GNU Radio). >>>>> >>>>> The question comes up as to what version "libgcc" should be. Right now >>>>> libgcc is a subport of gcc6. gcc7 requires an updated version of libgcc, >>>>> as I'm guessing gcc8 does. >>>>> >>>>> I can easily leave libgcc attached to gcc6, and then disable >>>>> libgcc-devel in favor of libgcc7 and libgcc8 ... but, I'm pretty new at >>>>> the gcc / libgcc combo so I'm really not sure what the best or proper >>>>> way to go here is. >>>>> >>>>> Looking for thoughts and direction on how to proceed. Thx! - MLD >
