MacPorts 2.5.2 has been released

Hot on the heels of 2.5.1, MacPorts 2.5.2 has been released to fix an issue affecting ports building with a macports-clang compiler. Please upgrade as soon as possible. (Note that it may be a little while before the rsync mirrors have the new version.)

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: How reconcile openmodelica-dvel & octave dependencies on sundials vs. sundials2

On 2018-06-04, at 8:22 AM, Adam Dershowitz wrote: >>> The odd thing is that octave 4.2.2 was working fine with sundials (which is >>> version 3.1.0_1) This doesn't seem too likely, unless Octave was ignoring sundials. Why don't you try deleting the sundials dependency in the Octave portfile

FYI - Microsoft is buying GitHub

I assume you have seen the headline: Why Microsoft is buying GitHub: It's all about developer relationships Microsoft's move to acquire GitHub isn't all that surprising given that the company is a top contributor and has worked well with developers in recent years. Now can it keep GitHub the

Re: How reconcile openmodelica-dvel & octave dependencies on sundials vs. sundials2

It looks like sundials (v3.) won’t work with Octave 4.4, only sundials2 (2.7): http://octave.1599824.n4.nabble.com/sundials-3-td4687354.html https://savannah.gnu.org/bugs/?52475 --Adam >

Re: How reconcile openmodelica-dvel & octave dependencies on sundials vs. sundials2

Welcome to our world! How to fix this?... you could try using sundials in octave (change the dependency in the Portfile). Maybe sundials2 was just an oversight. If that works, come up with a variant. you could disable sundials in octave if you don't want or need it (again, maybe a variant).

Re: How reconcile openmodelica-dvel & octave dependencies on sundials vs. sundials2

I’m in the same situation (I have openmodelica-devel installed and want to upgrade octave). The odd thing is that octave 4.2.2 was working fine with sundials (which is version 3.1.0_1). But, the upgrade of octave to 4.4 requires the sundials2 port (2.7.0). So, somehow it seems that upgrading

Re: conflicts with master

On Jun 02 15:30:53, rai...@macports.org wrote: > On 2018-06-02 08:25, Jan Stary wrote: > > $ git log -1 > > 33mcommit 101e557b4b08974559402a3c5cf6e247561ef5e7m33m (m1;36mHEAD -> > > m1;32mmasterm33m, m1;31morigin/masterm33m, > > m1;31mm33mm33mm1;36mm1;32mm33mm1;31mm33mm1;31morigin/HEADm33m)mm >

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