Re: Where is the eln search path defined

[Andrea Corallo <akrl@sdf.org>]

Alex Bennée <alex.bennee@linaro.org> writes:

> Hi,
>
> I thought it was about time I started getting the native-comp branch
> running on some of my aarch64 machines. The bionic version of libgccjit
> for aarch64 failed so I ended up having to build the latest from master
> and adding it to the search path.
>
> Emacs seems to have built fine but when I run it I get:
>
>   08:41:58 [alex@qemu-test:~/s/emacs] $ emacs -nw
>   emacs: /usr/bin/../lisp/eln-aarch64-unknown-linux-gnu-e59b16aa72ffe0cd/custom.eln: cannot open shared object file: No such file or directory
>
> The file in question is in my install directory ($HOME/src/emacs/install):
>
>   install/share/emacs/28.0.50/lisp/eln-aarch64-unknown-linux-gnu-e59b16aa72ffe0cd/custom.eln
>
> but emacs doesn't seem to be able to find it. I'm wondering what is
> different between aarch64 and x86 because in both cases all I've really
> done is add $HOME/src/emacs/install/bin to me PATH.
>
> Any pointers?

Hi Alex,

Emacs thinks the binary is installed in '/usr/bin/' and the relative path
to find the eln from there is expected to be
'../lisp/eln-aarch64-unknown-linux-gnu-e59b16aa72ffe0cd/custom.eln'.

I believe of the two information the first is wrong in this case.  This
is coming from the DESTDIR value while compiling.  Is it possible that
Emacs was compiled with a certain DESTDIR value and then installed using
a different one?

This would explain even if I understand this is really not ideal.

  Andrea

-- 
akrl@sdf.org