From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ludovic =?UTF-8?Q?Court=C3=A8s?= Subject: bug#35691: remote configure failure due to bad pathnames for crt*.o Date: Thu, 16 May 2019 11:52:36 +0200 Message-ID: <87ef4yiv4r.fsf@gnu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([209.51.188.92]:46397) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hRD6d-0005Rp-TA for bug-guix@gnu.org; Thu, 16 May 2019 05:55:20 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hRD4Q-0002ms-7S for bug-guix@gnu.org; Thu, 16 May 2019 05:53:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:40740) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hRD4Q-0002mO-3l for bug-guix@gnu.org; Thu, 16 May 2019 05:53:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hRD4Q-0007j7-0e for bug-guix@gnu.org; Thu, 16 May 2019 05:53:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: (Nelson H. F. Beebe's message of "Wed, 15 May 2019 18:19:06 -0600") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: "Nelson H. F. Beebe" Cc: 35691@debbugs.gnu.org Hi Nelson, "Nelson H. F. Beebe" skribis: > Even after that major update, and reboot, I still find that, from a > remote ssh connection, configure fails to find a C compiler, because > of the faulty construction of the path to crt1.o. I cannot reproduce the problem. With =E2=80=98guix environment=E2=80=99, a= s show below, I build an isolated environment that contains nothing but =E2=80=98gcc-toolchain=E2=80=99 and Bash: --8<---------------cut here---------------start------------->8--- $ guix environment --ad-hoc -C gcc-toolchain [env]$ echo 'int main() { }' > t.c [env]$ gcc t.c [env]$ ./a.out --8<---------------cut here---------------end--------------->8--- As you can see, I can compile and link in that environment. This environment defines PATH, CPATH, and LIBRARY_PATH appropriately: --8<---------------cut here---------------start------------->8--- $ guix environment --ad-hoc -C gcc-toolchain grep coreutils [env]$ env | grep PATH CPATH=3D/gnu/store/26ng85mn5rs22cw654bvh62wh0yjx89h-profile/include LIBRARY_PATH=3D/gnu/store/26ng85mn5rs22cw654bvh62wh0yjx89h-profile/lib PATH=3D/gnu/store/26ng85mn5rs22cw654bvh62wh0yjx89h-profile/bin:/gnu/store/2= 6ng85mn5rs22cw654bvh62wh0yjx89h-profile/sbin --8<---------------cut here---------------end--------------->8--- Can you check the value of CPATH and LIBRARY_PATH in your user shell? What does =E2=80=98guix package --search-paths=E2=80=99 return? (See also the bits about search paths and ~/.guix-profile/etc/profile at .) HTH, Ludo=E2=80=99.