From: Jonathan Brielmaier <jonathan.brielmaier@web.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 36811@debbugs.gnu.org, bug-guix@gnu.org
Subject: bug#36811: Guix fails to build with libgc 8.0.4
Date: Tue, 19 Nov 2019 13:09:19 +0100 [thread overview]
Message-ID: <7fa97933-fbb8-8cc1-0f6a-f67cb4436712@web.de> (raw)
In-Reply-To: <87o8x9i87h.fsf@gnu.org>
On 18.11.19 15:13, Ludovic Courtès wrote:
> To isolate the problem, how about:
>
> 1. Defining a Guix package for libgc 8.0.4;
>
> 2. Running “guix build guile --with-input=libgc@7=libgc@8” (or
> defining a package along these lines).
I did this and the build was fine as I expected. Guile builds fine
against libgc-8. But building Guix with a guile-libgc8 goes wrong.
I got now this little patch and try to build guix with:
./pre-inst-env guix build guix -K
```
diff --git a/gnu/packages/bdw-gc.scm b/gnu/packages/bdw-gc.scm
index 7196ffcd32..172833780f 100644
--- a/gnu/packages/bdw-gc.scm
+++ b/gnu/packages/bdw-gc.scm
@@ -91,6 +91,19 @@ C or C++ programs, though that is not its primary goal.")
(license (x11-style (string-append home-page "license.txt")))))
+(define-public libgc-8
+ (package
+ (inherit libgc)
+ (version "8.0.4")
+ (name "libgc")
+ (source (origin
+ (method url-fetch)
+ (uri (string-append "https://github.com/ivmai/bdwgc/releases"
+ "/download/v" version "/gc-" version
".tar.gz"))
+ (sha256
+ (base32
+ "1798rp3mcfkgs38ynkbg2p47bq59pisrc6mn0l20pb5iczf0ssj3"))))))
+
(define-public libgc/back-pointers
(package
(inherit libgc)
diff --git a/gnu/packages/guile.scm b/gnu/packages/guile.scm
index 4419c48d1a..bc69488fa2 100644
--- a/gnu/packages/guile.scm
+++ b/gnu/packages/guile.scm
@@ -250,6 +250,14 @@ without requiring the source code to be rewritten.")
(variable "GUILE_LOAD_COMPILED_PATH")
(files '("lib/guile/2.2/site-ccache")))))))
+(define-public guile-2.2-libgc8
+ (package
+ (inherit guile-2.2)
+ (propagated-inputs
+ `(("libgc" ,libgc-8)
+ ,@(srfi-1:alist-delete "bdw-gc"
+ (package-propagated-inputs guile-2.2))))))
+
(define-public guile-2.2/fixed
;; A package of Guile 2.2 that's rarely changed. It is the one used
;; in the `base' module, and thus changing it entails a full rebuild.
diff --git a/gnu/packages/package-management.scm
b/gnu/packages/package-management.scm
index 1daab4e879..d80e71749d 100644
--- a/gnu/packages/package-management.scm
+++ b/gnu/packages/package-management.scm
@@ -285,7 +285,7 @@
("sqlite" ,sqlite)
("libgcrypt" ,libgcrypt)
- ("guile" ,guile-2.2)
+ ("guile" ,guile-2.2-libgc8)
;; Some of the tests use "unshare" when it is available.
("util-linux" ,util-linux)
```
next prev parent reply other threads:[~2019-11-19 12:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 18:26 bug#36811: Guix fails to build with libgc 8.0.4 Jonathan Brielmaier
2019-11-18 14:13 ` Ludovic Courtès
2019-11-19 12:09 ` Jonathan Brielmaier [this message]
2019-11-19 13:33 ` Jonathan Brielmaier
2019-11-20 14:09 ` Ludovic Courtès
2019-11-20 14:16 ` Jonathan Brielmaier
2019-11-20 15:39 ` Ludovic Courtès
2019-11-20 16:06 ` Jonathan Brielmaier
2020-02-06 14:07 ` Ludovic Courtès
2020-02-06 14:16 ` Jonathan Brielmaier
2020-03-11 14:13 ` Ludovic Courtès
2020-03-12 10:23 ` Jonathan Brielmaier
2020-03-12 15:59 ` Ludovic Courtès
2020-03-12 16:15 ` Jonathan Brielmaier
2020-02-03 11:49 ` Jonathan Brielmaier
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7fa97933-fbb8-8cc1-0f6a-f67cb4436712@web.de \
--to=jonathan.brielmaier@web.de \
--cc=36811@debbugs.gnu.org \
--cc=bug-guix@gnu.org \
--cc=ludo@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).