On Wed, 2015-03-18 at 20:25 -0500, Srinivasan Rajaraman wrote:
>
> 2) Issued the following command at the terminal:
> ~/nlopt-2.4.2/configure
> PYTHON=python && make && sudo make install.
This is generally a very bad idea; you should have specified a prefix
within your home directory, and then you wouldn't have to have superuser
rights to install nlopt, e.g.
./configure --prefix=$HOME/opt/nlopt
> 3) Included the following path: ~/nlopt-2.4.2/swig in the lib-site
> packages for Python-2.7.6
This is the wrong path to include. In the example above it should be
something like $HOME/opt/nlopt/lib/python2.7/site-packages ... You can
be sure that this is the right directory, if it contains the files
"nlopt.py" and "_nlopt.so".
--
Sincerely yours,
Yury V. Zaytsev
_______________________________________________
NLopt-discuss mailing list
[email protected]
http://ab-initio.mit.edu/cgi-bin/mailman/listinfo/nlopt-discuss
