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.129.124]) by sourceware.org (Postfix) with ESMTPS id 39D423858CD1 for ; Fri, 23 Jun 2023 12:30:44 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 39D423858CD1 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=1687523443; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=q5ogcs70oINqWa43dvcbMEH+8GxCUDlTXuZJSQpJ5Po=; b=UxyuziD4D5dBhF4f5N72DzWve6yb55HHM/n2J1gO8wvZYD7ZKFX83kMM2ojAG+BzIYUQZb fJ+3XluzH8Sxoipg/eFj7BOArTllCU5hoGBLUvuGLhI9xLwqBSVUknbbEMr5eAIztjSHsY +lp4OTVEG+9FXLjobalXBj9q4NqJDp4= Received: from mail-vs1-f72.google.com (mail-vs1-f72.google.com [209.85.217.72]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-179-kFTQ5nXSNEKseL0OX_sV8A-1; Fri, 23 Jun 2023 08:30:42 -0400 X-MC-Unique: kFTQ5nXSNEKseL0OX_sV8A-1 Received: by mail-vs1-f72.google.com with SMTP id ada2fe7eead31-440d2cd1087so69638137.1 for ; Fri, 23 Jun 2023 05:30:42 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687523442; x=1690115442; h=content-transfer-encoding:in-reply-to:organization:from:references :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=q5ogcs70oINqWa43dvcbMEH+8GxCUDlTXuZJSQpJ5Po=; b=Bfo6YNKO8+DBktYDtyDojfITAtVCzi8nSiJAwe8867dtFkEy+AxefZUVLQO3SF7EUx 8MQy0eokfsq6qFTXYcrsOOYIHz9WGDN40/QDTwPFJA7MM5LF8x/kwEXSc5oX3U0R7Jr5 pJPEb6VZ8CAdDkfHIIK8/JKJr1JBg9pcVn0/L4MwGggiDh8FUGDUg2pFQLPl1HGaSFj1 YNRWttvbvCxJjCah3G7OokjOa1DsZQUsMggSAP6jzOShG5+J2XzMWW3GS2AaVLM76/Lp kg8VXryiy85dgO5vPQbBu3Gq9dvsuCZlDs0v49BBXHfiS6Oib7sgSYH06ptuOhSXVAc3 eQJQ== X-Gm-Message-State: AC+VfDyBwQpgE2vZGFklq8EXLYyVRC7tREwtG60ce4VgNwFs46LPTJuy LUoqS3QepnDr6xRfYRpe+bU2bC7u03ex3odBKWT3A9BMxnAs2iulRum5Pe1c/DqvD25F0hy1W/L sIDitd3t59a0UJt30CzA= X-Received: by 2002:a67:f5d4:0:b0:440:b898:4bc2 with SMTP id t20-20020a67f5d4000000b00440b8984bc2mr9108418vso.14.1687523441915; Fri, 23 Jun 2023 05:30:41 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ6MN6QXxZ83owxjyfOdXyz137T/enlc7CGXjm6UKKaMhLf02VPMOF+TQ8wxlXADTLFU9E4ahg== X-Received: by 2002:a67:f5d4:0:b0:440:b898:4bc2 with SMTP id t20-20020a67f5d4000000b00440b8984bc2mr9108395vso.14.1687523441665; Fri, 23 Jun 2023 05:30:41 -0700 (PDT) Received: from [192.168.0.241] ([198.48.244.52]) by smtp.gmail.com with ESMTPSA id t98-20020a25aaeb000000b00bd232859d10sm2037043ybi.33.2023.06.23.05.30.40 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 23 Jun 2023 05:30:41 -0700 (PDT) Message-ID: <7fdaba9d-e1b1-8062-3ba9-4dff81d79b8d@redhat.com> Date: Fri, 23 Jun 2023 08:30:40 -0400 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.12.0 Subject: Re: build-many-glibcs.py build failure for i686-gnu To: Joe Simmons-Talbott , Sergey Bugaev , libc-help References: <20230622195952.GL6392@oak> From: Carlos O'Donell Organization: Red Hat In-Reply-To: X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-US Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-6.7 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H5,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE,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: On 6/23/23 08:07, Joe Simmons-Talbott wrote: > This is likely the case as it has been a while since I ran > build-many-glibcs.py ./ collect. Which leads me to the question; How > do I keep my build-many-glibcs directory properly updated? It seems > that I should, every so often, remove the directory and re-run the > collect, host-libraries, and compilers steps to get the latest > changes. There is no way to track cross-project dependencies today. You just have to know that when a cross-project change occurs that you'll need to checkout your sources again to get the latest version, particularly where that source uses the main development branch. We would have to add meta-data to the gnumach checkout information in bmg to track which version of glibc works with that version of gnumach etc., but in practice as a developer you just may need to checkout the latest in-flight version to get things to work as we make cross-project changes. It is possible to do better though, glibc's configure could have detected out of date gnumach headers... but that's additional work that Sergey may not want to do for an unreleased transient change between two projects. In summary: - When dealing with released version of projects we should use configure checks to detect header versions and issue diagnostics. - When dealing with unreleased versions, this is just part of the developer requirements to stay up to date with the checkout of the latest cross-project dependencies. -- Cheers, Carlos.