unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Mike Gran <spk121@yahoo.com>, guile-devel@gnu.org
Subject: Re: Modernizing autotools and assuming C89 C library
Date: Wed, 12 Oct 2022 23:56:23 +0200	[thread overview]
Message-ID: <87ilko1z4h.fsf@web.de> (raw)
In-Reply-To: <87mta0vlbv.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]


Ludovic Courtès <ludo@gnu.org> writes:

> Hi Mike,
>
> Mike Gran <spk121@yahoo.com> skribis:
>
>> On Thu, Sep 15, 2022 at 10:20:26PM -0700, Mike Gran wrote:
>>> 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.
>> 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!  :-)

Same here! I tried many different build tools over the past years, and I
was surprised to find that autotools turned out to be the best choice
when the my projects did not exactly match widespread patterns.

Autotools are one of the few tools that actually solved bootstrapping,
and improvements in autotools provide huge benefits throughout the free
software toolchain.

So please forgive my non-technical post, and thank you very much for
your work!

Best wishes,
Arne
-- 
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1125 bytes --]

      reply	other threads:[~2022-10-12 21:56 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
2022-10-12 21:56       ` Dr. Arne Babenhauserheide [this message]

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=87ilko1z4h.fsf@web.de \
    --to=arne_bab@web.de \
    --cc=guile-devel@gnu.org \
    --cc=ludo@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).