unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: 宋文武 <iyzsong@envs.net>
To: Mohamed Amine LEGHERABA <mlegheraba@protonmail.com>
Cc: Ricardo Wurmus <rekado@elephly.net>,  help-guix@gnu.org
Subject: Re: no C_INCLUDE_PATH env variable defined : I can't compile C applications
Date: Mon, 24 Oct 2022 14:57:57 +0800	[thread overview]
Message-ID: <87h6ztr9my.fsf@envs.net> (raw)
In-Reply-To: <apDOjkbNHYOBfEqTFq0BFu4fwa15ZLNebYBePdAm2eXmArhCavM854Ynr1caLAyF9L2D-qQGuK-gEi_0a_vgEa_KMJaZZx7klR3xuWNs1GU=@protonmail.com> (Mohamed Amine LEGHERABA's message of "Mon, 24 Oct 2022 01:42:20 +0000")

Mohamed Amine LEGHERABA <mlegheraba@protonmail.com> writes:

> Thanks Ricardo for your answer.
>
> Sorry if my message was not clear,
> I don't have the env variable C_INCLUDE_PATH in my guix system and I
> should have it because I have the packages "gcc-toolchain" and
> "linux-libre-headers" in my home profile.
> When I run a instance of guix shell with these 2 packages, for example
> with the command "guix shell gcc-toolchain linux-libre-headers" I do
> have this env variable defined (in fact a guix shell with only
> gcc-toolchain works also) so I don't know why I don't have this
> variable defined in my system.

Hello, I think you're missing 'home-bash-service-type' in your home
services, which should setup bash to source
'$HOME_ENVIRONMENT/setup-environment', and 'setup-environment' will
source '.guix-home/profile/etc/profile'.  If gcc-toolchain is in the
home profile, that '.guix-home/profile/etc/profile' should have
C_INCLUDE_PATH in it.

Hope this helps!


  reply	other threads:[~2022-10-24  7:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-22 11:07 no C_INCLUDE_PATH env variable defined : I can't compile C applications Mohamed Amine LEGHERABA via
2022-10-23 21:48 ` Ricardo Wurmus
2022-10-24  1:42   ` Re : " Mohamed Amine LEGHERABA
2022-10-24  6:57     ` 宋文武 [this message]
2022-10-24  8:17       ` Efraim Flashner
2022-10-29 12:24         ` Re : " Mohamed Amine LEGHERABA

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=87h6ztr9my.fsf@envs.net \
    --to=iyzsong@envs.net \
    --cc=help-guix@gnu.org \
    --cc=mlegheraba@protonmail.com \
    --cc=rekado@elephly.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. 
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).