From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf1-f43.google.com (mail-lf1-f43.google.com [209.85.167.43]) by sourceware.org (Postfix) with ESMTPS id 623DC385780A for ; Fri, 21 Jan 2022 15:37:14 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 623DC385780A Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=rtems.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=gmail.com Received: by mail-lf1-f43.google.com with SMTP id b14so34713510lff.3 for ; Fri, 21 Jan 2022 07:37:14 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:reply-to :from:date:message-id:subject:to:cc; bh=CDNboPoOmj1RvWthhpVFGJkibkhXjNcjRb7znogzyfg=; b=S+aGaSXItWnlMv+Jc0GDRfMiYadPHHi3skrTZPZSLqRu0qBU2vg7lUNCZrnAvLRTPs Ma2e00kpgyO3m5OGS5z6NmjsfyIIidtoQyzkzOY0zhOH9ln0hw4RXaLDdBvLotWdQcX/ wVLLuPyZbMqTdC/9YgZPt69V8BPZAyicZ5V14GJ+ZyrFJkyOh5/dzMbR4UjNsCPIjRAa MDT1HfL7kaUXduYZIIPN36c9PjSmh7FZXxxsv4GQmeq4V8pHyKXmxKg0FTOYQ1hEe0Pz Fd/DVytNrXJ7er58roTo3bEXwux9D3kTvrzVvK4OhAkLFFR7NB04NunnXiIQLrrcqkQ+ twIQ== X-Gm-Message-State: AOAM531TxR1ZdynB9tpL+qCai5tMymGxOutzQs7ve+nnqtEeI/sbryv1 NUSM2ZKRhVvPDVA057nAKujyNweUp1aN7g== X-Google-Smtp-Source: ABdhPJw2Zcykjq3/alxIsy6E1wYG/X2StZTHFG5rC73+RqBhIAL02+8gDwmpPWRmhSzMKsmay4bhWw== X-Received: by 2002:a19:4401:: with SMTP id r1mr3925926lfa.351.1642779432536; Fri, 21 Jan 2022 07:37:12 -0800 (PST) Received: from mail-lf1-f49.google.com (mail-lf1-f49.google.com. [209.85.167.49]) by smtp.gmail.com with ESMTPSA id j6sm285170lfg.304.2022.01.21.07.37.12 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 21 Jan 2022 07:37:12 -0800 (PST) Received: by mail-lf1-f49.google.com with SMTP id y15so26383879lfa.9 for ; Fri, 21 Jan 2022 07:37:12 -0800 (PST) X-Received: by 2002:a05:6512:2215:: with SMTP id h21mr4086413lfu.470.1642779432107; Fri, 21 Jan 2022 07:37:12 -0800 (PST) MIME-Version: 1.0 References: <26fff1a3-7743-e0ce-f7a6-70b39a030118@embedded-brains.de> In-Reply-To: Reply-To: joel@rtems.org From: Joel Sherrill Date: Fri, 21 Jan 2022 09:37:00 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Question about autoreconf to regenerate configuration files To: "R. Diez" Cc: Matthew Joyce , Newlib Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-3031.6 required=5.0 tests=BAYES_00, FREEMAIL_FORGED_FROMDOMAIN, FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS, KAM_DMARC_STATUS, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: newlib@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Newlib mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2022 15:37:16 -0000 On Fri, Jan 21, 2022 at 9:03 AM R. Diez via Newlib wrote: > > > > [...] > > but I have also unwittingly modified well over 100 files (numerous Makefile.in, aclocal.m4, and configure files). > > I'd like to understand: Is this expected or desirable? Should I not be using autoreconf for this? > > This is another drawback of checking into the repository the files generated by the Autotools, see this e-mail: > > require autoconf-2.69 exactly > Wed Jan 12 20:01:01 GMT 2022 > https://sourceware.org/pipermail/newlib/2022/018866.html > > See also the answer from Mike Frysinger about this problem: > > require autoconf-2.69 exactly > Wed Jan 12 21:37:22 GMT 2022 > https://sourceware.org/pipermail/newlib/2022/018867.html Over at RTEMS when we used autotools, we didn't commit most of the output. Our tools included the preferred autoconf/automake versions. We did put the generated acinclude.m4 for the list of BSPs in git. But even on that, we had issues because the order of BSPs would vary depending on which host generated it. Ultimately, we eliminated that file. The bootstrap time after checkout was quite large compared to the actual compilation time. The bootstrap time was large enough to negatively impact our ability to do automated regression testing. We have switched away from autotools. One of our long standing concerns with letting users generate was reproducibility. How do you know that two end users end up with the same generated output? It's a pain to put the generated output in git but at least it saves generating it and ensures it is the same for all users building. All solutions in this area seem to suck. It is only a matter of degree. --joel > Regards, > rdiez