Re: Mailing list configuration (was: Re: compiler warning)

2019-10-28 Thread Ryan Schmidt
On Oct 28, 2019, at 22:28, Al Varnell wrote: > Maybe I’m missing something obvious here, but why isn’t the list configured > IAW RFC 2369 instead? What specifically are you proposing we change?

Re: compiler warning

2019-10-28 Thread Al Varnell via macports-users
Maybe I’m missing something obvious here, but why isn’t the list configured IAW RFC 2369 instead? Sent from my iPad -Al- > On Oct 28, 2019, at 19:44, Ryan Schmidt wrote: > >  > >> On Oct 12, 2019, at 21:50, Al Varnell wrote: >> >> I feel certain that could be configured to be the default

Re: compiler warning

2019-10-28 Thread Ryan Schmidt
On Oct 12, 2019, at 12:14, Andrew Hartung wrote: > On Oct 12, 2019, at 10:10 AM, Ryan Schmidt wrote: >> Clang 11 goes with Xcode 11 but you said you have Xcode 10. You should >> either upgrade to Xcode 11 to match your clang version (I don't recommend >> this due to the many problems we've

Re: compiler warning

2019-10-28 Thread Ryan Schmidt
On Oct 12, 2019, at 21:50, Al Varnell wrote: > I feel certain that could be configured to be the default setting for this > list. It is the only one of over a dozen that I subscribe to where it’s not. > > Could that be checked into? No. Munging the Reply-To header would contravene the

Re: p5.26-dbd-mysql configure failing with +mariadb

2019-10-28 Thread Ryan Schmidt
On Oct 26, 2019, at 18:28, Darwin O'Connor wrote: > I'm trying to install p5.26-dbd-mysql which is needed to update mythtv.28, > which needs to use mariadb. > > It is generating this error: > > :info:configure 'perldoc DBD::mysql::INSTALL'. > :info:configure Checking if libs are available

Re: Freecad ports ends in error

2019-10-28 Thread Marius Schamschula
Christoph, I just updated FreeCAD to version 0.18.4. https://git.io/JeuVl My build issue turned out to be MacPort’s trace mode. It prevented make from finding the OpenGL header files in the OpenGL.Framework. Marius -- Marius Schamschula > On Oct 28, 2019, at 4:03

Re:

2019-10-28 Thread Marius Schamschula
Ken, I stand corrected. However, we do want to migrate Freecad to Qt5 for other reasons. Marius -- Marius Schamschula > On Oct 28, 2019, at 5:45 PM, Ken Cunningham > wrote: > > > Further, Freecad 0.17 depends on Qt4, which is 32bit, and hence, not > > compatible with Catalina. > > As

[no subject]

2019-10-28 Thread Ken Cunningham
> Further, Freecad 0.17 depends on Qt4, which is 32bit, and hence, not compatible with Catalina. As they said in "Independance Day" ... Uhmm, Mr. President, that may not be entirely accurate: http://packages.macports.org/qt4-mac/qt4-mac-4.8.7_9.darwin_18.x86_64.tbz2

Re: Freecad ports ends in error

2019-10-28 Thread Marius Schamschula
Christoph, Freecad is currently broken! As you found, Freecad 0.17 is looking for an older version of boost. Further, Freecad 0.17 depends on Qt4, which is 32bit, and hence, not compatible with Catalina. Among other things, Freecad 0.18.x is having problems with the demise of OpenGL on

Re: kdepimlibs4 upgrade error

2019-10-28 Thread Stanton Sanderson
Thank you for filing the ticket and for the information- Stan P.S.(and off topic) In the interim, I have been using KMyMoney 5 for Mac built with Jenkins… No problem going back and forth with v. 4 and v. 5. > On Oct 28, 2019, at 1:24 AM, Richard L. Hamilton wrote: > > Ryan said in the ticket

Re: Freecad ports ends in error

2019-10-28 Thread Chris Jones
Hi, Please follow the procedure at https://guide.macports.org/#project.tickets first see if there is an open bug report, and if there is contribute to that. Otherwise, open a new one. cheers Chris On 28/10/2019 10:51 am, Christoph Kukulies wrote: I was trying to build FreeCAD under

Freecad ports ends in error

2019-10-28 Thread Christoph Kukulies
I was trying to build FreeCAD under macports and at the end I’m getting this: ---> Verifying checksums for freecad ---> Extracting freecad ---> Applying patches to freecad ---> Configuring freecad Error: Failed to configure freecad: configure

Re: kdepimlibs4 upgrade error

2019-10-28 Thread Richard L. Hamilton
Ryan said in the ticket that it's an incompatibility with libical @3.0.6. So I reverted to libical @2.0.0_2. Since I'd already removed the old version, I got the Portfile for it from