From: Ricardo Wurmus <rekado@elephly.net>
To: "Nelson H. F. Beebe" <beebe@math.utah.edu>
Cc: 35691@debbugs.gnu.org
Subject: bug#35691: remote configure failure due to bad pathnames for crt*.o
Date: Thu, 16 May 2019 11:18:54 +0200 [thread overview]
Message-ID: <877eaqaha9.fsf@elephly.net> (raw)
In-Reply-To: <CMM.0.95.0.1557965946.beebe@gamma.math.utah.edu>
Hi Nelson,
> 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.
Earlier you wrote this
there is still a gcc visible: /u/sy/beebe/.guix-profile/bin/gcc.
Where does that come from? Are you activating this profile in some
shell initialisation file? Does that profile contain “gcc-toolchain” or
“gcc”?
What does PATH look like?
You can check with “guix package -p /u/sy/beebe/.guix-profile -l”.
(Or is $HOME equivalent to /u/sy/beebe on this system and the profile is
thus the default?)
I’m interested in the activation of that profile. We recommend adding
these lines to ~/.bash_profile (not .bashrc) in the manual:
export GUIX_PROFILE=$HOME/.guix-profile
source $GUIX_PROFILE/etc/profile
(Leaving out the definition of GUIX_PROFILE will change the behaviour
slightly and you would end up with potentially outdated absolute store
file names in your PATH.)
--
Ricardo
next prev parent reply other threads:[~2019-05-17 1:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CMM.0.95.0.1557882967.beebe@gamma.math.utah.edu>
2019-05-15 13:03 ` bug#35691: remote configure failure due to bad pathnames for crt*.o Ludovic Courtès
2019-05-15 14:27 ` Nelson H. F. Beebe
2019-05-15 16:29 ` Ludovic Courtès
2019-05-16 0:19 ` Nelson H. F. Beebe
2019-05-16 9:18 ` Ricardo Wurmus [this message]
2019-05-16 9:52 ` Ludovic Courtès
2019-05-16 13:18 ` Giovanni Biscuolo
2019-05-11 23:24 Nelson H. F. Beebe
2019-05-13 7:41 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877eaqaha9.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=35691@debbugs.gnu.org \
--cc=beebe@math.utah.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.