From: ludo@gnu.org (Ludovic Courtès)
To: Manolis Ragkousis <manolis837@gmail.com>
Cc: Guix-devel@gnu.org, Samuel Thibault <sthibault@alioth.debian.org>,
bug-hurd@gnu.org
Subject: Re: libpthread fails to build as an add-on
Date: Sun, 23 Mar 2014 22:38:30 +0100 [thread overview]
Message-ID: <87d2hcr3xl.fsf@gnu.org> (raw)
In-Reply-To: <CAFtzXzPcDQPQo8H7wxBuXrfLkNnfEM1-R0U6C4MxgPOusmKkgw@mail.gmail.com> (Manolis Ragkousis's message of "Sun, 23 Mar 2014 09:17:36 +0000")
Manolis Ragkousis <manolis837@gmail.com> skribis:
> In the debian package I saw there are 2 patches that add this.
>
>> +libc_add_on_canonical=libpthread
>> +libc_add_on_subdirs=.
>
> How does this change the configure process?
Libc’s top-level configure file expects these two variables to be set by
the add-on’s ‘configure’ script:
--8<---------------cut here---------------start------------->8---
libc_add_on_frag=$libc_add_on_srcdir/configure
libc_add_on_canonical=
libc_add_on_config_subdirs=
if test -r "$libc_add_on_frag"; then
AC_MSG_NOTICE(running configure fragment for add-on $libc_add_on)
libc_add_on_canonical=unknown
libc_add_on_subdirs=
. "$libc_add_on_frag" ##### ← here, runs libpthread/configure
test -z "$libc_add_on" || {
configured_add_ons="$configured_add_ons $libc_add_on"
if test "x$libc_add_on_canonical" = xunknown; then
AC_MSG_ERROR(fragment must set \$libc_add_on_canonical)
fi
--8<---------------cut here---------------end--------------->8---
So when libpthread is built as an add-on, libpthread/configure must set
them, AFAIU.
HTH,
Ludo’.
next prev parent reply other threads:[~2014-03-23 21:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-18 10:02 Glibc/hurd work till now Manolis Ragkousis
2014-03-18 10:57 ` Ludovic Courtès
[not found] ` <CAFtzXzNSuz-wx2SDUafTvqtmRUbfOohO2-Nfzy7LYKd-wuWFWQ@mail.gmail.com>
2014-03-18 11:10 ` Fwd: " Manolis Ragkousis
2014-03-18 13:32 ` Ludovic Courtès
2014-03-18 14:55 ` Andreas Enge
2014-03-18 16:04 ` Ludovic Courtès
2014-03-18 19:06 ` Manolis Ragkousis
2014-03-18 20:34 ` Ludovic Courtès
2014-03-18 20:41 ` Manolis Ragkousis
2014-03-19 19:38 ` Manolis Ragkousis
2014-03-19 20:17 ` Ludovic Courtès
2014-03-19 20:47 ` Manolis Ragkousis
2014-03-19 21:58 ` Ludovic Courtès
2014-03-20 16:02 ` Manolis Ragkousis
2014-03-20 20:42 ` libpthread fails to build as an add-on Ludovic Courtès
2014-03-20 20:58 ` Manolis Ragkousis
2014-03-23 8:28 ` Manolis Ragkousis
2014-03-23 9:17 ` Manolis Ragkousis
2014-03-23 21:38 ` Ludovic Courtès [this message]
2014-03-21 23:23 ` Glibc/hurd work till now Manolis Ragkousis
2014-03-22 14:16 ` Ludovic Courtès
2014-03-22 16:13 ` 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=87d2hcr3xl.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=Guix-devel@gnu.org \
--cc=bug-hurd@gnu.org \
--cc=manolis837@gmail.com \
--cc=sthibault@alioth.debian.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 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).