From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ej1-x62a.google.com (mail-ej1-x62a.google.com [IPv6:2a00:1450:4864:20::62a]) by sourceware.org (Postfix) with ESMTPS id 925EB3858CDA for ; Thu, 29 Feb 2024 10:22:39 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 925EB3858CDA 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 925EB3858CDA Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=2a00:1450:4864:20::62a ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1709202161; cv=none; b=a9XyoJfnpnDZS6m4Crs7gWN62kQBboBpRAHv7EsPHk3qePUBt+lruqUDqNWtXwa7rVhwSqGjANDrYWoVH/rAoZiZjjxoKLpyRIQmtz65I42ZFJh20UFevNVdgZO29ltDgKNt9KA+9+XJVct2L9Ca7hHB9ssrRr/KTxHOWOhfaQ8= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1709202161; c=relaxed/simple; bh=Knvs2IjSb308niJZmpk/oYPPjGYdtIeb679kO1ORqP0=; h=DKIM-Signature:MIME-Version:From:Date:Message-ID:Subject:To; b=KpoHncP7UNTR4xG5YuUCe1Y1e8tvfg4LR7XlMVDEaodIaVD9RY/dBGfG5bBx4lmoKwBR2Fiiie29zfrGEjGc7sYLksPnoVgmF0mbqBQJO7yaAGqPPeHasWiPPwn2in0sysuQOIt13JL72kgNMMYNWP/DPVbOumXqWQyRkt1OwUw= ARC-Authentication-Results: i=1; server2.sourceware.org Received: by mail-ej1-x62a.google.com with SMTP id a640c23a62f3a-a3e706f50beso115367266b.0 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=sourceware.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=RZJPFZmauZiPY79/AHOdllMrenn9dUK5tOmt2pCtKjU=; b=JoVkBvtFf+MowVjZwLaLgGICFOPFYBuPhwbg204eelRx10QvqxySoxriZCuZJoSikq 6ibspnh7O51ewmt86+6lnHpFPQs6b6g2l8gcz/mQNort/LPWxOr6ACv2as6X7Ic1/7ms Undj+UoGfG/qNbJ+z3oZkim8eKckwRb81RuT0TAV52In/FQXS1TjR7V60WcYvgIz6ESU 8cw9wXoue6HrRxSYTFBdfDZY5cJH6Qu7DgqR/DBaeLnL0leKqdKVqh6vd/OwDhv2xP+N jrHT4ErmOLl7paAB57cQKqQ7rEGeWWJlWdBZqzb0r43kk4W/Wb3CPz4ihly3F4zaedqU zHwQ== 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=YLOUJiHYKvhs/wSmCge3WCtZ1tszxbdrK1uqxxvUd0czAVUS4EvVVAXc6kzLbPi6of Xp+X/7bq94DIZFYLWMoavgrKoVLFjXHyax2oVuKfZZmSUVwqs0uG49EE6UAF8oelwZhm mV2jOaVzWZfiCRzYa45cmcwUlZkvU/d0VD6ooAM7wWX+6YZgMEQR3ATekudh1fsCbgVV GJRW0WY7KSTIWcj0t3+kvofCfNcMLjZlYwir6Hz2aiqX8Cm/Fdhua6+YOX0jGcZz/CAU PUbGcXiAVy75noudrjYzOcRXFBImZ7uo8h+2jBiTSLgybt0LD/Z1h0curcFilYGXkIz1 /s0w== X-Forwarded-Encrypted: i=1; AJvYcCW5TL2o706k7j3Lo1/9c5xQJobdcz6JhUBEyW3/E38CYNwWYdDbZdfM2zDLxbYj+8JraxWsFLOpdcx2PlGYZtB8KFxBiuqGRbPnFg== X-Gm-Message-State: AOJu0YxFbMHef4XmN9EG3HvZL0L1QcSUm/G+xJ6vWATyonsa7V3y7b7T hwySdUkT+lXCi1N8eKwC827g/sNFnjUV4cfyT5FqxLwsJNqEcI0BfCl6XEgKMYIUI1Paj8BvO8f wrL7/AhFjOwFKu8o8hgTOupZ2XPcdVEP19gY08A== 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=-4.4 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=ham 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