This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: Problem recursing configure into add-on's stand alone sub-project.
On Tue, Sep 15, 2009 at 4:36 PM, Roland McGrath <roland@redhat.com> wrote:
> You do not need or want to set libc_add_on_canonical nonempty unless you
> want to match sysdeps/.../foo subdirectories in other add-ons. ÂThat's all
> it's really for. ÂIt will also set the build subdirectory name if you use
> . in libc_add_on_subdirs, but that will just default to `basename $add_on`
> and that will be fine. ÂYou do need to set it to empty if nothing else,
> just to keep configure from barfing on you.
Hi Roland,
This works great. Thanks!
foo/configure.in
GLIBC_PROVIDES
libc_add_on_canonical=
libc_add_on_config_subdirs=bar
> Another general note about add-on configure fragments: you don't need to
> write it as configure.in if you don't use any autoconf macros. ÂYou can
> just write configure directly (like nptl/configure) if you prefer.
I'll probably go without configure.in.
Ryan S. Arnold