On 23 Feb 2022 01:12, Mike Frysinger wrote:
> my inclination is to introduce two new variables that would be used for
> libtool
> & non-libtool, and only when compiling.
> * xxx_COMPILE: to provide parity with existing xxx_LINK setting -- override
> the compiler on a per-program basis
> * xxx_CO
On 17 Feb 2022 16:33, Karl Berry wrote:
> Hi Damian - thanks for the report.
>
> LTCOMPILE = $(LIBTOOL) $(AM_V_lt) --tag=CC $(AM_LIBTOOLFLAGS) \
> $(LIBTOOLFLAGS) --mode=compile $(CC) $(DEFS) \
> $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) \
>
On 22 Feb 2022 16:29, Karl Berry wrote:
> The "test" item, most of the way down in the "Limitations of Shell
> Builtins" node of the Autoconf manual, reports a lot of the things that
> have led to the common forms/workarounds.
> https://www.gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf-2.
* bin/automake.in: Split dir & file name back out from the constructed
required file path.
Looks like good work to me. Thanks. -k
i have no idea what the quoting style/preference is in the GNU world,
Nothing GNU-wide, but among autotools and related packages
written/maintained by approximately the same group of people, I believe
test x"$foo" = x1
is the most-usual style. Though "x$foo" is common too,
since it makes no
I'm afraid I can't easily tell.
It looks like I added a workaround in
https://github.com/open-mpi/ompi/commit/40dd4c5b766ff62a681692b1fa6b72a1023fc81f
on Dec 20, 2014 (the same day that I initially filed this bug report).
Half of that workaround was removed in June of 2015 when we stopped embed
