From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ej1-x62e.google.com (mail-ej1-x62e.google.com [IPv6:2a00:1450:4864:20::62e]) by sourceware.org (Postfix) with ESMTPS id 94CBE3858C52 for ; Thu, 29 Feb 2024 10:22:39 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 94CBE3858C52 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=linaro.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=linaro.org ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 94CBE3858C52 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=2a00:1450:4864:20::62e ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1709202163; cv=none; b=vxGGijVKdqy2++vGP+3JOJbha6n6V2gn4jxq1rqyu9t7ucQTwbGVsXT9qSYiTGYsiMpi6yhdQVsARZs2zHbMZhF1oabShVnZ11m+XjRuUw1FhaI34t2ZYIN5/5o45KMce2X9IVh470d80+aTCn1aHS3Ps9dmTOgGtsZbf7s9e7c= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1709202163; c=relaxed/simple; bh=Knvs2IjSb308niJZmpk/oYPPjGYdtIeb679kO1ORqP0=; h=DKIM-Signature:MIME-Version:From:Date:Message-ID:Subject:To; b=Y3OPSkv+r91Fz3AXNl80foCRrYvsGu5YN+adK3u53neuEwuKt/rkn/Xq3XyuKgHMN1jVxF3zrjLXRvfnmRJNgHiFmBiRcTytdazgrWzeUtHwDyzL1/CQMYhbAUl4eskAMdNAHKJb6ns1auxuxU6iImeknBCBtjtjMwrIWLDAeqk= ARC-Authentication-Results: i=1; server2.sourceware.org Received: by mail-ej1-x62e.google.com with SMTP id a640c23a62f3a-a3e550ef31cso98072166b.3 for ; Thu, 29 Feb 2024 02:22:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1709202158; x=1709806958; darn=gcc.gnu.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=RZJPFZmauZiPY79/AHOdllMrenn9dUK5tOmt2pCtKjU=; b=Cro/5ML4jrZ9HmGeDd0S9RFjH4a4u2pUO2IRn4KKr3aUjRQM01zOitNjxPDeE/I82S j51KFtl9Cx09a0y/GT4gStHrPA7M0WY0RqBGb5MHXiKzwAHgmIdaQveB6/T7Gyl5o2Ac t7Eyc7HopQKS061lzu3grSLSzxA6zIQDVIa7AzjHuGaqOT2y1ORTB1tyY9cWxhzrkA8j nV0ZrDKQccuK8xvbQFSBAPw2rnUMxAsT4mpV41/JTaNYoPMt8BWU230I9ZolVZZzcTNk MmPHbTHqU1l6jBUUfJZCyUZCFM/bwapwuYZWhT/bqL8nU2Dq0+xN7aBf1bp97zbell4j urEg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1709202158; x=1709806958; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=RZJPFZmauZiPY79/AHOdllMrenn9dUK5tOmt2pCtKjU=; b=xVldXuMHw1QJJ3VkLs/Mut0CH2Zj3UO/KpXOfEDm57AS6RyOSG/JJzd1u/va5RHfl2 ylGv+Vsq20vj3h0HZ9I0JD3K9ri+PYXGxeC6DQojzEN1AyoqwE8wyJLLgIAmPfPUZsn3 z8uhJulT+CFvLGq27LUi3PPYQxAOgWD6/YfrlZp9w7RapKYdHLl8BXOompPcgoM+NMd0 6JdAjLZouAJz4lCJ+Jjulha7YjVr6GhXAtwqnwRzMKKDr8DJq+tyAjCI5pay5GlaHAVr +I8cAVbq9qm07sllX/Vk6mPzkITg4/Uz8qR8WXHPxNme6XSVxYO+uEnj7OHwxtU7l27f KZqQ== X-Forwarded-Encrypted: i=1; AJvYcCWcuddBAPGcGlHJK7bYzm6mdKPo4V7DDCUylAhaJn0VoWyfPDVrCBHWs0OmQAEJQ1E0bEYxj69wJpHVMYR2W1o= X-Gm-Message-State: AOJu0YwCpO3tdLAik8hCtqSF2Vnk/QWeZntgTTeCf6nzNs4bwQ/sFpck 6Ca4FusvgxsHfzya6JIP18MMvQAKaI/DvwtXOe5d7+OXQehVnPlJ7HQ5qXNFx7CqdyP9si/ImD/ g5/qOnxAEbMMVEhaBl2XFTHlZRVvaVJ4rf/bbphP1DAzhh4CjW/R3cA== X-Google-Smtp-Source: AGHT+IE/i37ncF27quoDIRd6tV77bPEjgZXz7gp/USIXaB0/PR+S2UhaphLhE+SgIitzOfsViJ5DvvbS2+c95MyWa9I= X-Received: by 2002:a17:906:289b:b0:a44:da2:11b2 with SMTP id o27-20020a170906289b00b00a440da211b2mr1050004ejd.12.1709202158151; Thu, 29 Feb 2024 02:22:38 -0800 (PST) MIME-Version: 1.0 From: Christophe Lyon Date: Thu, 29 Feb 2024 11:22:33 +0100 Message-ID: Subject: Help needed with maintainer-mode To: binutils@sourceware.org, GCC Mailing List , gdb-patches@sourceware.org Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-2.9 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Hi! Sorry for cross-posting, but I'm not sure the rules/guidelines are the same in gcc vs binutils/gdb. TL;DR: are there some guidelines about how to use/enable maintainer-mode? In the context of the Linaro CI, I've been looking at enabling maintainer-mode at configure time in our configurations where we test patches before they are committed (aka "precommit CI", which relies on patchwork). Indeed, auto-generated files are not part of patch submissions, and when a patch implies regenerating some files before building, we currently report wrong failures because we don't perform such updates. I hoped improving this would be as simple as adding --enable-maintainer-mode when configuring, after making sure autoconf-2.69 and automake-1.15.1 were in the PATH (using our host's libtool and gettext seems OK). However, doing so triggered several problems, which look like race conditions in the build system (we build at -j160): - random build errors in binutils / gdb with messages like "No rule to make target 'po/BLD-POTFILES.in". I managed to reproduce something similar manually once, I noticed an empty Makefile; the build logs are of course difficult to read, so I couldn't figure out yet what could cause this. - random build failures in gcc in fixincludes. I think this is a race condition because fixincludes is updated concurrently both from /fixincludes and $buillddir/fixincludes. Probably fixable in gcc Makefiles. - I've seen other errors when building gcc like configure.ac:25: error: possibly undefined macro: AM_ENABLE_MULTILIB from libquadmath. I haven't investigated this yet. I've read binutils' README-maintainer-mode, which contains a warning about distclean, but we don't use this: we start our builds from a scratch directory. So... I'm wondering if there are some "official" guidelines about how to regenerate files, and/or use maintainer-mode? Maybe I missed a "magic" make target (eg 'make autoreconf-all') that should be executed after configure and before 'make all'? I've noticed that sourceware's buildbot has a small script "autoregen.py" which does not use the project's build system, but rather calls aclocal/autoheader/automake/autoconf in an ad-hoc way. Should we replicate that? Thanks, Christophe