Re: mysql57, boost and postgresql84

I don’t know if it helps at all, but on October 24th I did the first steps of MacPorts migration in anticipation of installing Catalina. I never did install Catalina, but I saved the myports.txt and requested.txt files. They are here: https://pastebin.com/cxM85Dq6

Re: mysql57, boost and postgresql84

On Nov 8, 2019, at 20:31, Chris Jones wrote: > On 9 Nov 2019, at 1:39 am, Ryan Schmidt wrote: > >> If you ran `sudo port install clamav`, and it was not already installed, >> MacPorts should have marked it as requested. If clamav was automatically >> installed as a dependency of something e

Re: mysql57, boost and postgresql84

> On 9 Nov 2019, at 1:39 am, Ryan Schmidt wrote: > >  > >> On Nov 8, 2019, at 16:06, Michael Newman wrote: >> >>> On Nov 7, 2019, at 06:34, Ryan Schmidt wrote: >>> >>> If `port installed requested` shows things that you don't actually want, >>> tell MacPorts by marking them as not request

Re: mysql57, boost and postgresql84

On Nov 8, 2019, at 16:06, Michael Newman wrote: > On Nov 7, 2019, at 06:34, Ryan Schmidt wrote: > >> If `port installed requested` shows things that you don't actually want, >> tell MacPorts by marking them as not requested: >> >> sudo port unsetrequested portname1 portname2 ... >> >> Then

Re: mysql57, boost and postgresql84

> On Nov 7, 2019, at 06:34, Ryan Schmidt > wrote: > > If `port installed requested` shows things that you don't actually want, tell > MacPorts by marking them as not requested: > > sudo port unsetrequested portname1 portname2 ... > >

Re: installed port wants to rebuild

> On Nov 7, 2019, at 10:39 PM, Ryan Schmidt wrote: > > > > On Nov 7, 2019, at 21:23, Stan Sanderson wrote: > >> OS X 10.14, all installed ports up-to-date. >> Re: kmymoney4-devel >> >> Since the recent problem with kdepimlibs4 was solved (thanks!), port >> upgrade outdated consistently en

Re: XCode 11 on Mojave problem, again

Dear Ruben, This definitely looks like a bug in Xcode. I would suggest you to file a bug report to Apple. Can you please try to compile a simple hello world with just the following contents // test.cpp: #include int main() { return 0; } and compile it with: /Applications/Xcode.app/Cont

XCode 11 on Mojave problem, again

Hello people,  I saw this kind of errors quite often lately around. But this times I’m hitting this with a local project, not a port in Macports. A project that used to build correctly with Xcode 10, now it seems to miss stuff in header. ninja -j 1 [1/48] Building CXX object src/libs/CMakeFile

Re: package version and variant info in `main.log`

I've noticed that in `main.log` files there is no information what version and variants have been requested – for example, ImageMagick @6.9.9-40_7+x11 Wouldn't it make sense to make `port` add this information to the very top of `main.log`? This would also help

Re: rxvt-unicode install fails

On Nov 6, 2019, at 05:54, joerg van den hoff wrote: > On 05.11.19 20:41 , Ryan Schmidt wrote: >> On Nov 5, 2019, at 10:20, joerg van den hoff wrote: >>> this is on OSX 10.14.6 and with current macports 2.6.2. >>> >>> it does not find it seems. I don't find anything related to >>> this in the

Re: libunwind-headers issue

On Nov 8, 2019, at 02:36, Werner LEMBERG wrote: > On Mac Lion, installing a fresh MacPorts from scratch, then calling > > port -N mpkg lilypond-devel +mactex +perl5_28 +python37 > > always causes a (harmless) abort. The reason is that > `libunwind-headers' gets installed as part of the depe

Re: package version and variant info in `main.log`

>> I've noticed that in `main.log` files there is no information what >> version and variants have been requested – for example, >> >> ImageMagick @6.9.9-40_7+x11 >> >> Wouldn't it make sense to make `port` add this information to the >> very top of `main.log`? This would also help identify vari

Re: package version and variant info in `main.log`

> On Nov 8, 2019, at 02:39, Werner LEMBERG wrote: > >>> I've noticed that in `main.log` files there is no information what >>> version and variants have been requested – for example, >>> >>> ImageMagick @6.9.9-40_7+x11 >>> >>> Wouldn't it make sense to make `port` add this information to the

libunwind-headers issue

On Mac Lion, installing a fresh MacPorts from scratch, then calling port -N mpkg lilypond-devel +mactex +perl5_28 +python37 always causes a (harmless) abort. The reason is that `libunwind-headers' gets installed as part of the dependencies rather early, but one of the very last steps is inst