From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of text editors" Newsgroups: gmane.emacs.bugs Subject: bug#44128: [feature/native-comp] Date: Thu, 22 Oct 2020 20:51:44 +0000 Message-ID: References: <87eelri6l8.fsf@bernoul.li> Reply-To: Andrea Corallo Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="2733"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: 44128@debbugs.gnu.org To: Jonas Bernoulli Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Oct 22 22:52:19 2020 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kVhZJ-0000Ym-91 for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 22 Oct 2020 22:52:17 +0200 Original-Received: from localhost ([::1]:48344 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kVhZH-0001uj-Pr for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 22 Oct 2020 16:52:15 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:52642) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kVhZ4-0001tF-Bs for bug-gnu-emacs@gnu.org; Thu, 22 Oct 2020 16:52:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:42495) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kVhZ4-0004bF-2z for bug-gnu-emacs@gnu.org; Thu, 22 Oct 2020 16:52:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1kVhZ4-0003D8-2C for bug-gnu-emacs@gnu.org; Thu, 22 Oct 2020 16:52:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Andrea Corallo Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 22 Oct 2020 20:52:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 44128 X-GNU-PR-Package: emacs Original-Received: via spool by 44128-submit@debbugs.gnu.org id=B44128.160339990912322 (code B ref 44128); Thu, 22 Oct 2020 20:52:02 +0000 Original-Received: (at 44128) by debbugs.gnu.org; 22 Oct 2020 20:51:49 +0000 Original-Received: from localhost ([127.0.0.1]:54041 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kVhYr-0003Cg-1F for submit@debbugs.gnu.org; Thu, 22 Oct 2020 16:51:49 -0400 Original-Received: from mab.sdf.org ([205.166.94.33]:34584 helo=ma.sdf.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kVhYp-0003CY-Gs for 44128@debbugs.gnu.org; Thu, 22 Oct 2020 16:51:48 -0400 Original-Received: from akrl by ma.sdf.org with local (Exim 4.92) (envelope-from ) id 1kVhYm-0006n9-Sp; Thu, 22 Oct 2020 20:51:44 +0000 In-Reply-To: <87eelri6l8.fsf@bernoul.li> (Jonas Bernoulli's message of "Wed, 21 Oct 2020 23:58:59 +0200") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:191316 Archived-At: Jonas Bernoulli writes: > Hello Andrea Hi Jonas! > [We talked about this briefly on Twitter; > https://twitter.com/magit_emacs/status/1313534891506757635.] > > When running gccemacs from the git repository without installing but by > using a symlink like e.g. /usr/local/bin/emacs -> ~/git/emacs/src/emacs, > then that results in an error like: > > emacs: /usr/local/bin/../native-lisp/.eln: cannot open shared > object file: No such file or directory > > You mentioned that this happens because code in pdump[er].c just relies > on invocation-directory and that you are wonder whether symlinks should > be followed to address this. > > I think they should. :D Well I agree :) I believe the only question is if we want to change `invocation-directory' to have the link followed or to do that in the load mechanism. I guess the second has less impact. Andrea