unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: Brian Woodcox <bw@inskydata.com>
Cc: help-guix@gnu.org
Subject: Re: Build failure on nss-3.36.1
Date: Sun, 4 Nov 2018 11:38:07 +0100	[thread overview]
Message-ID: <20181104113807.10cdaecd@alma-ubu> (raw)
In-Reply-To: <5E3CDDC4-C2F0-4D3A-AE45-F2F6E6793333@inskydata.com>

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

On Sat, 3 Nov 2018 21:46:02 -0600
Brian Woodcox <bw@inskydata.com> wrote:

> Hi Björn,
> 
> You nailed it.
> 
> Of course, I am not too certain how to use the guix git-checkout
> command.
> 
> Do you or anyone else have an example of how you would build this
> after downloading it?
> 
>   I’ve done a bit of search, but have not come up with much.
> 
> Thanks
> 

Hi Brian,

its described in section "7 Contributing" of the manual:

https://www.gnu.org/software/guix/manual/en/guix.html#Contributing

Please refer to the manual for full details, I will show here in short
out of my head, errors/typos might be included:

git clone https://...guix.gt

cd git

# Now you need to enter an enviromnent where guix' build tools are
# available. You could install everything yourself in a foreign distro
# or via guix package -i ..., but Guix knows it best, so just do a:

guix environment guix

# Next you need to bootstrap and build:

./bootstrap
./configure --localstatedir=/var
make

# Now search source file:
guix package -s "^nss$"
name: nss
version: 3.39
outputs: out bin
systems: x86_64-linux i686-linux armhf-linux aarch64-linux mips64el-linux
dependencies: nspr@4.20 perl@5.26.1 sqlite@3.23.0 zlib@1.2.11
location: gnu/packages/gnuzilla.scm:364:2
[..]

# edit it:

emacs gnu/packages/gnuzilla.scm

#[could also call "guix edit nss" directly]

    (arguments
     `(#:parallel-build? #f ; not supported
;; Add this line to arguments:
       #:tests? #f
       #:make-flags
;; Remove this:  (replace 'check ...)

Now run guix from source:

./pre-inst-env guix build nss

Then do whatever you want to from there:

./pre-inst-env guix install ...
./pre-inst-env guix system ...

Note: It is not enough to just build/install nss from here and then go
on with the "normal" guix: Because you changed nss, all dependencies
need to be built too.

And that is basically the world:

./pre-inst-env guix refresh -l nss

Building the following 3119 packages would ensure 8553 dependent packages are rebuilt:

So, not sure if that helps you here...

Björn


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2018-11-04 10:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-04  3:17 Build failure on nss-3.36.1 Brian Woodcox
2018-11-04  3:46 ` Brian Woodcox
2018-11-04 10:38   ` Björn Höfling [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-11-03 17:28 Brian Woodcox
2018-11-03 17:38 ` Gábor Boskovits
2018-11-03 17:47   ` Brian Woodcox
2018-11-03 19:38     ` Gábor Boskovits
2018-11-03 20:46 ` Björn Höfling

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=20181104113807.10cdaecd@alma-ubu \
    --to=bjoern.hoefling@bjoernhoefling.de \
    --cc=bw@inskydata.com \
    --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).