Thanks. Deinstallation of Gimp and macports worked via the link below. The only 
thing that there is a relict in a folder named macports
with a document showing a question mark and named „Idle“.

Would be fine if I could get rid of that also.

—
Christoph



> Am 04.07.2018 um 09:31 schrieb Nathan Brazil <[email protected]>:
> 
> One option is to remove MacPorts completely from your machine via this page 
> <https://guide.macports.org/chunked/installing.macports.uninstalling.html> 
> and start over from here <https://guide.macports.org/chunked/installing.html>.
> 
> —
> 
>> On Jul 4, 2018, at 12:16 AM, Christoph Kukulies <[email protected] 
>> <mailto:[email protected]>> wrote:
>> 
>> Initially I just wanted to download Gimp to my macOS (High Sierra 10.13.5) 
>> but got informed that there is no installer tool for macOS. On the page
>> http://gimp.org/downloads <http://gimp.org/downloads> is a hint that one 
>> could use macports to install gimp, which I followed.
>> 
>> A huge amount of dependencies got installed and it took several hours to 
>> install. Nearly every compile was accomanied by a warning saying that some 
>> compiler could not be found and another was take (IIRC). Was referring to 
>> some Xcode dependency not being there.
>> 
>> After the install was finished, I first didn’t find any launchable Gimp Icon 
>> and I don’t know whether it was depending on some actions I did afterwards 
>> or if it was just the reboot, but suddenly there was a Gimp Icon in the 
>> launcher directory.
>> 
>> But looking at the Applications with some tool (App Cleaner) I saw that this 
>> Gimp was only occupying 45KB.
>> 
>> I then installed Xcode. Also did a sudo port uninstall gimp and the sudo 
>> port install gimp, to no avail.
>> 
>> So either I would like to totally uninstall any traces of the macport 
>> install attempt of Gimp and wait until a binary installer would be available 
>> or
>> do another try with Xcode installed now.
>> 
>> There is /Applications/MacPorts/Gimp.app with a lot of stuff under it.
>> 
>> —
>> Christoph
>>  
> 

Reply via email to