From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by sourceware.org (Postfix) with ESMTPS id B772A3858D37 for ; Mon, 10 Oct 2022 10:06:33 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org B772A3858D37 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1665396393; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=IKmOn3lQtmTZEpfndPbH+lg7Nt11US2C4KW/7ahct2E=; b=E6d9QQcr2fhK1krWld8GVHTza6b9HBSS7LSBvV5Ve2HNbCRw7Gm5Nv2dfEiCKKzP6JAp/t 2HO3BQy+CqeSqpw5vyJse1256YMK+4F1m4eKXn9/gQC64oxm0RxwN9XiC+rfSnczvtR+DS 0zRVjtGjjLcghqGa6z1ooFxlmBx3OhI= Received: from mail-qt1-f197.google.com (mail-qt1-f197.google.com [209.85.160.197]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-644-b8khs7F1NkGkYZYpsYYDTQ-1; Mon, 10 Oct 2022 06:06:32 -0400 X-MC-Unique: b8khs7F1NkGkYZYpsYYDTQ-1 Received: by mail-qt1-f197.google.com with SMTP id bz12-20020a05622a1e8c00b0039ae6e887ffso757768qtb.8 for ; Mon, 10 Oct 2022 03:06:32 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=IKmOn3lQtmTZEpfndPbH+lg7Nt11US2C4KW/7ahct2E=; b=7Zg3ZFyFz2j6KxA+ZQWoHv7nzyCPUNyM/6qeqaOTAwTKwlA+3vQc0RdBHBwd4R4zFI kr/zHXUpP6HyVSKr10M0Pb54M0PrgNfHmQ+bvoUSvHu3/5/dg2pJKiubUps7I1iW1VY+ hvONU4KLsG7KuNztYZh+puGzFOjHmP/06HI5YT4C7OjFtRJg8uL0EpID7xIn+nqaoLja JAyOMzZzi1EWFVG6y6SgFrbX0hOUdJLCTFTu99WSaIVrlFMXc6gzSmEW85NyMRWuQjxO OfPIOHltnFeoyLUo2uLUZsTSKenMWFlfeehDt1CJxp3Yv1Ud+UjDr3zyw0Vjw45sBuIj iZRw== X-Gm-Message-State: ACrzQf1fX8kiELMv8I7yIQKucMG0OhffMT6nw2VJNipn+UxvwBTwr1CR t7N1eCnjTTBPay1yE0/8yTCwaXry6G7KE/ZrXf4rFUjcsYqbNTYXmWV00JQHWdXKX5Yf6fKNz4q CPGXEWeBj/kzzsyk/QQ== X-Received: by 2002:ad4:5b8a:0:b0:4ad:8ee4:a1e5 with SMTP id 10-20020ad45b8a000000b004ad8ee4a1e5mr13903753qvp.23.1665396391154; Mon, 10 Oct 2022 03:06:31 -0700 (PDT) X-Google-Smtp-Source: AMsMyM6y152RbFXcQeh0k2dUV0deM/39SFF/en58+fzvMDOt7j9Fpp2iy8ic42mYPPIhAF8ckQNM1Q== X-Received: by 2002:ad4:5b8a:0:b0:4ad:8ee4:a1e5 with SMTP id 10-20020ad45b8a000000b004ad8ee4a1e5mr13903735qvp.23.1665396390921; Mon, 10 Oct 2022 03:06:30 -0700 (PDT) Received: from [192.168.1.18] (adsl-164-85.freeuk.com. [80.168.164.85]) by smtp.gmail.com with ESMTPSA id u1-20020a05620a0c4100b006cfc4744589sm9916845qki.128.2022.10.10.03.06.29 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 10 Oct 2022 03:06:30 -0700 (PDT) Message-ID: <0aad9687-e70d-9e79-e2d3-cbbba04b10f6@redhat.com> Date: Mon, 10 Oct 2022 11:06:29 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.3.1 Subject: Re: @CPP_FOR_BUILD@ problem since binutils-2.38 To: Jan Beulich , Andrew Goth , "H.J. Lu" Cc: "binutils@sourceware.org" References: From: Nick Clifton In-Reply-To: X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-GB Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,KAM_NUMSUBJECT,NICE_REPLY_A,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_NONE,TXREP 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 Jan, > Hmm, this looks to be due to 08ca783430ac syncing only Makefile.* > with gcc's, but not configure.ac. The CPPFLAGS_FOR_BUILD issue was > meanwhile addressed in isolation by commit e472ec9fad6d. Nick - > what is the general policy / approach of syncing top level files? From the MAINTAINERS file at the top level: Makefile.*; configure; configure.ac; src-release Any global maintainer can approve changes to these files, but they should be aware that they need to be kept in sync with their counterparts in the GCC repository. Also please notify the following of any committed patches: binutils@sourceware.org gdb-patches@sourceware.org So changes to configure.ac should also be submitted to the gcc project. Cheers Nick