On 2024-03-14 06:03, Pádraig Brady wrote:
How about leaving it AC_COMPILE_IFELSE, but ensuring that -O1 or better
is used when the compiler supports -O1? That way we don't have to worry
about running the program, because (with the "volatile") clang will
error out.
Alternatively perhaps
Multicolumn options in pr imply option -i (tabification). The introduction
of tabs with physical rather than logical meaning makes output that is OK
for viewing only if you have correct tab stops, and is complicated for
further processing. It caters for obsolete equipment--typewriters, on
which
On 3/14/24 7:48 AM, Pádraig Brady wrote:
> For completeness I should add that the above check can be
> overridden if cross-compiling or whatever like:
>
> ./configure utils_cv_ieee_16_bit_supported=yes
> utils_cv_brain_16_bit_supported=yes
Ah, thanks. I wasn't aware of this.
> Interesting.
>
On Mon, 11 Mar 2024, Zachary Santer wrote:
On Mon, Mar 11, 2024 at 7:54 AM Carl Edquist
wrote:
(In my coprocess management library, I effectively run every coproc
with --output=L by default, by eval'ing the output of 'env -i stdbuf
-oL env', because most of the time for a coprocess,
On 14/03/2024 13:35, Collin Funk wrote:
On 3/14/24 6:03 AM, Pádraig Brady wrote:
It would disable this feature for cross-compilation yes,
but this isn't the first instance of AC_RUN_IFELSE we use.
For completeness I should add that the above check can be
overridden if cross-compiling or
On 3/14/24 6:03 AM, Pádraig Brady wrote:
> It would disable this feature for cross-compilation yes,
> but this isn't the first instance of AC_RUN_IFELSE we use.
Sorry if this is not the proper place to ask, but would it be possible
to make Autoconf use an emulator when cross-compiling? This issue
On 14/03/2024 05:59, Paul Eggert wrote:
On 2024-03-12 19:24, Grisha Levit wrote:
- AC_COMPILE_IFELSE(
+ AC_RUN_IFELSE(
This sort of change would break cross-compilation, no?
It would disable this feature for cross-compilation yes,
but this isn't the first instance of AC_RUN_IFELSE we use.
On 2024-03-12 19:24, Grisha Levit wrote:
- AC_COMPILE_IFELSE(
+ AC_RUN_IFELSE(
This sort of change would break cross-compilation, no?
How about leaving it AC_COMPILE_IFELSE, but ensuring that -O1 or better
is used when the compiler supports -O1? That way we don't have to worry
about running
