From: ludo@gnu.org (Ludovic Courtès)
To: Manolis Ragkousis <manolis837@gmail.com>
Cc: Guix-devel@gnu.org, bug-hurd@gnu.org
Subject: libpthread fails to build as an add-on
Date: Thu, 20 Mar 2014 21:42:33 +0100 [thread overview]
Message-ID: <87y504wqiu.fsf_-_@gnu.org> (raw)
In-Reply-To: <CAFtzXzPLmEm0rAPoLfS-p8xWFvU20R5vRuV6onxhuDABoCwt=A@mail.gmail.com> (Manolis Ragkousis's message of "Thu, 20 Mar 2014 16:02:22 +0000")
(Hurd people: this is about a configure error when cross-compiling glibc
with libpthread as an add-on.)
Manolis Ragkousis <manolis837@gmail.com> skribis:
> when building glibc with libpthread as an addon I get this
>
> configure: running configure fragment for add-on libpthread
> configure: WARNING: you should use --build, --host, --target
> configure: WARNING: you should use --build, --host, --target
> checking build system type... Invalid configuration `dummy': machine
> `dummy' not recognized
> configure: error:
> /gnu/store/281n6ma5jxy9sb3nwc09mzpqx43vczr6-bash-4.2/bin/bash
> ../source/scripts/config.sub dummy failed
>
> Normally the flags passed to glibc's configure should be passed to
> libpthread as well. Why isn't it happening?
Actually libc’s configure doesn’t use the normal AC_CONFIG_SUBDIRS
mechanism, and instead runs add-on configure scripts by itself, without
arguments AFAICS.
[...]
> It was created by GNU C Library configure (see version.h), which was
> generated by GNU Autoconf 2.68. Invocation command line was
>
> $ ../source/configure dummy readelf
(This is libpthread’s config.log, right?)
I don’t understand where those arguments come from.
Ideas?
Thanks,
Ludo’.
next prev parent reply other threads:[~2014-03-20 20:42 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 ` Ludovic Courtès [this message]
2014-03-20 20:58 ` libpthread fails to build as an add-on Manolis Ragkousis
2014-03-23 8:28 ` Manolis Ragkousis
2014-03-23 9:17 ` Manolis Ragkousis
2014-03-23 21:38 ` Ludovic Courtès
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=87y504wqiu.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=Guix-devel@gnu.org \
--cc=bug-hurd@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).