unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: mbcladwell@stihie.net
To: Julien Lepiller <julien@lepiller.eu>
Cc: help-guix@gnu.org
Subject: Re: No Guile development packages were found.
Date: Mon, 27 Jul 2020 13:58:07 -0500	[thread overview]
Message-ID: <20200727135807.Horde.qzMO1hZdiGwWVFB8QMq3A0L@www.stihie.net> (raw)
In-Reply-To: <20200727154826.06c55fa2@tachikoma.lepiller.eu>


Quoting Julien Lepiller <julien@lepiller.eu>:

> Hi,
>
> Le Mon, 27 Jul 2020 06:52:52 -0500,
> mbcladwell@stihie.net a écrit :
>
>> Hi,
>> I would like to upgrade guile-json in my local store.
>> I start with
>> $guix pull
>> $guix package -u  (didn't do anything)
>
> If guile-json is not installed in your default profile, that's
> expected. Otherwise, maybe it was your first guix pull? Make sure you
> have ~/.config/guix/current/bin *first* in your $PATH and run "hash
> guix" to invalidate your shell's cache for the guix binary location.
>
> Make sure "type guix" returns ~/.config/guix/current/bin/guix.
>
>>
>> Modifying the template at
>> https://guix.gnu.org/blog/2018/a-packaging-tutorial-for-guix/
>> I create the file guile-json.scm:
>>
>> [...]
>>
>> Looking at the log file, the final lines are:
>>
>> checking for pkg-config... no
>> configure: checking for guile 3.0
>> configure: checking for guile 2.2
>> configure: checking for guile 2.0
>> configure: error:
>> No Guile development packages were found.
>>
>> Please verify that you have Guile installed.  If you installed Guile
>> from a binary distribution, please verify that you have also installed
>> the development packages.  If you installed it yourself, you might
>> need to adjust your PKG_CONFIG_PATH; see the pkg-config man page for
>> more.
>>
>> command
>> "/gnu/store/29jhbbg1hf557x8j53f9sxd9imlmf02a-bash-minimal-5.0.7/bin/bash"
>> "./configure" "CONFIG_SHELL=/gnu/store/29jhbbg1hf55$
>>
>>
>> I am on Debian 9 working with guile v 2.2.7, dev files are installed:
>>
>> apt-get install guile-2.0-dev
>> Reading package lists... Done
>> Building dependency tree
>> Reading state information... Done
>> guile-2.0-dev is already the newest version (2.0.13+1-4).
>
> Guix does not interact with your system, and ensures that it does not
> use anything from it when building. Otherwise, the resulting package's
> content might depend on the content of the system that built it, and we
> wouldn't be able to ensure reproducibility across all the linux
> distributions.
>
> Instead, Guix builds packages in its own container system, completely
> isolated from the system, your environment variables, etc... In order
> to ensure guile is present in this container, you must declare it as a
> dependency (we call that an "input"). You'll also need pkg-config, so
> the package definition would look like this:
>
> (package
>   (name "guile-json")
>   ...
>   (build-system gnu-build-system)
>   (native-inputs
>    `(("pkg-config" ,pkg-config)))
>   (inputs
>    `(("guile" guile-3.0)))
>   ...
>   (license gpl3+))
>
> With the necessary imports at the beginning of the file. You can have a
> look at the actual definition we use in Guix with:
>
> guix edit guile-json
>
> Another possibility, as guile-json is available in Guix (we have 1.2.0,
> 3.5.0 and 4.0.1 currently) is to use the available recipe for guile-json
> but with a different source, like this:
>
> guix install guile-json@3.5.0 --with-source=https://...
>
> Not tested and if something changed in the build instructions, it might
> break, but it's certainly easier than creating your own definition from
> scratch. I specify the version since it's the closest to the version
> you want (in fact the recipe has not changed for guile-json 4, which
> would be the one used if you don't specify a version).
>
> Note that you'll need guile itself in your profile too in order for
> guile-json to be useful.
>
>>
>> In my .bashrc I set the variable such that at the terminal prompt:
>>
>> echo $PKG_CONFIG_PATH
>> /home/mbc/.guix-profile/lib/pkgconfig
>>
>> Where did I go wrong?
>
> As said above, guix just doesn't care about your environment :)
>
>> Thanks
>> Mortimer
>>
I need guile-json >= 4.2 because 4.2 provides guile-json-mapping

I modified PATH:

mbc@xps:~$ echo $PATH
/opt/gradle/gradle-4.8.1/bin:/home/mbc/bin:/gnu/profiles/base/bin:/usr/share/lintian/overrides:/usr/local/bin/guile:/home/mbc/.guix-profile/bin:/home/mbc/.nvm/versions/node/v12.16.3/bin:/usr/local/bin:/usr/bin:/bin:
mbc@xps:~$ export PATH=/home/mbc/.config/guix/current/bin/guix:$PATH
mbc@xps:~$ echo $PATH
/home/mbc/.config/guix/current/bin/guix:/opt/gradle/gradle-4.8.1/bin:/home/mbc/bin:/gnu/profiles/base/bin:/usr/share/lintian/overrides:/usr/local/bin/guile:/home/mbc/.guix-profile/bin:/home/mbc/.nvm/versions/node/v12.16.3/bin:/usr/local/bin:/usr/bin:/bin:


/home/mbc/.config/guix/current/bin/guix is first but:

mbc@xps:~$ hash guix
mbc@xps:~$ type guix
guix is hashed (/usr/local/bin/guix)
mbc@xps:~$

Thanks
Mortimer




  reply	other threads:[~2020-07-27 18:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-27 11:52 No Guile development packages were found mbcladwell
2020-07-27 13:37 ` Efraim Flashner
2020-07-27 18:29   ` mbcladwell
2020-07-27 20:25     ` Julien Lepiller
2020-07-28  8:50       ` mbcladwell
2020-07-28 19:25       ` mbcladwell
2020-07-27 13:48 ` Julien Lepiller
2020-07-27 18:58   ` mbcladwell [this message]
2020-07-27 20:21     ` Julien Lepiller

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=20200727135807.Horde.qzMO1hZdiGwWVFB8QMq3A0L@www.stihie.net \
    --to=mbcladwell@stihie.net \
    --cc=help-guix@gnu.org \
    --cc=julien@lepiller.eu \
    /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).