From: Manolis Ragkousis <manolis837@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>,
"Samuel Thibault" <sthibault@alioth.debian.org>
Cc: Guix-devel@gnu.org, bug-hurd@gnu.org
Subject: Re: libpthread fails to build as an add-on
Date: Sun, 23 Mar 2014 08:28:23 +0000 [thread overview]
Message-ID: <CAFtzXzNGdzLj6xNf2O0JNY1xWvq5vx8Jd93pLwr1e053GRgMRA@mail.gmail.com> (raw)
In-Reply-To: <CAFtzXzMyYk+B1AJZF_Gm-VWOv3H=n=bTGurCST2opBN+GFj_XA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 605 bytes --]
As Ludovic wrote
> 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.
The part responsible for this is in the attached file and specifically the
part:
> libc_add_on_frag=$libc_add_on_srcdir/configure
I was thinking of modifying the configure script so it would use the
AC_CONFIG_SUBDIRS mechanism and configure all the addons with the flags
passed in the glibc configure.
Then I would apply the patch in a patch-phase before configure gets called
in guix.
What do you think?
Manolis
[-- Attachment #1.2: Type: text/html, Size: 793 bytes --]
[-- Attachment #2: config.txt --]
[-- Type: text/plain, Size: 3323 bytes --]
# Now source each add-on's configure fragment.
# The fragments can use $srcdir/$libc_add_on to find themselves,
# and test $add_ons_automatic to see if they were explicitly requested.
# A fragment can clear (or even change) $libc_add_on to affect
# whether it goes into the list to be actually used in the build.
use_add_ons=
for libc_add_on in $add_ons; do
# Test whether such a directory really exists.
# It can be absolute, or relative to $srcdir, or relative to the build dir.
case "$libc_add_on" in
/*)
libc_add_on_srcdir=$libc_add_on
;;
*)
test -d "$srcdir/$libc_add_on" || {
if test -d "$libc_add_on"; then
libc_add_on="`pwd`/$libc_add_on"
else
as_fn_error $? "add-on directory \"$libc_add_on\" does not exist" "$LINENO" 5
fi
}
libc_add_on_srcdir=$srcdir/$libc_add_on
;;
esac
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
{ $as_echo "$as_me:${as_lineno-$LINENO}: running configure fragment for add-on $libc_add_on" >&5
$as_echo "$as_me: running configure fragment for add-on $libc_add_on" >&6;}
libc_add_on_canonical=unknown
libc_add_on_subdirs=
. "$libc_add_on_frag"
test -z "$libc_add_on" || {
configured_add_ons="$configured_add_ons $libc_add_on"
if test "x$libc_add_on_canonical" = xunknown; then
as_fn_error $? "fragment must set \$libc_add_on_canonical" "$LINENO" 5
fi
for d in $libc_add_on_subdirs; do
case "$libc_add_on" in
/*) subdir_srcdir="$libc_add_on" ;;
*) subdir_srcdir="\$(..)$libc_add_on" ;;
esac
case "$d" in
.)
d="${libc_add_on_canonical:-$libc_add_on}"
;;
/*)
subdir_srcdir="$d"
;;
*)
subdir_srcdir="$subdir_srcdir/$d"
;;
esac
d=`echo "$d" | sed 's@/*$@@;s@^.*/@@'`
add_on_subdirs="$add_on_subdirs $d"
test "$subdir_srcdir" = "\$(..)$d" || config_vars="$config_vars
$d-srcdir = $subdir_srcdir"
done
for d in $libc_add_on_config_subdirs; do
case "$d" in
/*) as_fn_error $? "fragment uses absolute path in \$libc_add_on_config_subdirs" "$LINENO" 5 ;;
esac
if test ! -d "$libc_add_on_srcdir/$d"; then
as_fn_error $? "fragment wants to configure missing directory $d" "$LINENO" 5
fi
case "$libc_add_on" in
/*) as_fn_error $? "relative path required for add-on using \$libc_add_on_config_subdirs" "$LINENO" 5 ;;
esac
subdirs="$subdirs $libc_add_on/$d"
done
}
fi
if test -n "$libc_add_on"; then
if frags=`ls -d $libc_add_on_srcdir/sysdeps/*/preconfigure 2> /dev/null`
then
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking add-on $libc_add_on for preconfigure fragments" >&5
$as_echo_n "checking add-on $libc_add_on for preconfigure fragments... " >&6; }
for frag in $frags; do
name=`echo "$frag" | sed 's@/[^/]*$@@;s@^.*/@@'`
echo $ECHO_N "$name $ECHO_C" >&6
. "$frag"
done
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: " >&5
$as_echo "" >&6; }
fi
use_add_ons="$use_add_ons $libc_add_on"
add_ons_pfx="$add_ons_pfx $libc_add_on/"
test -z "$libc_add_on_canonical" ||
add_ons_sfx="$add_ons_sfx /$libc_add_on_canonical"
fi
done
# Use echo to strip excess whitespace.
add_ons="`echo $use_add_ons`"
fi
next prev parent reply other threads:[~2014-03-23 8:28 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 [this message]
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=CAFtzXzNGdzLj6xNf2O0JNY1xWvq5vx8Jd93pLwr1e053GRgMRA@mail.gmail.com \
--to=manolis837@gmail.com \
--cc=Guix-devel@gnu.org \
--cc=bug-hurd@gnu.org \
--cc=ludo@gnu.org \
--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).