Re: Failed to install libgcc9: no destroot found

2019-09-27 Thread Piet van Oostrum
Vahid Askarpour  writes:

> port provides /opt/local/lib/libgcc/libatomic.1.dylib results in:
>
> /opt/local/lib/libgcc/libatomic.1.dylib does not exist.
>
Is there anything in /opt/local/lib/libgcc ?
-- 
Piet van Oostrum 
WWW: http://piet.vanoostrum.org/
PGP key: [8DAE142BE17999C4]


Re: Failed to install libgcc9: no destroot found

2019-09-27 Thread Piet van Oostrum
Chris Jones  writes:

> You are still getting
>
> :error:activate Failed to activate libgcc9: Image error:
> /opt/local/lib/libgcc/libatomic.1.dylib is being used by the active
> libgcc port.  Please deactivate this port first, or use 'port -f 
> activate libgcc9' to force the activation.
> :debug:activate Error code: registry::image-error
> :debug:activate Backtrace: Image error:
> /opt/local/lib/libgcc/libatomic.1.dylib is being used by the active
> libgcc port.  Please deactivate this port first, or use 'port -f 
> activate libgcc9' to force the activation.
>
> This is not correct. libgcc has not installed anything (other than a
> stub readme file) for some time now.

But could it have been installed by some other libgcc* port? Like libgcc8?
What does 'port provides /opt/local/lib/libgcc/libatomic.1.dylib' say?
-- 
Piet van Oostrum 
WWW: http://piet.vanoostrum.org/
PGP key: [8DAE142BE17999C4]


Re: Portfile question (actually, tcl question)

2019-09-21 Thread Piet van Oostrum
Gerben Wierda  writes:

> set startupitemstring   [variant_isset "withdnsserver" ? "port load 
> dns-server\n\t" : ""]

Try this one:

set startupitemstring [expr [variant_isset withdnsserver] ? {"port load 
dns-server\n\t"} : {""}]

-- 
Piet van Oostrum 
WWW: http://piet.vanoostrum.org/
PGP key: [8DAE142BE17999C4]


Re: help needed: “Error: clang-4.0 has been replaced by clang-8.0; please install that instead”

2019-07-23 Thread Piet van Oostrum
Dmitri Zaitsev  writes:

> Hi everyone,
> Any help is appreciated with this problem:
>
> https://stackoverflow.com/questions/57162325/macports-error-clang-4-0-has-been-replaced-by-clang-8-0-please-install-that
>
I would suggest to check if there is a port installed with a dependency on 
clang-4.0 or llvm-4.0. When my system automatically switched from clang-4.0 to 
clang-8.0 I remember I had to do some manual cleanup. I think it was 
ld64-latest.
Run 'port installed|grep llvm' to check.
Or maybe 'port installed|grep clang'.

-- 
Piet van Oostrum 
WWW: http://piet.vanoostrum.org/
PGP key: [8DAE142BE17999C4]


Re: Heads up: poppler won't build

2019-02-25 Thread Piet van Oostrum
Mojca Miklavec  writes:

> Dear Dave,
>
> On Mon, 25 Feb 2019 at 00:55, Dave Horsfall wrote:
>>
>> Sierra 10.12.6 + latest security updates, MacPorts 2.5.4.
>>
>> Doing my regular Monday "port upgrade outdated", and...
>>
>>  --->  Computing dependencies for poppler
>>  --->  Configuring poppler
>>  Error: poppler cannot be built while another version of poppler is 
>> active.
>>  Error: Please forcibly deactivate the existing copy of poppler, e.g. by 
>> running:
>>  Error:
>>  Error: sudo port -f deactivate poppler
>>  Error:
>>  Error: Then try again.
>>  Error: Failed to configure poppler: poppler is active
>
> Yes, I would count it as a bug. Primarily as a bug in poppler build
> system, but as a consequence also a bug on our side. I don't know what
> precisely happened, but I assume that poppler picks its own installed
> headers from the previous version from $prefix and then fails to
> build.

There is an explicit test in the poppler Portfile. It seems this was necessary 
for some older version.

if {${subport} ne ${name}} {
...
} else {
# generation of Poppler-0.18.gir fails if previous version of poppler is 
active
# appropriate for main poppler port only
conflicts_build ${name}
}

-- 
Piet van Oostrum 
WWW: http://piet.vanoostrum.org/
PGP key: [8DAE142BE17999C4]


Re: Error in trace mode

2019-02-19 Thread Piet van Oostrum
Ryan Schmidt  writes:

> On Feb 9, 2019, at 13:02, Piet van Oostrum wrote:
>
>> Ken Cunningham writes:
>> 
>>> due to a weird idiosyncracy, if set autoconf.cmd you need to specify the
>>> depends.build stuff after that line.
>>> 
>>> No idea if this can ever be fixed. You just have to "know" this.
>>> 
>> 
>> Actually, I found out after much trial and error that the solution is
>> to add port:autoconf and port:automake not only to depends_build, but
>> also to depends_lib. Which of course is weird, as they are not needed
>> after the configure phase. And I needed a build dependency on
>> pkgconfig, because that is used in configure to check the versions of
>> some dependencies.
>
> Don't add those to depends_lib. Add them to depends_build, after changing 
> autoconf.cmd.
>
> Ken, it's not a weird idiosyncrasy; it's just the way it was designed to
> work. I've discussed the reason for that design before. In retrospect,
> it was probably wrong to design it that way, and we could yet change the
> design. Please look up the prior discussion and resume it if you're
> interested.

I have done it this way. But if that is the way it is supposed to be
used, then it should be documented.
-- 
Piet van Oostrum 
WWW: http://piet.vanoostrum.org/
PGP key: [8DAE142BE17999C4]


Re: Error in trace mode

2019-02-09 Thread Piet van Oostrum
Ken Cunningham  writes:

> due to a weird idiosyncracy, if set autoconf.cmd you need to specify the
> depends.build stuff after that line.
>
> No idea if this can ever be fixed. You just have to "know" this.
>

Actually, I found out after much trial and error that the solution is to add  
port:autoconf and port:automake not only to depends_build, but also to 
depends_lib. Which of course is weird, as they are not needed after the 
configure phase. And I needed a build dependency on pkgconfig, because that is 
used in configure to check the versions of some dependencies.

And with that it works, even with set autoconf.cmd after the dependencies.
-- 
Piet van Oostrum 
WWW: http://piet.vanoostrum.org/
PGP key: [8DAE142BE17999C4]


Error in trace mode

2019-02-08 Thread Piet van Oostrum
I am testing a Portfile, and running with trace mode:

sudo port -vst install

I get this error message:

Warning: The following existing file was hidden from the build system by trace 
mode:
  /opt/local/bin/aclocal

aclocal is part of automake, and I have automake as build dependency:

depends_build   port:autoconf \
port:automake

use_autoconfyes
autoconf.cmd./bootstrap

I have no idea how to get rid of this warning. Without -t the port installs 
without problems.
Can anyone give me an idea how to solve this?
-- 
Piet van Oostrum 
WWW: http://piet.vanoostrum.org/
PGP key: [8DAE142BE17999C4]



Re: gimp doesn't open images

2019-01-27 Thread Piet van Oostrum
Riccardo Mottola via macports-users  writes:

> Hi All,
>
>
> after upgrading all my ports, GIMP is malfunctioning. It starts, but
> then it will fail at loading any image, spitting out two alert messages,
> but not crashing (the loading plugin has the issue).
>
>
>
> Any of you experiencing something similar?
>
>
https://trac.macports.org/ticket/57842

-- 
Piet van Oostrum 
WWW: http://piet.vanoostrum.org/
PGP key: [8DAE142BE17999C4]


Re: Gimp crashes when loading png or jpg

2019-01-08 Thread Piet van Oostrum
Ryan Schmidt wrote:

 > On Dec 31, 2018, at 14:11, Piet van Oostrum wrote:
 > 
 > > Suddenly my gimp crashes when I try to load a PNG or JPG file. It gives 
 > > the error message:
 > > Plug-in crashed: "file-png"
 > > (/Applications/MacPorts/GIMP.app/Contents/Resources/lib/gimp/2.0/plug-ins/file-png/file-png)
 > > 
 > > Plug-in crashed: "file-jpeg"
 > > (/Applications/MacPorts/GIMP.app/Contents/Resources/lib/gimp/2.0/plug-ins/file-jpeg/file-jpeg)
 > > 
 > > This is gimp @2.10.8_0+animation+quartz and gimp2 
 > > @2.10.8_2+python27+quartz on MacOS High Sierra.
 > > I upgraded on 26 december and before that it worked. I also uninstalled 
 > > and reinstalled both gim and gimp2 from source but that did not help.
 > > 
 > > Is this a known issue?
 > 
 > I'm not sure. Did something actually crash? If so, a log should have been 
 > left behind in ~/Library/Logs/DiagnosticReports; if so, showing us that 
 > logfile might help us diagnose the issue.

I found this today:

https://trac.macports.org/ticket/57842

-- 
Piet van Oostrum 
WWW: http://piet.vanoostrum.org/
PGP key: [8DAE142BE17999C4]



Gimp crashes when loading png or jpg

2019-01-05 Thread Piet van Oostrum
Hello,

Suddenly my gimp crashes when I try to load a PNG or JPG file. It gives the 
error message:
Plug-in crashed: "file-png"
(/Applications/MacPorts/GIMP.app/Contents/Resources/lib/gimp/2.0/plug-ins/file-png/file-png)

Plug-in crashed: "file-jpeg"
(/Applications/MacPorts/GIMP.app/Contents/Resources/lib/gimp/2.0/plug-ins/file-jpeg/file-jpeg)

This is gimp @2.10.8_0+animation+quartz and gimp2 @2.10.8_2+python27+quartz on 
MacOS High Sierra.
I upgraded on 26 december and before that it worked. I also uninstalled and 
reinstalled both gim and gimp2 from source but that did not help.

Is this a known issue?
-- 
Piet van Oostrum 
WWW: http://piet.vanoostrum.org/
PGP key: [8DAE142BE17999C4]



Re: GIMP native Quartz

2018-03-02 Thread Piet van Oostrum
Riccardo Mottola via macports-users  writes:

> Question: GIMP works quite fine, but compared to the official build I
> got on the website (which is for 10.6 and up though), in our version all
> controls look like GTK on X11, while in the other one they look more
> mac-like, some look being even native.
> Is this a difference of OS? GTK? build setting? a GTK theme?

I have compared the current Macports build of Gimp with +quartz and the one 
downloaded from gimp.org. They look mostly the same but they are slightly 
different.
The Macports one has old-fashioned rounded buttons with big round corners 
(almost half circles). The downloaded one has the more modern buttons with tiny 
corners.
AFAIK, the GIMP UI is completely based on GTK. The look-and-feel should depend 
on the theme. I think the look-and-feel is emulated, and does not use the 
native MacOS widgets. But I have the same theme in both cases (Default). I 
looked in the theme directory and they are equal. So maybe it comes down to a 
different GTK implementation.
-- 
Piet van Oostrum 
WWW: http://piet.vanoostrum.org/
PGP key: [8DAE142BE17999C4]


Upgrade/install osxfuse gives checksum errors.

2017-09-25 Thread Piet van Oostrum
--->  Verifying checksums for osxfuse
Error: Checksum (rmd160) mismatch for prefpane-8a65eb2.tar.gz
Error: Checksum (sha256) mismatch for prefpane-8a65eb2.tar.gz
Error: Failed to checksum osxfuse: Unable to verify file checksums

-- 
Piet van Oostrum 
WWW: http://piet.vanoostrum.org/
PGP key: [8DAE142BE17999C4]



Re: Rescuing a Macports file from Time Machine

2017-02-24 Thread Piet van Oostrum
Michael Parson  writes:

> For those allergic to command-lines, or afraid of terminals, you can
> use 'Shift-CMD-G' (or Menu Bar->Go->Go to Folder) and put '/opt' in the
> dialog box that opens.

You can also do the Shift-Cmd-G while in TM.
-- 
Piet van Oostrum 
WWW: http://pietvanoostrum.com/
PGP key: [8DAE142BE17999C4]