From: Joerg Vehlow <lkml@jv-coder.de>
To: rpalethorpe@suse.de
Cc: ltp@lists.linux.it, Joerg Vehlow <joerg.vehlow@aox.de>
Subject: Re: [LTP] [PATCH 2/3] openposix: Setup autoconf and fix installation layout
Date: Tue, 5 Jul 2022 08:43:26 +0200 [thread overview]
Message-ID: <ff33060e-07d1-a552-caa2-dda8188f2131@jv-coder.de> (raw)
In-Reply-To: <87czekrseu.fsf@suse.de>
Hi,
Am 7/5/2022 um 7:57 AM schrieb Richard Palethorpe:
> Hello Joerg,
>
> Joerg Vehlow <lkml@jv-coder.de> writes:
>> +AC_PROG_CC_C99
>
> This causes a deprecation warning for me
I think autoconf developers messed up here. They obsoleted the macro in
2.70 and told users to replace it with just AC_PROG_CC, which defaults
to C11, but also excepts C89. It is not possible (without adding more
code), to verify if the required C version is available. What is even
worse, that autoconf does not fallback to a version, where this was
still not obsolete, even if an older autoconf version is defined in
AC_PREREQ.
Nevertheless, I guess in case of C99, we can just switch to AC_PROG_CC,
because every compiler should support C99 nowadays. I just wanted to be
explicit, because C99 us currenty selected in the CFLAGS file, that I
dropped.
Joerg
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-07-05 6:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 12:53 [LTP] [0/3] openposix: Fix installation file layout Joerg Vehlow
2022-06-27 12:53 ` [LTP] [PATCH 1/3] openposix: Fix existence test for local flag-files Joerg Vehlow
2022-06-27 12:53 ` [LTP] [PATCH 2/3] openposix: Setup autoconf and fix installation layout Joerg Vehlow
2022-07-05 5:57 ` Richard Palethorpe
2022-07-05 6:28 ` Richard Palethorpe
2022-07-05 6:37 ` Joerg Vehlow
2022-07-05 7:37 ` Richard Palethorpe
2022-07-27 5:42 ` Joerg Vehlow
2022-07-05 6:43 ` Joerg Vehlow [this message]
2022-07-27 5:26 ` Joerg Vehlow
2022-06-27 12:53 ` [LTP] [PATCH 3/3] configure: Integrate open posix testsuite configure Joerg Vehlow
2022-07-05 6:22 ` Richard Palethorpe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ff33060e-07d1-a552-caa2-dda8188f2131@jv-coder.de \
--to=lkml@jv-coder.de \
--cc=joerg.vehlow@aox.de \
--cc=ltp@lists.linux.it \
--cc=rpalethorpe@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.