Re: gcc49 fails to build

On 2018-06-11 06:39, Dave Horsfall wrote: > On Sun, 10 Jun 2018, Ken Cunningham wrote: > >> Dave, I would be tempted to uninstall gcc49 and just see what happens. >> I don't think you need it. > > OK, with trepidation: > >     ozzie:~ dave# port uninstall gcc49 >     --->  Deactivating gcc49

Re: gcc49 fails to build

On Jun 10, 2018, at 23:05, Dave Horsfall wrote: > Sanitised version attached; it's a bit out of date, but the hardware has not > changed. > > I'll attempt another High Sierra upgrade later, when I have a few hours to > spare, and report back. > > -- Dave Ok, so you have the MacBook6,1.

Re: gcc49 fails to build

On Jun 10, 2018, at 23:39, Dave Horsfall wrote: > On Sun, 10 Jun 2018, Ken Cunningham wrote: > >> Dave, I would be tempted to uninstall gcc49 and just see what happens. I >> don't think you need it. > > OK, with trepidation: > >ozzie:~ dave# port uninstall gcc49 >---> Deactivating

Re: gcc49 fails to build

On Thu, 7 Jun 2018, Ryan Schmidt wrote: Speaking of Xcode, I keep being offered to upgrade it, but it will only run on High Sierra. I assume this upgrade offer is coming from the Mac App Store. I'm not sure why it would offer you a version of Xcode that's not compatible with your OS. It's

Re: gcc49 fails to build

On 2018-06-10, at 8:54 PM, Dave Horsfall wrote: > On Tue, 5 Jun 2018, Christopher Jones wrote: > > [...] > > Sorry for the delay, but I have several disparate systems here to maintain, > along with a bunch of electronics projects. Anyway... > >> Its possible you have a port installed using

Re: gcc49 fails to build

On Tue, 5 Jun 2018, Christopher Jones wrote: [...] Sorry for the delay, but I have several disparate systems here to maintain, along with a bunch of electronics projects. Anyway... Its possible you have a port installed using a gcc49 variant, and when you update this choice is maintained,

Re: gcc49 fails to build

On Jun 5, 2018, at 11:42, Dave Horsfall wrote: > Speaking of Xcode, I keep being offered to upgrade it, but it will only run > on High Sierra. I assume this upgrade offer is coming from the Mac App Store. I'm not sure why it would offer you a version of Xcode that's not compatible with your

Re: gcc49 fails to build

Dave Horsfall wrote: > On Tue, 5 Jun 2018, Ken Cunningham wrote: > >> You will still need to fix this >> >> >> , and who knows what else >> >> The real question is why? What do you need gcc49 for that

Re: gcc49 fails to build

> On 5 Jun 2018, at 5:42 pm, Dave Horsfall wrote: > > On Mon, 4 Jun 2018, Ryan Schmidt wrote: > >> Here is the bug report corresponding to that problem: >> https://trac.macports.org/ticket/56511 > > Ooh - a utility called "sw_vers"! I wonder what other hidden gems are > lurking,

Re: gcc49 fails to build

On Tue, 5 Jun 2018, Ken Cunningham wrote: You will still need to fix this , and who knows what else The real question is why? What do you need gcc49 for that gcc5 doesn't do? Because I use whatever

Re: gcc49 fails to build

On 2018-06-05, at 9:53 AM, Ken Cunningham wrote: > build on 10.16 and 10.17 before I get shot, read this as "darwin 16 and darwin 17" please...

Re: gcc49 fails to build

On 2018-06-05, at 9:42 AM, Dave Horsfall wrote: > On Mon, 4 Jun 2018, Ryan Schmidt wrote: > >> Here is the bug report corresponding to that problem: >> https://trac.macports.org/ticket/56511 > > Ooh - a utility called "sw_vers"! I wonder what other hidden gems are > lurking, essentially

Re: gcc49 fails to build

On Mon, 4 Jun 2018, Ryan Schmidt wrote: Here is the bug report corresponding to that problem: https://trac.macports.org/ticket/56511 Ooh - a utility called "sw_vers"! I wonder what other hidden gems are lurking, essentially undocumented, on one of Apple's finest products? After over 40

Re: gcc49 fails to build

On Jun 4, 2018, at 16:05, Dave Horsfall wrote: > On Mon, 4 Jun 2018, Ryan Schmidt wrote: > >>> I won't include the entire log (yet), as I'm sure that I'm not the only >>> one. What I certainly do *not* want, however, is to rebuild GCC, so I >>> consider this to be a blessing in disguise :-)

Re: gcc49 fails to build

On Jun 4, 2018, at 03:42, Mojca Miklavec wrote: > On 4 June 2018 at 05:36, Dave Horsfall wrote: >> ---> Building gcc49 >> Error: Failed to build gcc49: command execution failed >> Error: See >>

Re: gcc49 fails to build

On Mon, 4 Jun 2018, Riccardo Mottola via macports-users wrote: coulkd this be due to the latest C++ fixes of macports? Fixed in 2.5.1, I'm told, hence my query as to whether it's a known issue before I waste time filing a duplicate bug report. -- Dave

Re: gcc49 fails to build

On Mon, 4 Jun 2018, Mojca Miklavec wrote: To me this looks like the macports-libstdc++ issue that was solved in MacPorts 2.5.1. Thanks; I thought it was familiar, hence my reluctance to include the log etc, but since Ryan asked... My next MacPorts update is due next Monday (I check every

Re: gcc49 fails to build

Hi, Dave Horsfall wrote: We can't guess what the problem is. Please file a bug report and attach the compressed main.log. I like to make sure that I'm not duplicating a bug report -- how do *you* go bug-hunting? -- but OK, one hidously-long filename "main.log.gz" attached... In the

Re: gcc49 fails to build

On Mon, 4 Jun 2018, Ryan Schmidt wrote: I won't include the entire log (yet), as I'm sure that I'm not the only one. What I certainly do *not* want, however, is to rebuild GCC, so I consider this to be a blessing in disguise :-) We can't guess what the problem is. Please file a bug report

Re: gcc49 fails to build

Hi, On 4 June 2018 at 05:36, Dave Horsfall wrote: > ---> Building gcc49 > Error: Failed to build gcc49: command execution failed > Error: See > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc49/gcc49/main.log > for details.

Re: gcc49 fails to build

On Jun 3, 2018, at 22:36, Dave Horsfall wrote: > ---> Building gcc49 > Error: Failed to build gcc49: command execution failed > Error: See > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc49/gcc49/main.log > for

gcc49 fails to build

---> Building gcc49 Error: Failed to build gcc49: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc49/gcc49/main.log for details. Error: rev-upgrade failed: Error rebuilding gcc49 I