#2 Configured prefix directory ignored for Python files

closed
Bob Deblier
None
5
2009-08-05
2006-02-11
Ed Avis
No

I configured beecrypt-4.1.2 with

% ./configure --prefix=/home/ed

then built and installed it with

% make
% make install

The installation should put all files under /home/ed
since that is the prefix I chose. But the install
tries to write a file
/usr/lib/python2.3/site-packages/_bc.so. It should
have used /home/ed/lib/python2.3 or similar.

Discussion

  • Tim Noell
    Tim Noell
    2006-02-24

    Logged In: YES
    user_id=1460756

    I am having a similar problem. The configure script finds
    "python" on your path and then queries that python for
    include and lib dirs to determine where to install the
    python bindings.

    In my case, I have a "python2.4" on my path I want it to
    use, but it finds /usr/bin/python instead, and then tries to
    install its python bindings under /usr/lib, which also fails
    in my case because I am not root.

    You can throw the --with-python=no (--without-python) flag
    if you dont' need the python bindings, but this is just
    avoiding the problem.

    I'm no autoconf expert, but it seems one should be able to
    tell configure
    --with-python=path_to_my_python
    so that "python" doesn't have to be on your $PATH to have
    beecrypt get the right one.

    In my case, I have added a symlink in
    <prefix>/bin/python -> <prefix>/bin/python2.4
    to solve the problem for now.

    HTH,
    T.

     
  • Logged In: NO

    More on this:
    In addition to setting up
    ${PREFIX}/bin/python -> ${PREFIX}/bin/python2.4
    I had to add
    .include "../../lang/python/pyversion.mk"
    to security/beecrypt/Makefile
    to make this work.

    HTH,
    T.

     
  • Bob Deblier
    Bob Deblier
    2006-05-06

    • assigned_to: nobody --> upuaut
     
  • Bob Deblier
    Bob Deblier
    2006-05-06

    Logged In: YES
    user_id=56582

    I could add options --pythondir and --pythonlibdir to
    configure to allow you to specify other versions/locations.

    Would this be acceptable?

    Bob

     
  • Ed Avis
    Ed Avis
    2006-05-13

    Logged In: YES
    user_id=10769

    A --pythondir option would work, but I think that --prefix
    should mean what it says and all files should be installed
    somewhere under that location.

     
  • Bob Deblier
    Bob Deblier
    2007-05-01

    Logged In: YES
    user_id=56582
    Originator: NO

    I have changed the --with-python option to accept --with-python=<path-to-your-python-executable> to work around tnoell's problem.

     
  • Bob Deblier
    Bob Deblier
    2009-08-05

    • status: open --> closed
     
  • Bob Deblier
    Bob Deblier
    2009-08-05

    You can now configure --with-python=<your specific python executable path>