From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf1-x133.google.com (mail-lf1-x133.google.com [IPv6:2a00:1450:4864:20::133]) by sourceware.org (Postfix) with ESMTPS id 0313F3858D20 for ; Wed, 10 Apr 2024 13:30:56 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 0313F3858D20 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=gmail.com ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 0313F3858D20 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=2a00:1450:4864:20::133 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1712755857; cv=none; b=NNvyChz/oSTkHD2LTeTjjnQUuBWIkdTJVU2HJfjADgz9NQYdZTjjRPHNTCatNhS24tSwPDfDfw9nkm0jrhUed6TNHV9uCh1yooR3c0tNUohdEkEn/kUJOwKYzjW1njynIVmWhs00TGDe/StaVSvJh78Auy3jToH5c9yNX/U5dD4= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1712755857; c=relaxed/simple; bh=eKJGN4XUBcyN+5MX7UsKFYlBICeNUH01hEraWPyjlaY=; h=DKIM-Signature:Message-ID:Date:MIME-Version:Subject:To:From; b=fc2OnvgNlSEFnn0vll7jgpXDtaw0M1CApgODEvtq/LVn1p3OeR9EBlqokQqyGF/ylDm7URNU8m1p3W/8pC/HaU8MuyAYaz86xSFgiQp/5iu7rEjtOaEm5e6A5XQsl2nftmaivoQ9BXCskNw4h2ACiGj03f3byeVdyLJGAxZP530= ARC-Authentication-Results: i=1; server2.sourceware.org Received: by mail-lf1-x133.google.com with SMTP id 2adb3069b0e04-5176f217b7bso1069695e87.0 for ; Wed, 10 Apr 2024 06:30:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1712755854; x=1713360654; darn=sourceware.org; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=nnkHJdbAcJiPDySS7j5KSXYP0Z/pW9/NAtJ7a1upEOU=; b=Ir/Nq2ztJ1x+27C5K//7fToJ/S+e9szHJMPjmwkz1XVN3gRZf94a3duASg4n5/C0tw L7B4XM49BpNRDl3xNRL/tnfp8DSX6txJAbzzgyYE/lo0QPJ+eCtZODu1ckX+G/iIooZ/ +gIkjC/s5cuvD4GprdsSROnMvTdWRNDl4fyHBf4jc4IK57wQj0lPISxY2HtDFMJod+6E 1637kG9Sz0wmor282sd0fEeKrQTGFpSYRrjowYwHsCEo6CfdGNE1C08NHnV+FEUtAWvD LdeLONk+rhWTbc9nuxosBTw7VNegUQJeGRfCo/oukrpkIB912fjqHdeWI91D+3UXdd3t LACQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712755854; x=1713360654; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=nnkHJdbAcJiPDySS7j5KSXYP0Z/pW9/NAtJ7a1upEOU=; b=vTSEN5wstLIvLbAbQC/N16OZ800JH2kfo0Xzq4+i3X0zJPeadrtyKUwHZgNkKfYJ4g IUfsg9ewd8FDk6MsBn0YJ9PmEJiZt8bDcHHwpzUfboR1mHpjlZ556y+JFPsLe8rabEWA 6owEX3BH6co3O9PtgfjMUvPFMMgGHCSq7Lbxnfie60iw6pSeo1KgzVwhz8ZaKrBosIeD yfUbCAYJhTqtlPzrV4+0/wURK93iTHkugW66UiRlcTy3YRY2fHydL9KIBcqVKmc+hVIO KqJETbwlSp/LPtMGx8357iX05SmM3Zcy/hqZR04bJNgMxv6QyE6KsF2VVsknqlsKOzfm +VUw== X-Gm-Message-State: AOJu0YwRfyG1ZNdUEV5r9lUiW5e+YbBFFnnUuDKRX0HnoFJI98NcQrA6 RpAn73jQYnRQplbcYKiQbmLB73PkUdkLgm7RFOoH+TXdprQp2WhJ X-Google-Smtp-Source: AGHT+IHCsRQCcJFX1beiVzjihpooPjfF7M2/jqw+3r1EqiX5/sgDshIKu0wwm6rKWV1iU87OcvPv/Q== X-Received: by 2002:ac2:5dc4:0:b0:516:be9d:11ac with SMTP id x4-20020ac25dc4000000b00516be9d11acmr2151319lfq.13.1712755853606; Wed, 10 Apr 2024 06:30:53 -0700 (PDT) Received: from [0.0.0.0] ([94.177.207.80]) by smtp.googlemail.com with ESMTPSA id qx3-20020a170906fcc300b00a4e26377bf1sm7052870ejb.175.2024.04.10.06.30.52 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 10 Apr 2024 06:30:53 -0700 (PDT) Message-ID: Date: Wed, 10 Apr 2024 16:30:51 +0300 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Beta Subject: Re: libstdc++ link errors in support/links-dso-program To: Konstantin Kharlamov , Florian Weimer Cc: =?UTF-8?B?0JPQvtGA0LHQtdGI0LrQviDQkdC+0LPQtNCw0L0gdmlhIExpYmMtaGVscA==?= References: <87msr0hs3n.fsf@oldenburg.str.redhat.com> <8734srh194.fsf@oldenburg.str.redhat.com> <98b5b573-67b8-4110-8759-ca67fab6f85b@gmail.com> <874jc92znl.fsf@oldenburg.str.redhat.com> <290c8346-5c9f-4d2e-80b8-80bdabfe833f@gmail.com> <442b4a2d966e8a34cf948e58416573157f9b5814.camel@yandex.ru> Content-Language: en-US From: =?UTF-8?B?0JPQvtGA0LHQtdGI0LrQviDQkdC+0LPQtNCw0L0=?= In-Reply-To: <442b4a2d966e8a34cf948e58416573157f9b5814.camel@yandex.ru> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=3.6 required=5.0 tests=BAYES_00,BODY_8BITS,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,RCVD_IN_BARRACUDACENTRAL,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=no autolearn_force=no version=3.4.6 X-Spam-Level: *** X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On 10/04/2024 16:22, Konstantin Kharlamov wrote: > On Wed, 2024-04-10 at 15:50 +0300, Горбешко Богдан via Libc-help wrote: >> On 10/04/2024 15:03, Florian Weimer wrote: >>> * Горбешко Богдан: >>> >>>> We already have a solution to build this in Docker, though the >>>> target >>>> test VPS is tight on resources and I wouldn't really like to mess >>>> with >>>> Docker there. >>> You don't have to build on the target system directly, you just >>> need to >>> use a container/chroot environment that matches the target >>> distribution >>> version.  These containers tend to be fairly lightweight, requiring >>> less >>> space and resources than a full glibc build. >> An unpacked binary Glibc package takes just 12 MB. A minimal Debian >> image is orders of magnitude larger. >> >> And the primary problem with Docker is that continuous rebuilds >> occupy >> the disk space rapidly fast, as it normally preserves old builds, >> which >> is not a case with builds on a host system. > I am confused. Docker may or may not preserve something depending on > how you use it. You're saying compilation on the host system is not > preserved, which confuses me even further because why would it not. > Unless you run `make clean && make distclean` sure you have all > artifacts in place. The primary difference is that artifacts overwrite the same files, while in Docker every difference involves creating new images (or new cache entries if BuildKit is used) for the whole chain after the layer where a change happened. > > Anyway. As far as I understand what you're saying you don't want Docker > to preserve a build. I presume it's being "preserved" because you're > building on a host directory that is mount-bound via `-v` option (there > isn't many other ways you'd be getting that. Saving container state is > another one but why would you do that if you don't want the state to be > saved. So it is likely not that). You can solve that by using mount- > bind in such way so that any changes the container does to the mound- > bind will only be visible inside the container. Idk of any ways to do > that in the vanilla Docker, but in Podman it's supported by `:O` > option, i.e. `-v my_host_dir:/mnt:O`. I already added a lot of bind mounts and cache mounts to minimize the redundancy. Cache mounts are reused between builds, at least.