From: Andrew Whatson <whatson@gmail.com>
To: John Kehayias <john.kehayias@protonmail.com>
Cc: Tobias Geerinckx-Rice <me@tobias.gr>,
"remco@remworks.net" <remco@remworks.net>,
Liliana Marie Prikler <liliana.prikler@gmail.com>,
"55657@debbugs.gnu.org" <55657@debbugs.gnu.org>
Subject: bug#55657: libgccjit is unusable
Date: Tue, 9 Aug 2022 23:53:52 +0000 [thread overview]
Message-ID: <CAPE069dbexuxVo1axHHdp+q9-N0BxpmqD7y7KhvgVKeS92AvhQ@mail.gmail.com> (raw)
In-Reply-To: <B8CApiFvNSCTNNxMAiyApTJzI2makyG69nPaGc_TMEBQ-xJHUBwAJcqq4kp3NRXp8L_XArmz9K0lWI8IZA_DVoPF8P16sFXLYckicFxBqGA=@protonmail.com>
John Kehayias wrote:
>
> As for the original issue here, I guess the LIBRARY_PATH and ld shadowing is the workaround. I don't know if that is something that can/should be incorporated into the libgccjit package definition or should just be handled by any package using it. Currently, that will just be emacs anyway and hopefully the discussion here is useful to anyone trying to use libgccjit.
This might be possible by adding LIBRARY_PATH to native-search-paths
in the libgccjit package definition?
> Thanks again Lily and Andrew for your work here!
Thanks John & Lily for persisting with getting this submitted, I'm
very grateful for your efforts.
Cheers,
Andrew
next prev parent reply other threads:[~2022-08-09 23:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-26 13:07 bug#55657: libgccjit is unusable Liliana Marie Prikler
2022-06-04 14:07 ` Remco van 't Veer
2022-06-04 14:22 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2022-06-04 14:25 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2022-06-04 15:14 ` Liliana Marie Prikler
2022-06-28 0:53 ` John Kehayias via Bug reports for GNU Guix
2022-06-28 4:17 ` Liliana Marie Prikler
2022-06-28 5:16 ` John Kehayias via Bug reports for GNU Guix
2022-08-03 21:13 ` John Kehayias via Bug reports for GNU Guix
2022-08-04 4:26 ` Liliana Marie Prikler
2022-08-04 4:48 ` Andrew Whatson
2022-08-04 16:52 ` Liliana Marie Prikler
2022-08-05 0:59 ` Andrew Whatson
2022-08-05 18:44 ` Liliana Marie Prikler
2022-08-05 20:01 ` John Kehayias via Bug reports for GNU Guix
2022-08-05 21:31 ` Liliana Marie Prikler
2022-08-06 5:37 ` John Kehayias via Bug reports for GNU Guix
2022-08-06 5:53 ` Liliana Marie Prikler
2022-08-07 3:19 ` John Kehayias via Bug reports for GNU Guix
2022-08-07 13:59 ` Liliana Marie Prikler
2022-08-07 15:09 ` John Kehayias via Bug reports for GNU Guix
2022-08-07 15:41 ` Liliana Marie Prikler
2022-08-09 20:44 ` John Kehayias via Bug reports for GNU Guix
2022-08-09 23:53 ` Andrew Whatson [this message]
2022-08-09 18:37 ` bug#55657: [PATCH 0/6] Add native compilation to Emacs Liliana Marie Prikler
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPE069dbexuxVo1axHHdp+q9-N0BxpmqD7y7KhvgVKeS92AvhQ@mail.gmail.com \
--to=whatson@gmail.com \
--cc=55657@debbugs.gnu.org \
--cc=john.kehayias@protonmail.com \
--cc=liliana.prikler@gmail.com \
--cc=me@tobias.gr \
--cc=remco@remworks.net \
/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/guix.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).