From: ludo@gnu.org (Ludovic Courtès)
To: manolis837@gmail.com
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: glibc-hurd: Force mach/hurd/libpthread subdirs to build first.
Date: Mon, 14 Nov 2016 14:05:05 +0100 [thread overview]
Message-ID: <87r36e8b5q.fsf@gnu.org> (raw)
In-Reply-To: <20161113131946.4185-2-manolis837@gmail.com> (manolis's message of "Sun, 13 Nov 2016 15:19:46 +0200")
manolis837@gmail.com skribis:
> From: Manolis Ragkousis <manolis837@gmail.com>
>
> * gnu/packages/base.scm (glibc/hurd): Avoid linking errors by forcing
> mach/hurd/libpthread glibc subdirs to build before anything else.
Rather:
* gnu/packages/base.scm (glibc/hurd)[arguments]: Replace 'build' phase.
The comment in there is what explains the details.
> + (alist-replace
> + 'build
> + (lambda _
> + ;; Force mach/hurd/libpthread subdirs to build first in order to avoid
> + ;; linking errors.
If there’s a link to a bug-hurd discussion, you can add it here, in case
someone wants to see the details at a later point in time.
> + (zero?
> + (and (system* "make" "mach/subdir_lib")
> + (system* "make" "hurd/subdir_lib")
> + (system* "make" "libpthread/subdir_lib")
> + (system* "make"))))
The ‘zero?’ call is misplaced.
Also, I’d suggest enabling parallel builds, so something like this:
(let ((-j (list "-j" (number->string (parallel-job-count)))))
(let-syntax ((make (syntax-rules ()
((_ target)
(zero? (apply system* "make" target -j))))))
(and (make "mach/subdir_lib")
(make "hurd/subdir_lib")
(make "libpthread/subdir_lib")
(zero? (apply system* "make" -j)))))
OK with changes along these lines.
Thank you!
Ludo’.
next prev parent reply other threads:[~2016-11-14 13:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-13 13:19 [PATCH] gnu: glibc-hurd: Force mach/hurd/libpthread subdirs to build manolis837
2016-11-13 13:19 ` [PATCH] gnu: glibc-hurd: Force mach/hurd/libpthread subdirs to build first manolis837
2016-11-14 13:05 ` Ludovic Courtès [this message]
2016-11-30 13:21 ` Manolis Ragkousis
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=87r36e8b5q.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=manolis837@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).