From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Apoorv <apoorvs@tuta.io>
Cc: guix-devel <guix-devel@gnu.org>,
Tobias Geerinckx-Rice <me@tobias.gr>,
Ekaitz Zarraga <ekaitz@elenq.tech>
Subject: Re: Suggestion for a guix shell feature.
Date: Fri, 29 Dec 2023 22:10:11 -0500 [thread overview]
Message-ID: <87edf4s7vw.fsf@gmail.com> (raw)
In-Reply-To: <NmrVHaU--3-9@tuta.io> (Apoorv's message of "Fri, 29 Dec 2023 22:35:45 +0100 (CET)")
Hi,
Apoorv <apoorvs@tuta.io> writes:
> There are a lot of libs that need to be added to LD_LIBRARY_PATH for
> my project to compile successfully. I do have gcc-toolchain added in
> the guix.scm file. I had to do a lot of trickery for the shell
> environment to work for me properly, using direnv,
[...]
Did you try the 'guix shell --container --emulate-fhs' trick I suggested
earlier? I guess it should just work. What is it that you are
building/attempting to run?
Also, please keep guix-devel@gnu.org and participants in CC, so that
everyone can follow/participate (the easiest way to do so is to "wide
reply" from your email client).
--
Thanks,
Maxim
next parent reply other threads:[~2023-12-30 3:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <NmrVHaU--3-9@tuta.io>
2023-12-30 3:10 ` Maxim Cournoyer [this message]
2023-12-31 12:10 ` Suggestion for a guix shell feature Apoorv via Development of GNU Guix and the GNU System distribution.
2023-12-31 16:55 ` Maxim Cournoyer
2024-01-01 3:01 ` Apoorv via Development of GNU Guix and the GNU System distribution.
2024-01-02 16:33 ` Maxim Cournoyer
2024-01-03 9:14 ` Apoorv via Development of GNU Guix and the GNU System distribution.
2024-01-03 17:57 ` Maxim Cournoyer
2024-01-05 13:38 ` Apoorv via Development of GNU Guix and the GNU System distribution.
2023-12-21 16:10 Apoorv via Development of GNU Guix and the GNU System distribution.
2023-12-29 3:58 ` Maxim Cournoyer
2023-12-29 13:50 ` Ekaitz Zarraga
2023-12-29 15:39 ` Tobias Geerinckx-Rice
2023-12-29 17:21 ` Maxim Cournoyer
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87edf4s7vw.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=apoorvs@tuta.io \
--cc=ekaitz@elenq.tech \
--cc=guix-devel@gnu.org \
--cc=me@tobias.gr \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.