From: Ulrich Mueller <ulm@gentoo.org>
To: Yuri Khan <yuri.v.khan@gmail.com>
Cc: Andrea Corallo <akrl@sdf.org>, Eli Zaretskii <eliz@gnu.org>,
Paul Eggert <eggert@cs.ucla.edu>,
Stefan Monnier <monnier@iro.umontreal.ca>,
"Andrea Corallo via Emacs development discussions."
<emacs-devel@gnu.org>
Subject: Re: Path for system-wide .eln files
Date: Tue, 01 Sep 2020 09:16:48 +0200 [thread overview]
Message-ID: <u36427yqn@gentoo.org> (raw)
In-Reply-To: <CAP_d_8XTrvPgz+4wiNRrOkSe55R19VL_xOFJ6oygYS9JjfTOqg@mail.gmail.com> (Yuri Khan's message of "Tue, 1 Sep 2020 11:28:53 +0700")
>>>>> On Tue, 01 Sep 2020, Yuri Khan wrote:
>> > AFAIU `/usr/libexec` would be for binaries in general, infact we store
>> > there the pdumper img. Okay for `/usr/lib`.
>>
>> It should be ${libdir} I think? That is, "lib64" on 64-bit systems.
> I am on a 64-bit system and my /usr/lib64 is empty except for a single
> ld-linux-x86-64.so.2 symlink. On the other hand, /usr/lib32 contains a
> number of shared objects belonging to the libc6-i386 package. This
> tells me maybe native bitness belongs in /usr/lib.
I should have been more precise. It is in fact distro specific, so there
may be 64-bit systems where the native libs are installed in /usr/lib
(and 32-bit libs would go to /usr/lib32), while others install the
native libs in /usr/lib64.
So the right thing to do is to use configure's ${libdir}.
next prev parent reply other threads:[~2020-09-01 7:16 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-16 11:51 Native compilation: the bird-eye view Eli Zaretskii
2020-05-16 12:58 ` Andrea Corallo
2020-05-16 15:57 ` Paul Eggert
2020-05-16 16:26 ` Eli Zaretskii
2020-05-16 17:03 ` Andrea Corallo
2020-05-16 17:35 ` Eli Zaretskii
2020-05-16 17:44 ` Andrea Corallo
2020-05-16 17:50 ` Eli Zaretskii
2020-05-16 18:26 ` Andrea Corallo
2020-05-16 18:32 ` Eli Zaretskii
2020-05-16 18:41 ` Andrea Corallo
2020-05-18 14:27 ` Andrea Corallo
2020-05-19 5:08 ` ASSI
2020-05-19 16:25 ` Andrea Corallo
2020-05-19 16:37 ` Stefan Kangas
2020-05-19 19:16 ` Andrea Corallo
2020-05-29 17:25 ` Andrea Corallo
2020-06-02 15:16 ` Stefan Monnier
2020-06-03 14:23 ` Andrea Corallo
2020-06-03 14:38 ` Stefan Monnier
2020-08-10 9:23 ` Andrea Corallo via Emacs development discussions.
2020-08-10 12:20 ` Stefan Monnier
2020-08-10 21:34 ` Andrea Corallo via Emacs development discussions.
2020-08-15 10:51 ` Andrea Corallo via Emacs development discussions.
2020-08-15 15:00 ` Eli Zaretskii
2020-08-19 15:01 ` Andrea Corallo via Emacs development discussions.
2020-08-20 0:53 ` tumashu
2020-08-20 8:11 ` Andrea Corallo via Emacs development discussions.
2020-08-23 12:19 ` Andrea Corallo via Emacs development discussions.
2020-08-23 15:37 ` Stefan Monnier
2020-08-23 16:31 ` Andrea Corallo via Emacs development discussions.
2020-08-23 18:20 ` Stefan Monnier
2020-08-24 8:03 ` Andrea Corallo via Emacs development discussions.
2020-08-24 13:31 ` Stefan Monnier
2020-08-24 14:09 ` Andrea Corallo via Emacs development discussions.
2020-08-30 10:18 ` Path for system-wide .eln files (was: Native compilation: the bird-eye view) Ulrich Mueller
2020-08-30 20:50 ` Path for system-wide .eln files Andrea Corallo via Emacs development discussions.
2020-08-30 21:51 ` Stefan Monnier
2020-08-31 19:13 ` Andrea Corallo via Emacs development discussions.
2020-08-31 21:16 ` Ulrich Mueller
2020-09-01 4:28 ` Yuri Khan
2020-09-01 7:16 ` Ulrich Mueller [this message]
2020-09-01 8:46 ` tomas
2020-09-04 17:55 ` Andrea Corallo via Emacs development discussions.
2020-09-04 18:25 ` Ulrich Mueller
2020-09-04 19:47 ` Andrea Corallo via Emacs development discussions.
2020-09-04 20:01 ` Ulrich Mueller
2020-09-04 21:42 ` Stefan Monnier
2020-09-04 22:59 ` Ulrich Mueller
2020-09-05 2:58 ` Stefan Monnier
2020-09-05 7:10 ` Ulrich Mueller
2020-09-06 6:24 ` Andrea Corallo via Emacs development discussions.
2020-09-05 7:48 ` Alfred M. Szmidt
2020-05-16 19:11 ` Native compilation: the bird-eye view Yuan Fu
2020-05-17 4:04 ` Ihor Radchenko
2020-05-17 11:18 ` Arthur Miller
2020-05-16 22:09 ` John Wiegley
2020-05-17 4:11 ` Ihor Radchenko
2020-05-17 7:43 ` Andrea Corallo
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=u36427yqn@gentoo.org \
--to=ulm@gentoo.org \
--cc=akrl@sdf.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=yuri.v.khan@gmail.com \
/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).