problem installing gnureadline
jonesc at hep.phy.cam.ac.uk
Wed Apr 18 13:49:34 UTC 2018
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
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
and then still uses the previously saved list of ports to reinstall the
ports, once you have reinstalled macports.
>> 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
>> 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
>>> for details.
>>>> Is this file provided by a port? If not, you must have installed it in
>>>> some other way.
>>>> port provides
>>> 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
> "S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise
More information about the macports-users