unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: guile-devel@gnu.org, Mike Gran <spk121@yahoo.com>
Subject: Re: Modernizing autotools and assuming C89 C library
Date: Wed, 12 Oct 2022 22:27:48 +0200	[thread overview]
Message-ID: <87mta0vlbv.fsf@gnu.org> (raw)
In-Reply-To: <YzZfc5sbXmKlTqGM@spikycactus.com> (Mike Gran's message of "Thu,  29 Sep 2022 20:16:03 -0700")

Hi Mike,

Mike Gran <spk121@yahoo.com> skribis:

> On Thu, Sep 15, 2022 at 10:20:26PM -0700, Mike Gran wrote:
>> Hello Guile Devel,
>> 
>> I pushed a git branch: wip-modernize-autotools.
>> 
>> It removes some obsolete tests by presuming we at least have a
>> C89-compliant C library. It also uses LT_INIT for libtool, and removes
>> some macros that autoconf has deprecated.

Sounds good!

> I know patches like this are unlikely to spark enthusiasm
> or review because it is autotools, but, I think presuming a C89
> C library is a safe bet.

No no, I actually find it quite exciting!  :-)

Seriously, it’s good to see old cruft vanish.  I’ve looked at the
commits on that branch and they all LGTM.

Regarding <time.h>, we’ve actually been using Gnulib’s headers, so most
likely the difference wasn’t relevant anymore.

So: LGTM!

It would be good to have some testing on OSes other than GNU/Linux
eventually (I’m looking at you, Greg ;-)).

Thanks,
Ludo’.



  reply	other threads:[~2022-10-12 20:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <YyQHmtaArxJEq9RI.ref@spikycactus.com>
2022-09-16  5:20 ` Modernizing autotools and assuming C89 C library Mike Gran
2022-09-30  3:16   ` Mike Gran
2022-10-12 20:27     ` Ludovic Courtès [this message]
2022-10-12 21:56       ` Dr. Arne Babenhauserheide

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mta0vlbv.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guile-devel@gnu.org \
    --cc=spk121@yahoo.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).