From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id AE5AA158041 for ; Tue, 7 Sep 2021 21:07:05 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 6C406E0976; Tue, 7 Sep 2021 21:06:58 +0000 (UTC) Received: from mail-pj1-x1033.google.com (mail-pj1-x1033.google.com [IPv6:2607:f8b0:4864:20::1033]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id D0D09E0901 for ; Tue, 7 Sep 2021 21:06:56 +0000 (UTC) Received: by mail-pj1-x1033.google.com with SMTP id pi15-20020a17090b1e4f00b00197449fc059so2552364pjb.0 for ; Tue, 07 Sep 2021 14:06:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=d8dX3CrRbM7azBxqPIVdmwekZgnWoIU0hzwwKSFg2kM=; b=Khfq9W7IgX6+QUDFu4l8B2XdYmV2jfEtx5tIs4K7pkFvMu4BBZJlgts+2BwA8dBYSl rKsSbhx0BjA6NsdTBiwudJcpHxa+o0SECShsClFlI0cEFVmtxBoekagub1CLmxDfju7h TJsflMRJCegaKcu30Vm6qWnNOfSnXGOjoZmJOD2dn31jlBdAmbMI7ca/+J4p+I7ZGgni FyLSsFAArWr/lzIsbddsotWzmh5tZYexvRqeIYp3aeZJXWZ65paXnE2QCBfjuE67Hr8n OlhGQdGJemFhew1m9RgOTvNwwb4s0e6dXV3G1TL9amPUwSQ4ryMK5oTnfE1iRZu+xpTT /ibQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=d8dX3CrRbM7azBxqPIVdmwekZgnWoIU0hzwwKSFg2kM=; b=JGSGK0S58wjJthQ/eAx75vycYcwvLMpTKTDuJ1J+RbgTn6bRcNgBQlD4NscBf7aCgC f1D9R3Un08IyZQhIiP9HzFJZK2n25ReQqXa8FQKDyQwpo6CMFTyfvB+GckC9QAqcThe6 VvP6k2zMjiVzAjhafoSK6WJnix/K687EeTSxqhNvrWI0WRnkcE7K4imljXh0TKpb6id7 8pHPzYRuat1KifKoDq86xhsxegocBV1arR+Seu6FWxN1HVwdPqI/6k1q+S1lnDx2xZKU YopNtgOiCo6L7qvbKFnCVWY+R684wGrSzwS1xcVeZZk7l7V8h9GeaCEzJMRbuvW0XbGm Q1OA== X-Gm-Message-State: AOAM5333K91gPiS1xP8ZavRjWbB61nRf+lu3zJJQ+uyrCOaIKwmrBzrk kKhoq7/AVwUtOuu09meErqGnxgTtLpA= X-Google-Smtp-Source: ABdhPJzJPbe2+dvusYjPgZr6hbNOHylj/2Pz5GCEpgB71Lvst4jphPJF+JO3s34k02wuLgjrPW7JMQ== X-Received: by 2002:a17:90b:14d5:: with SMTP id jz21mr316211pjb.11.1631048815688; Tue, 07 Sep 2021 14:06:55 -0700 (PDT) Received: from [192.168.247.5] ([108.180.126.133]) by smtp.gmail.com with ESMTPSA id 141sm58992pgg.16.2021.09.07.14.06.55 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 07 Sep 2021 14:06:55 -0700 (PDT) Subject: Re: [gentoo-user] Broken update To: gentoo-user@lists.gentoo.org References: <9db181b1-d91d-ac28-3d28-400570975677@gmail.com> <20210907201357.488a3674@digimed.co.uk> From: Daniel Frey Message-ID: <259ece54-0265-442c-4af6-13573d1ec52d@gmail.com> Date: Tue, 7 Sep 2021 14:06:54 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 In-Reply-To: <20210907201357.488a3674@digimed.co.uk> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Archives-Salt: 3be996f7-3d2d-4f96-a4b8-d070a58efb79 X-Archives-Hash: fdb6820a6879a973ce26c6c08043edb0 On 9/7/21 12:13 PM, Neil Bothwick wrote: > On Tue, 7 Sep 2021 09:32:41 -0700, Daniel Frey wrote: > >> Why is it checking the build environment for a binary package? > > I was wondering the same. > >> As it stands, I can't fix this problem. >> >> I tried editing the ebuild (removing the __thread check) and rebuilding >> the manifest but it still fails at the same place. I've double- and >> triple-checked it's the right ebuild but it's still running the checks! >> >> Some assistance on installing glibc would be much appreciated! > > You can untar the binary package into /, which bypasses the checks. Then > you can emerge it so that portage knows where it stands. > > The usual guarantees apply: if it breaks your system, you get to keep the > pieces. I'd backup / first. > > Thanks Neil, I just unpacked it manually and it fixed my problem. gcc actually works now so I've remerged (emerge -K1) glibc and pax-utils. I had a *really* old stage4-esque backup if it really came down to it. I think that's the first time a binary update (I have two identical PCs, a bit on the slow side - so one binpkgs them and I install them on the second one, lessening the compiling load.) Still don't know why glibc was checking the build environment for a binary package though, that was really strange. As gcc was broken and not providing any meaningful output for checks, it fails immediately. Dan