all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: John Darrington <jmd@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 2/3] gnu: boost: New module
Date: Mon, 03 Feb 2014 22:18:37 +0100	[thread overview]
Message-ID: <87ha8fopxu.fsf@gnu.org> (raw)
In-Reply-To: <1391336858-4846-2-git-send-email-jmd@gnu.org> (John Darrington's message of "Sun, 2 Feb 2014 11:27:37 +0100")

Hi!

Thanks for looking into those big packages!

John Darrington <jmd@gnu.org> skribis:

> +       (alist-replace
> +        'configure 
> +        (lambda* (#:key outputs #:allow-other-keys) 
> +          (let ((out (assoc-ref outputs "out")))
> +            (substitute* '("libs/config/configure"
> +                           "libs/spirit/classic/phoenix/test/runtest.sh"
> +                           "tools/build/v2/doc/bjam.qbk"
> +                           "tools/build/v2/engine/boehm_gc/aclocal.m4"
> +                           "tools/build/v2/engine/boehm_gc/config.guess"
> +                           "tools/build/v2/engine/boehm_gc/configure"
> +                           "tools/build/v2/engine/boehm_gc/configure.ac"
> +                           "tools/build/v2/engine/boehm_gc/install-sh"
> +                           "tools/build/v2/engine/boehm_gc/libtool.m4"
> +                           "tools/build/v2/engine/boehm_gc/ltmain.sh"
> +                           "tools/build/v2/engine/boehm_gc/Makefile.direct"
> +                           "tools/build/v2/engine/boehm_gc/Makefile.dj"
> +                           "tools/build/v2/engine/boehm_gc/missing"
> +                           "tools/build/v2/engine/boehm_gc/PCR-Makefile"
> +                           "tools/build/v2/engine/execunix.c"
> +                           "tools/build/v2/engine/Jambase"
> +                           "tools/build/v2/engine/jambase.c")
> +              (("/bin/sh") (which "sh")))

Boehm GC doesn’t need patching, because it uses an Autoconf-generated
‘configure’, so it honors $SHELL and $CONFIG_SHELL.  Could you try
(setenv "CONFIG_SHELL" (which "sh"))?

Even better: can Boost be told to use our libgc instead of building its
own?

As for the other scripts, why do they need to be patched?  Normally the
patch-shebang phase should have taken care of the shebang of
‘libs/config/configure’, ‘runtest.sh’, etc.

> +            (setenv "SHELL" (which "sh"))
> +            
> +            (zero? (system* "./bootstrap.sh" 
> +                            (string-append "--prefix=" out) 
> +                            "--with-toolset=gcc"))))
> +        (alist-replace
> +         'build
> +         (lambda* (#:key outputs #:allow-other-keys #:rest args) 
> +           (zero? (system* "./b2" "threading=multi" "link=shared")))

Since both ‘outputs’ and ‘args’ are ignored, just write:

  (lambda _
    (zero? ...))

(where ‘_’ is by convention a placeholder.)

> +         (alist-replace
> +          'check
> +          (lambda* (#:key outputs #:allow-other-keys #:rest args) #t)

Just use #:tests? #f instead of replacing the ‘check’ phase.

> +    (synopsis "peer-reviewed portable C++ source libraries")

Capitalization.

> +    (description  "A collection of libraries intended to be widely useful, and usable across
> +    a broad spectrum of applications.")

Extra spaces, line too long.

Thanks,
Ludo’.

  reply	other threads:[~2014-02-03 21:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-02 10:27 [PATCH 1/3] gnu: gtkmm-2 New variable John Darrington
2014-02-02 10:27 ` [PATCH 2/3] gnu: boost: New module John Darrington
2014-02-03 21:18   ` Ludovic Courtès [this message]
2014-02-02 10:27 ` [PATCH 3/3] gnu: inkscape: " John Darrington
2014-02-03 21:20   ` Ludovic Courtès
2014-02-04  7:54     ` John Darrington
2014-02-04  8:08       ` Ludovic Courtès

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ha8fopxu.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=jmd@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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.