From: Thorsten Wilms <t_w_@freenet.de>
To: help-guix <help-guix@gnu.org>
Subject: Re: Can't configure guix, no guile-sqlite3
Date: Thu, 2 Aug 2018 13:40:19 +0200 [thread overview]
Message-ID: <52dc709a-7b4a-4d96-9cf3-eb211bbccbe9@freenet.de> (raw)
In-Reply-To: <87o9elcke1.fsf@gmail.com>
On 02.08.2018 09:12, Chris Marusich wrote:
>> configure: error: Package requirements (sqlite3 >= 3.6.19) were not met:
>> No package 'sqlite3' found
>> ---
>
> It sounds like you're saying this error occurs when you've run "guix
> environment guix", and then you run "./configure --localstatedir=/var".
> Is that right?
Yes.
> * Run "guix pull" at least twice - without using ./pre-inst-env.
Done.
> * Start from a clean slate.
> make distclean
> git clean -dfx
> git reset --hard
> * Make sure you're using a recent Guix:
>
> git pull
Done
> * Now try to build again:
>
> ./bootstrap
> ./configure --localstatedir=/var
For the sake of completeness, without `guix environment guix`, this happens:
configure.ac:89: error: possibly undefined macro: GUILE_MODULE_AVAILABLE
With `guix environment guix` it's again:
---
checking for sqlite3 >= 3.6.19... no
configure: error: Package requirements (sqlite3 >= 3.6.19) were not met:
No package 'sqlite3' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables SQLITE3_CFLAGS
and SQLITE3_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
---
> FWIW, you might also consider trying to develop your packages by putting
> the package definitions on your own GUIX_PACKAGE_PATH (see "Package
> Modules" in the manual), rather than using ./pre-inst-env.
> GUIX_PACKAGE_PATH is the recommended way for adding custom packages,
> while ./pre-inst-env is technically an unsupported hack that is
> primarily useful for developing Guix itself.
I have to wonder about "unsupported hack". If it is one, then
https://www.gnu.org/software/guix/manual/en/html_node/Packaging-Guidelines.html#Packaging-Guidelines
needs to be altered.
In this case (a rather obscure Emacs package), it would make sense to
use GUIX_PACKAGE_PATH and perhaps not even bother sending a patch.
However, for any chance of later, more involved and worthwhile
contributions, I figured I should get the process down as described.
Especially since even my limited experience tells me any deviation
between a test run and later use introduces a risk of some silly mistake
to slip in.
Been there before, but checking again:
Within or outside of `guix environment guix`, same result:
which guix
=> /home/thorwil/.config/guix/current/bin/guix
ls -l /home/thorwil/.config/guix/current/bin/guix
=> lrwxrwxrwx 2 root root 56 Jan 1 1970
/home/thorwil/.config/guix/current/bin/guix ->
/gnu/store/aldvc43h0gyqmpl08yzpfgmcz77539sk-guix-command
stat /gnu/store/aldvc43h0gyqmpl08yzpfgmcz77539sk-guix-command
=> <snip> Change: 2018-08-02 12:05:49.134396623 +0200
Still, thanks for your detailed email, Chris!
--
Thorsten Wilms
thorwil's design for free software:
http://thorwil.wordpress.com/
next prev parent reply other threads:[~2018-08-02 11:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-17 20:24 Can't configure guix, no guile-sqlite3 Thorsten Wilms
2018-06-18 19:58 ` Ludovic Courtès
2018-06-18 20:12 ` Pierre Neidhardt
2018-06-19 10:26 ` swedebugia
2018-06-19 10:32 ` Pierre Neidhardt
2018-06-19 12:27 ` swedebugia
2018-06-19 12:32 ` Pierre Neidhardt
2018-06-20 20:41 ` How to announce important changes Ludovic Courtès
2018-06-20 22:05 ` Pierre Neidhardt
2018-06-21 0:39 ` myglc2
2018-06-21 10:52 ` Ricardo Wurmus
2018-06-19 10:33 ` Can't configure guix, no guile-sqlite3 Thorsten Wilms
2018-07-23 19:51 ` Thorsten Wilms
2018-08-02 7:12 ` Chris Marusich
2018-08-02 11:40 ` Thorsten Wilms [this message]
2018-08-02 12:18 ` Ricardo Wurmus
2018-08-02 13:21 ` Thorsten Wilms
2018-08-19 21:31 ` Maxim Cournoyer
2018-08-23 20:03 ` Thorsten Wilms
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=52dc709a-7b4a-4d96-9cf3-eb211bbccbe9@freenet.de \
--to=t_w_@freenet.de \
--cc=help-guix@gnu.org \
/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).