On 03/20/2018 11:45 AM, Helmut Grohne wrote: > AX_CC_FOR_BUILD is precisely the thing you want here. The usual way to > use it is not to add some dependency on autoconf-archive, but to ship an > embedded copy of ax_cc_for_build.m4 in your repository and have autoconf > use that copy. I hate such copies (because they tend to be broken and > outdated quite often), but that's the way autoconf upstream wants it to > be used. > >> Anyway, his use of an unacceptable macro kind of made his actual >> diff/example useless to me. > If external macros are unacceptable, then I wonder why autoconf is > acceptable. That's the (autoconf) upstream-blessed way to use it. I'd > compare it to using Python without PyPI or Perl without CPAN.
That embedding a copy of ax_cc_for_build.m4 in one's release is considered an appropriate thing to do is quite a surprise to me. Even shocking. I don't think I have any objection to doing that if that approach is widely accepted. David Anderson [And what about libelf? Include it too because it is not available automatically to all? Where to stop embedding?] -- Don't worry about people stealing your ideas. If your ideas are any good, you'll have to ram them down people's throats. -- Howard Aiken
