[emboss-dev] ./configure --prefix=/somewhere --destdir=/chroot/somewhere

Moretti Sébastien sebastien.moretti at unil.ch
Tue Mar 5 13:00:40 UTC 2013


Hi Mahmut

Thanks for your answer.

I already use bindir and libdir but they have the same drawback than prefix.
At the end binaries and libraries are linked to /somewhere but I cannot 
directly install them there. Or they are linked to /chroot/somewhere and 
I need to use $LD_LIBRAY_PATH to run them, and compilation of EMBASSY 
tools fail.

Regards
Sébastien

> Hi Sebastien,
>
> I don't know about the chroot environments and has poor knowledge of
> configure system EMBOSS have. I write just in case you are not aware of
> the configure script --help option.
>
>    > ./configure --help
>
> It has a section called "Fine tuning of the installation directories"
> that i thought can be used to address the problem you described.
>
> Picked below few options that might be relevant to your query.
>
>    --bindir=DIR            user executables [EPREFIX/bin]
>    --sbindir=DIR           system admin executables [EPREFIX/sbin]
>    --libexecdir=DIR        program executables [EPREFIX/libexec]
>    --libdir=DIR            object code libraries [EPREFIX/lib]
>
> Mahmut
>
>
>
> On 05/03/13 11:14, Moretti Sébastien wrote:
>> Hi
>>
>> I wonder if it is possible to define a prefix during configure step,
>> used internally for library paths, AND a destination path, for the
>> installation step, that can be different from the prefix one.
>>
>> Files will be installed in destdir but libraries will keep
>> useful/internal paths (the one from prefix).
>>
>>
>> I ask that because we install software through a chroot environment that
>> cannot write directly in /somewhere

-- 
Sébastien Moretti
Department of Ecology and Evolution,
Biophore, University of Lausanne,
CH-1015 Lausanne, Switzerland
Tel.: +41 (21) 692 4221/4079
http://selectome.unil.ch/ http://bgee.unil.ch/



More information about the emboss-dev mailing list