From: Eli Zaretskii <eliz@gnu.org>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: emacs-devel@gnu.org, akrl@sdf.org
Subject: Re: Where is the eln search path defined
Date: Sat, 16 May 2020 09:37:36 +0300 [thread overview]
Message-ID: <834ksgv0zz.fsf@gnu.org> (raw)
In-Reply-To: <87sgg0c2ve.fsf@linaro.org> (message from Alex Bennée on Fri, 15 May 2020 22:19:49 +0100)
> From: Alex Bennée <alex.bennee@linaro.org>
> Date: Fri, 15 May 2020 22:19:49 +0100
> Cc: emacs-devel@gnu.org
>
> > Mmh I see. Would be interesting if you could check the DESTDIR value
> > (if any) in your build environment.
>
> Definitely not in env:
>
> 19:55:42 [alex@qemu-test:~/s/e/emacs.git] native-comp|✔ + env | grep DESTDIR
> 19:56:31 [alex@qemu-test:~/s/e/emacs.git] native-comp|✔ 1 +
>
> >>> 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?
> >>
> >> I can't quite follow where the automake magic sets DESTDIR but in the
> >> main Makefile I certainly have:
> >>
> >> # The default location for installation. Everything is placed in
> >> # subdirectories of this directory. The default values for many of
> >> # the variables below are expressed in terms of this one, so you may
> >> # not need to change them. This defaults to /usr/local.
> >> prefix=/home/alex/src/emacs/install
> >>
> >> Where is DESTDIR defined during the build?
> >
> > That is a very good question.
>
> I can't see it set, although LISP and BIN DESTDIRS are set:
I think this is looking in the wrong direction: DESTDIR is almost
_never_ defined. It exists for a corner use case, so much so that I
even don't think it will help to describe that use cased here.
My guess is something else is causing this.
Of course, I could be wrong, since I don't know enough about these
details of native compilation. Apologies if I cause more confusion
than help.
prev parent reply other threads:[~2020-05-16 6:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 8:57 Where is the eln search path defined Alex Bennée
2020-05-15 16:49 ` Andrea Corallo
2020-05-15 17:19 ` Alex Bennée
2020-05-15 18:10 ` Andrea Corallo
2020-05-15 21:19 ` Alex Bennée
2020-05-15 21:55 ` Andrea Corallo
2020-05-17 11:00 ` Alex Bennée
2020-05-17 12:45 ` Andrea Corallo
2020-05-17 13:55 ` Alex Bennée
2020-05-17 14:26 ` Andrea Corallo
2020-05-18 15:10 ` Alex Bennée
2020-05-18 15:39 ` Andrea Corallo
2020-05-18 16:34 ` Alex Bennée
2020-05-18 17:23 ` Andrea Corallo
2020-05-19 10:39 ` Alex Bennée
2020-05-19 10:46 ` Andrea Corallo
2020-05-19 14:49 ` Andrea Corallo
2020-05-19 18:35 ` Alex Bennée
2020-05-19 18:57 ` Andrea Corallo
2020-05-20 7:06 ` Alex Bennée
2020-05-25 14:13 ` Alex Bennée
2020-05-25 15:01 ` Gong-Yi Liao 廖宮毅
2020-05-25 18:44 ` Andrea Corallo
2020-05-19 21:07 ` Thomas Fitzsimmons
2020-05-16 6:37 ` Eli Zaretskii [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=834ksgv0zz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=akrl@sdf.org \
--cc=alex.bennee@linaro.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).