gimp2 install

[Ken Cunningham]

Probably same deal. Compiler is too old.

This ancient relic:

/usr/bin/gcc-4.2

can't build much of anything anymore, and it's getting worse by the day.

Abandon 2004!


K






On 2018-11-13, at 7:17 PM, Uli Wienands wrote:

> Ok, now I am really getting confused. 
> I cleaned zstd and installed it by itself. That actually worked; it even pulled a binary.
> 
> Still left with broken ports I let it attempt to fix these only for the thing to crap out at, you guessed it, zstd. WTF? 
> zstd is installed, same signature as Ken's upon port installed.
> But now Macports has butchered gcc 46, gcc5 and gcc6 and ghostscript. Not nice!
> 
> Anyway, trying gimp2 again. Now I get a message about all compilers being blacklisted...
> 
> Then it wants to build zstd again. I tell it no and it goes on anyway. Eventually it begins rebuilding ghostscript (one of the broken ports). It actually seems to download a binary first but then goes on to get the distfiles and building it. This fails for reasons I cannot tell.
> 
> logfile attached.
> 
> Am I completely hosed now? I mean, how does this get so messed up just trying to install one port (even if a complicated one)?
> 
> Uli
> 
> 
> On 11/13/18 8:47 PM, Ken Cunningham wrote:
>> $ port -v installed zstd
>> The following ports are currently installed:
>>   zstd @1.3.4_0 (active) platform='darwin 10' archs='x86_64' date='2018-09-03T16:17:32-0700'
>> 
>> zstd builds on 10.6.8 with a newer compiler. I used clang-3.9.
>> 
>> Nobody on a newer system could know this, so they rely on us "archeologists" to find these and blacklist compilers that don't work.
>> 
>> K
>> 
>> 
>> 
>> 
>> 
>> 
>> On 2018-11-13, at 6:33 PM, Uli Wienands wrote:
>> 
>>> Ok, so I did upgrade tk. That went ok, sort of. In the process of upgrading tk it butchered several other ports ("found 61 broken files, 5 broken ports"). In the process of fixing those it ran aground trying to install zstd. As a result, my octave 4.2.1 is now kaput :-(.
>>> 
>>> (Which explains why I do not routinely upgrade things. If it ain't broke don't fix it.)
>>> 
>>> Anyway, pressing on with gimp2. xorg-xorgproto now does install. Eventually it dies at zstd again. (port installed does not list zstd so I do not appear to have an older version installed).
>>> 
>>> As usual, log file attached.
>>> 
>>> Thanks,
>>> 
>>> Uli
>>> 
>>> 
>>> 
>>> On 11/13/18 12:31 AM, Chris Jones wrote:
>>>>> On 13 Nov 2018, at 3:49 am, Uli Wienands <wienands at gmail.com> wrote:
>>>>> 
>>>>> Given Ryan's comment I updated my Macports installation (was 2.4.2, now: 2.5.4),
>>>> Thats a huge jump... if you also had not updated your ports for that period as well, no surprise you are having problems now. Its really not a good idea to not update for that length of time...
>>>> 
>>>>> cleaned gimp2 and tried again... same error. I do this on a 10.6.8 machine, incidentally.
>>>>> 
>>>>> So is there anything else I should/could do?
>>>> Gimp2 is not the problem, tk is.
>>>> 
>>>> You need to first upgrade this specific port.
>>>> 
>>>> Try
>>>> 
>>>>> sudo port upgrade tk
>>>> And if that fails, report back.
>>>> 
>>>> Chris
>>>>> Log file attached.
>>>>> 
>>>>> Thanks,
>>>>> 
>>>>> Uli
>>>>> 
>>>>> 
>>>>>> On 11/12/18 12:52 PM, Ryan Schmidt wrote:
>>>>>> 
>>>>>>> On Nov 12, 2018, at 12:47, Uli Wienands wrote:
>>>>>>> 
>>>>>>> Hi, after Riccardo Mottola mentioned that he contributed a patch to gimp to make Gimp 2.10 run under 10.6 I tried to install it.
>>>>>>> 
>>>>>>> The install went a fair amount but then died at xorg-xorgproto, whatever that is, with the error:
>>>>>>> 
>>>>>>> Error: Failed to activate xorg-xorgproto: Image error: /opt/local/include/X11/X.h is being used by the active tk port. Please deactivate this port first, or use 'port -f activate xorg-xorgproto' to force the activation.
>>>>>>> 
>>>>>>> I am attaching the logfile.
>>>>>> I thought we fixed the tk port to no longer install that. Is your tk port up to date? Try selfupdating and upgrading tk.
>>>>>> 
>>>>>> 
>>>>>>> Incidentally: Why is /opt/local/var/macports hiden from the finder? I had to use goto Folder to get there.
>>>>>> I guess we hid it for the same reason Apple hides Library folders for you.
>>>>>> 
>>>>> <main.log>
>>> <main.log>
> 
> <main.log>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-users/attachments/20181113/6b1aa63d/attachment.html>