problem installing gnureadline

[Chris Jones]

> 
> But if one erases everything along the
> 
> https://guide.macports.org/chunked/installing.macports.uninstalling.html
> 
> what is the use to run macports uninstall ? Isn’t everything wiped out once /opt/local is erased ?

The page first describes the uninstall command. That will be enough for 
many. The 'rm -rf' is described as a second option, if you *really* want 
to get rid of everything. You can run one or the other, take you pick. 
You can run both, but indeed once you run the second whether or not you 
ran he first is a moot point, its redundant.


> 
> L.
> 
>> Le 18 avr. 2018 à 15:49, Chris Jones <jonesc at hep.phy.cam.ac.uk> a écrit :
>>
>>
>>
>> On 18/04/18 14:44, pagani laurent via macports-users wrote:
>>> You are right of course. So I ended up removing everything which was not installed yesterday or today and that cured it but is there a way to clean up completely /opt/local without removing Macports itself so that one can reply the reinstall script easily ?
>>
>> If you first follow the instructions at
>>
>> https://trac.macports.org/wiki/Migration
>>
>> to create the lists of ports you have installed, you can then if you wish replace steps c and d
>>
>> c Uninstall all installed ports:
>>
>> sudo port -f uninstall installed
>>
>> d Clean any partially-completed builds:
>>
>> sudo rm -rf /opt/local/var/macports/build/*
>>
>> with the nuke at
>>
>> https://guide.macports.org/chunked/installing.macports.uninstalling.html
>>
>> and then still uses the previously saved list of ports to reinstall the ports, once you have reinstalled macports.
>>
>>
>>> Laurent
>>>> Le 18 avr. 2018 à 15:18, Rainer Müller <raimue at macports.org <mailto:raimue at macports.org>> a écrit :
>>>>
>>>> On 2018-04-18 15:07, pagani laurent wrote:
>>>>> after uninstalling everything and following the ”migration” tuto (and removing tk from requested ports), I tried to install py36-jupyter but it stopped again with the gnureadline install which still fails in the same way as before (complaining about some scipy directory) though in principle there is nothing left from outside/weird installations.
>>>>
>>>> No port command will get rid of this file/directory when it is not
>>>> provided by a MacPorts port. You will have to clean it up manually.
>>>>
>>>>> --->  Configuring py36-gnureadline
>>>>> --->  Building py36-gnureadline
>>>>> Error: Failed to build py36-gnureadline: command execution failed
>>>>> Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_python_py-gnureadline/py36-gnureadline/main.log for details.
>>>>>
>>>>> (attached)
>>>>>
>>>>>>
>>>>>> Is this file provided by a port? If not, you must have installed it in
>>>>>> some other way.
>>>>>>
>>>>>> port provides
>>>>>> /opt/local/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/scipy-0.19.1.dist-info
>>>>>
>>>>> it says it is a directory.
>>>>> Note also that py36-scipy was installed earlier today with MP on my request without failure.
>>>>
>>>> This file is definitely not coming from the current version of
>>>> py36-scipy. I assume you used 'sudo pip install' before (or some script
>>>> did) and that installed python packages directly into the MacPorts prefix.
>>>>
>>>> The simplest solution is to just move this directory away:
>>>>
>>>> sudo mv
>>>> /opt/local/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/scipy-0.19.1.dist-info
>>>> ~/Desktop/
>>>>
>>>> Rainer
>>> "S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)
> 
> "S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)
>