Problem recursing configure into add-on's stand alone sub-project.

Ryan Arnold
Fri Sep 18 04:10:00 GMT 2009

On Tue, Sep 15, 2009 at 4:36 PM, Roland McGrath <> 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!




> Another general note about add-on configure fragments: you don't need to
> write it as 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

Ryan S. Arnold

More information about the Libc-help mailing list