unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
Cc: Ricardo Wurmus <rekado@elephly.net>, help-guix@gnu.org
Subject: Re: About packaging (was: About packaging documentation)
Date: Sun, 04 Apr 2021 16:38:08 +0200	[thread overview]
Message-ID: <87y2dyuncf.fsf@nckx> (raw)
In-Reply-To: <2a22a012-f2b1-9d05-4297-44c5c0e4fd64@posteo.de>

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

Hi Zelphir,

Zelphir Kaltstahl writes:
> The guide at 
> https://guix.gnu.org/manual/en/html_node/Building-from-Git.html
> <https://guix.gnu.org/manual/en/html_node/Building-from-Git.html> 
> does not
> mention running a lone `make`.

It says, after running ./configure:

    Finally, you have to invoke 'make check' [...]

This has the effect of running make [all], and then runs the test 
suite.

Ignore it at your peril.  At most, substitute a ‘lone make’ for 
‘make check’ if you're feeling lucky and have previously run the 
test suite.

> There is an error. Perhaps I need to run it in the some kind of 
> minimalistic GNU
> Guix env as I ran the configure and bootstrap in?

Yep, *all* commands need to be run in the guix environment.  No 
need for ‘--ad-hoc make’ here as ‘make’ is already an input to 
guix.

> Trying that (warning, long log ahead):

[ 8< nom nom ]

>   HELP2MAN doc/guix-time-machine.1
>   HELP2MAN doc/guix-weather.1
>   HELP2MAN doc/guix.1
> make[2]: Leaving directory '/home/user/dev/guix'
> make[1]: Leaving directory '/home/user/dev/guix'

Success!  \o/

> So now it should be build with the package definition I added 
> known, I guess.
> Now I try running guix build again:
>
> ~~~~
> $ ./pre-inst-env guix build guile-fslib

You need to run this inside the environment as well.  You keep 
leaving it; that won't work.  It used to work sometimes, years 
ago.

Instead of tediously prefixing everything with ‘guix environment 
guix --’, just enter the environment once and stay there:

  $ guix environment guix
  $ ./bootstrap
  $ ./configure --localstatedir=/var
  $ make -j`nproc` check
  $ ./pre-inst-env guix build guile-fslib
  $ ...
  $ exit # or C-d, to leave it when finished

That's a rather standard way of doing things.  Does it work?

Kind regards,

T G-R

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

  parent reply	other threads:[~2021-04-04 14:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-15 14:46 About packaging documentation Zelphir Kaltstahl
2021-03-15 15:43 ` Ricardo Wurmus
2021-03-16 19:27   ` Zelphir Kaltstahl
2021-03-16 22:03     ` Ricardo Wurmus
2021-03-17 20:43       ` Zelphir Kaltstahl
2021-04-02 11:29       ` Zelphir Kaltstahl
2021-04-02 15:33         ` Zelphir Kaltstahl
2021-04-02 21:59           ` Ricardo Wurmus
2021-04-04 13:41             ` About packaging (was: About packaging documentation) Zelphir Kaltstahl
2021-04-04 14:35               ` Ricardo Wurmus
2021-04-04 15:57                 ` Zelphir Kaltstahl
2021-04-04 14:38               ` Tobias Geerinckx-Rice [this message]
2021-04-04 15:30                 ` Zelphir Kaltstahl
2021-04-02 21:56         ` About packaging documentation Ricardo Wurmus
2021-04-04 13:59           ` Zelphir Kaltstahl

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=87y2dyuncf.fsf@nckx \
    --to=me@tobias.gr \
    --cc=help-guix@gnu.org \
    --cc=rekado@elephly.net \
    --cc=zelphirkaltstahl@posteo.de \
    /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).