Installation sets library path incorrectly for python

Bug #1285080 reported by Chris Richardson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libadjoint
New
Undecided
Unassigned

Bug Description

When installing, the path for the libadjoint library, as defined in clibadjoint.py is the path of the build directory, not the
installation directory (at least that is what happened to me).

Therefore, if the build directory is not available at runtime :-) it will crash.

Revision history for this message
Patrick Farrell (pefarrell) wrote :

Hi Chris,

Is this with the hand-written Makefile or CMake?

Can you give me directions to reproduce on archer? (I assume it's on archer?)

Revision history for this message
Chris Richardson (chris-bpi) wrote : Re: [Bug 1285080] Re: Installation sets library path incorrectly for python

On 26/02/2014 10:57, Patrick Farrell wrote:
> Hi Chris,
>
> Is this with the hand-written Makefile or CMake?
>
> Can you give me directions to reproduce on archer? (I assume it's on
> archer?)
>

OK, I just downloaded the source, made a build directory and did:

cd build

cmake -DCMAKE_INSTALL_PREFIX=/work/e319/shared/libadjoint ..

make

which worked OK, but left the source directory hard-wired into the
install.

You should be able to look at it in /home/e319/e319/shared I think

Chris

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.