unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: mbcladwell@stihie.net
Cc: help-guix@gnu.org
Subject: Re: No Guile development packages were found.
Date: Mon, 27 Jul 2020 16:37:36 +0300	[thread overview]
Message-ID: <20200727133736.GG9269@E5400> (raw)
In-Reply-To: <20200727065252.Horde.zwuqgyOS38xl3-x-35QYgsn@www.stihie.net>

[-- Attachment #1: Type: text/plain, Size: 4396 bytes --]

On Mon, Jul 27, 2020 at 06:52:52AM -0500, mbcladwell@stihie.net wrote:
> 
> Hi,
> I would like to upgrade guile-json in my local store.
> I start with
> $guix pull
> $guix package -u  (didn't do anything)
> 
> Modifying the template at
> https://guix.gnu.org/blog/2018/a-packaging-tutorial-for-guix/
> I create the file guile-json.scm:
> 
> (use-modules (guix packages)
>              (guix download)
>              (guix build-system gnu)
>              (guix licenses))
> 
> (package
>   (name "guile-json")
>   (version "4.3.2")
>   (source (origin
>             (method url-fetch)
>             (uri (string-append
> "https://download.savannah.gnu.org/releases/guile-json/guile-json-" version
> ".tar.gz"))
>             (sha256
>              (base32
>               "0255c7f053z4p9mqzhpxwbfx3y47j9nfvlgnm8xasdclyzmjl9y2"))))
>   (build-system gnu-build-system)
>   (synopsis "Hello, Guix world: An example custom Guix package")
>   (description
>    "GNU Hello prints the message \"Hello, world!\" and then exits.  It
> serves as an example of standard GNU coding practices.  As such, it supports
> command-line arguments, multiple languages, and so on.")
>   (home-page "https://www.gnu.org/software/hello/")
>   (license gpl3+))
> 
> 
> Then I run:
> 
> $guix package --install-from-file=./Downloads/guile-json/guile-json.scm
> guix package: warning: Consider running 'guix pull' followed by
> 'guix package -u' to get up-to-date packages and security updates.
> 
> The following package will be upgraded:
>    guile-json 3.2.0 → 4.3.2
> 
> The following derivations will be built:
>    /gnu/store/advvlsn24m0jc84ivqsfrd9y9bicfsan-profile.drv
>    /gnu/store/w58xzy3xz0xf4ljr84k9q35kyriapvq6-guile-json-4.3.2.drv
> The following profile hooks will be built:
>    /gnu/store/3z61qjph0ww2bizg904vmqn6p5cwgcyq-fonts-dir.drv
>    /gnu/store/9nnjb0y55hb5ai9ss3zrljyx6npxqjip-ca-certificate-bundle.drv
>    /gnu/store/jmris7xjszh69gci0mpxw76isrirb9dk-info-dir.drv
>    /gnu/store/yyp1p3mpsz5azfl59sdlncr0zcscj6qx-manual-database.drv
> building /gnu/store/w58xzy3xz0xf4ljr84k9q35kyriapvq6-guile-json-4.3.2.drv...
> | 'configure' phasebuilder for
> `/gnu/store/w58xzy3xz0xf4ljr84k9q35kyriapvq6-guile-json-4.3.2.drv' failed
> with exit code 1
> build of /gnu/store/w58xzy3xz0xf4ljr84k9q35kyriapvq6-guile-json-4.3.2.drv
> failed
> View build log at '/var/log/guix/drvs/w5/8xzy3xz0xf4ljr84k9q35kyriapvq6-guile-json-4.3.2.drv.bz2'.
> cannot build derivation
> `/gnu/store/advvlsn24m0jc84ivqsfrd9y9bicfsan-profile.drv': 1 dependencies
> couldn't be built
> guix package: error: build of
> `/gnu/store/advvlsn24m0jc84ivqsfrd9y9bicfsan-profile.drv' failed
> 
> 
> 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).
> 
> 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?
> Thanks
> Mortimer

Builds occur in a chrooted environment, so only the packages added in
the package definition are there. Try adding

(inputs
 `(("guile" ,guile)))

to the package definition after the build-system line. and (gnu packages
guile) to the top with the other use-modules.

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-07-27 13:38 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 [this message]
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
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=20200727133736.GG9269@E5400 \
    --to=efraim@flashner.co.il \
    --cc=help-guix@gnu.org \
    --cc=mbcladwell@stihie.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).