unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
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: Mon, 13 May 2019 09:41:56 +0200	[thread overview]
Message-ID: <87r292vm0r.fsf@gnu.org> (raw)
In-Reply-To: <CMM.0.95.0.1557617050.beebe@gamma.math.utah.edu> (Nelson H. F. Beebe's message of "Sat, 11 May 2019 17:24:10 -0600")

Hi Nelson,

"Nelson H. F. Beebe" <beebe@math.utah.edu> skribis:

> However, if I instead execute those commands remotely with
>
> 	% ssh guix10.vm.example.com 'cd FOO-x.y.z ; ./configure && make all check && make install'
>
> then the configure script fails like this:
>
> 	checking whether the C compiler works... no
> 	configure: error: in `/local/build/cc/dw-2.00':
> 	configure: error: C compiler cannot create executables
> 	See `config.log' for more details
> 	...
>
> The config.log file contains these messages:
>
> 	ld: cannot find crt1.o: No such file or directory
> 	ld: cannot find crti.o: No such file or directory
> 	collect2: error: ld returned 1 exit status

You need to install the ‘gcc-toolchain’ package, not just ‘gcc’:

  https://www.gnu.org/software/guix/manual/en/html_node/Application-Setup.html#The-GCC-toolchain

I hope this helps!

Thanks for testing,
Ludo’.

  reply	other threads:[~2019-05-13  7:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-11 23:24 bug#35691: remote configure failure due to bad pathnames for crt*.o Nelson H. F. Beebe
2019-05-13  7:41 ` Ludovic Courtès [this message]
     [not found] <CMM.0.95.0.1557882967.beebe@gamma.math.utah.edu>
2019-05-15 13:03 ` 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
2019-05-16  9:52         ` Ludovic Courtès
2019-05-16 13:18           ` Giovanni Biscuolo

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r292vm0r.fsf@gnu.org \
    --to=ludo@gnu.org \
    --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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).