From: Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Pankaj Jangid <pankaj@codeisgreat.org>
Cc: 47783@debbugs.gnu.org
Subject: bug#47783: 28.0.50; [feature/native-comp] libgccjit.so: error: error invoking gcc driver
Date: Fri, 16 Apr 2021 09:25:40 +0000 [thread overview]
Message-ID: <xjflf9ibmy3.fsf@sdf.org> (raw)
In-Reply-To: <m27dl2prto.fsf@codeisgreat.org> (Pankaj Jangid's message of "Fri, 16 Apr 2021 13:46:35 +0530")
Pankaj Jangid <pankaj@codeisgreat.org> writes:
> Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of
> text editors" <bug-gnu-emacs@gnu.org> writes:
>
>> I don't know what happened here but I bet has to do with the value of
>> one of these three env vars [1] and most likely PATH.
>>
>> [1] <https://gcc.gnu.org/onlinedocs/jit/internals/index.html#environment-variables>
>>
>
> I am working with pre-built version of ‘gcc’ and ‘libgccjit’ from
> Homebrew. So I tried to set the following environment
> variables. Experimented with various permutation combinations of these.
>
> #+begin_src elisp
> (add-to-list 'exec-path
> "/usr/local/opt/gcc/bin")
> (setenv "PATH" (mapconcat 'identity exec-path ":"))
> (setenv "LD_LIBRARY_PATH"
> "/usr/local/opt/libgccjit/lib/gcc/10:/usr/local/opt/gcc/lib/gcc/10")
> (setenv "LIBRARY_PATH"
> "/usr/local/opt/libgccjit/lib/gcc/10:/usr/local/opt/gcc/lib/gcc/10")
> #end_src
>
> The above are standard location of ‘gcc’ and ’libgccjit’ artifacts.
>
> The exec-path configuration above crashes my Emacs at startup. So I had
> to comment that out.
> \f
>
> Is there a way in Emacs to get all the environment variables in one
> go?
One can use the `process-environment' variable. Also might be useful for
you `initial-environment'.
Andrea
next prev parent reply other threads:[~2021-04-16 9:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-15 2:50 bug#47783: 28.0.50; [feature/native-comp] libgccjit.so: error: error invoking gcc driver Pankaj Jangid
2021-04-15 6:58 ` Eli Zaretskii
2021-04-15 12:56 ` Pankaj Jangid
2021-04-15 13:52 ` Eli Zaretskii
2021-04-15 16:12 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-15 7:09 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-15 14:06 ` Pankaj Jangid
2021-04-15 16:17 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-16 8:16 ` Pankaj Jangid
2021-04-16 9:25 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-04-17 16:57 ` Pankaj Jangid
2021-04-17 17:10 ` Eli Zaretskii
2021-04-17 17:33 ` Pankaj Jangid
2021-04-17 18:49 ` Pankaj Jangid
2021-05-05 13:10 ` Lars Ingebrigtsen
2021-05-06 7:00 ` Pankaj Jangid
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=xjflf9ibmy3.fsf@sdf.org \
--to=bug-gnu-emacs@gnu.org \
--cc=47783@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=pankaj@codeisgreat.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).