From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from forward501c.mail.yandex.net (forward501c.mail.yandex.net [IPv6:2a02:6b8:c03:500:1:45:d181:d501]) by sourceware.org (Postfix) with ESMTPS id 075E53858D20 for ; Wed, 10 Apr 2024 13:22:30 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 075E53858D20 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=yandex.ru Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=yandex.ru ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 075E53858D20 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=2a02:6b8:c03:500:1:45:d181:d501 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1712755352; cv=none; b=WnbsnUQTuJxv2E6eH+cWTzZNG1aZMHp59znSPuoPo9DMMZ23pWGExtKqoVE363SOATzBMpsX7Aa/ezgh91RQyvbEFBtZSHJXdhsfbMhEgoM/1qcD1glNm8EmSqJw04hicntX3nsHejjgidqPVugvXsZOElM4izqEZVB8GqsRgw0= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1712755352; c=relaxed/simple; bh=stsyc8NCrDs9h7KEqzQMeJ9K8z9uyz2t8KfvjjDWg9A=; h=DKIM-Signature:Message-ID:Subject:From:To:Date:MIME-Version; b=jsGPWR4+pgGg+JgfdCDmxSbu2v23YBD/j2YxAKkU/5h2V6+4nWyryNY7hlCL87VDQAvKBdzLb8Ay4XGB3FyLYFPMi8ONd+JRxdrWi2/xN0z2ebT/OncBl30eXNrU6AJi5JYnNWP5Pv8cfPWPLHUvS+KeZIY5WLfClSd54jgf3aA= ARC-Authentication-Results: i=1; server2.sourceware.org Received: from mail-nwsmtp-smtp-production-main-39.sas.yp-c.yandex.net (mail-nwsmtp-smtp-production-main-39.sas.yp-c.yandex.net [IPv6:2a02:6b8:c08:f220:0:640:b85:0]) by forward501c.mail.yandex.net (Yandex) with ESMTPS id 6005260E60; Wed, 10 Apr 2024 16:22:26 +0300 (MSK) Received: by mail-nwsmtp-smtp-production-main-39.sas.yp-c.yandex.net (smtp/Yandex) with ESMTPSA id PMa4lPCRi4Y0-xDRK5Suo; Wed, 10 Apr 2024 16:22:26 +0300 X-Yandex-Fwd: 1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1712755346; bh=stsyc8NCrDs9h7KEqzQMeJ9K8z9uyz2t8KfvjjDWg9A=; h=References:Date:In-Reply-To:Cc:To:From:Subject:Message-ID; b=iQ1GAYSknvVFY1I48GY5NFzOL6kDXBxkMu/QSD3sJHZH5f85UnF9UyoLTlP/767Po aA2QplxD+yQi9+jdQtdOMH1LD2TVAq97/bfeloTKxPoDrwMceH0NidCsZN+dvA8xuq FoqiIujaSmrMnRZDEn/d8ypyKRVlzAJaliguCUjY= Authentication-Results: mail-nwsmtp-smtp-production-main-39.sas.yp-c.yandex.net; dkim=pass header.i=@yandex.ru Message-ID: <442b4a2d966e8a34cf948e58416573157f9b5814.camel@yandex.ru> Subject: Re: libstdc++ link errors in support/links-dso-program From: Konstantin Kharlamov To: =?UTF-8?Q?=D0=93=D0=BE=D1=80=D0=B1=D0=B5=D1=88=D0=BA=D0=BE_?= =?UTF-8?Q?=D0=91=D0=BE=D0=B3=D0=B4=D0=B0=D0=BD?= , Florian Weimer Cc: =?UTF-8?Q?=D0=93=D0=BE=D1=80=D0=B1=D0=B5=D1=88=D0=BA=D0=BE_?= =?UTF-8?Q?=D0=91=D0=BE=D0=B3=D0=B4=D0=B0=D0=BD?= via Libc-help Date: Wed, 10 Apr 2024 16:22:25 +0300 In-Reply-To: <290c8346-5c9f-4d2e-80b8-80bdabfe833f@gmail.com> 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> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.52.0 MIME-Version: 1.0 X-Spam-Status: No, score=-1.2 required=5.0 tests=BAYES_00,BODY_8BITS,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_HELO_NONE,SPF_PASS,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: On Wed, 2024-04-10 at 15:50 +0300, =D0=93=D0=BE=D1=80=D0=B1=D0=B5=D1=88=D0= =BA=D0=BE =D0=91=D0=BE=D0=B3=D0=B4=D0=B0=D0=BD via Libc-help wrote: > On 10/04/2024 15:03, Florian Weimer wrote: > > * =D0=93=D0=BE=D1=80=D0=B1=D0=B5=D1=88=D0=BA=D0=BE =D0=91=D0=BE=D0=B3= =D0=B4=D0=B0=D0=BD: > >=20 > > > 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.=C2=A0 These containers tend to be fairly lightweight, requirin= g > > less > > space and resources than a full glibc build. >=20 > An unpacked binary Glibc package takes just 12 MB. A minimal Debian=20 > image is orders of magnitude larger. >=20 > And the primary problem with Docker is that continuous rebuilds > occupy=20 > the disk space rapidly fast, as it normally preserves old builds, > which=20 > is not a case with builds on a host system.=C2=A0 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. 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`.