unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Mathieu Lirzin <mthl@gnu.org>
Cc: 30395@debbugs.gnu.org
Subject: bug#30395: ‘gcc’ doesn't compile with LD_LIBRARY_PATH="$HOME/.guix-profile/lib"
Date: Fri, 16 Feb 2018 14:03:30 +0100	[thread overview]
Message-ID: <874lmhozml.fsf@gnu.org> (raw)
In-Reply-To: <87mv09gn3i.fsf@gnu.org> (Mathieu Lirzin's message of "Fri, 16 Feb 2018 13:01:21 +0100")

Mathieu Lirzin <mthl@gnu.org> skribis:

> GCC is waiting on ‘collect2’ to finish and ‘collect2’ according to [1]
> tries to find ‘ld’.  When ‘ld’ is provided by Binutils the program
> completes but not with ‘ld-wrapper’ on my machine, so I suspect this is
> related to ‘ld-wrapper’, but maybe this is just a symptom of something
> else.

Oooh, I see.  It could be the ‘guile’ used by ld-wrapper that fails
somehow.

Do you have ‘guile’ in ~/.guix-profile?  You could run again that gcc
command, this time prefixed with “strace -f -o log” to see which
libguile.so is being used when ‘ld’ is invoked, and whether something
else is going on, such as auto-compilation or something?

Ludo’.

  reply	other threads:[~2018-02-16 13:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-08 17:20 bug#30395: ‘gcc’ doesn't compile with LD_LIBRARY_PATH="$HOME/.guix-profile/lib" Mathieu Lirzin
2018-02-16 10:14 ` Ludovic Courtès
2018-02-16 12:01   ` Mathieu Lirzin
2018-02-16 13:03     ` Ludovic Courtès [this message]
2018-02-16 14:56       ` Mathieu Lirzin
2018-02-16 16:43         ` Ludovic Courtès
2018-02-17 19:02           ` Mathieu Lirzin
2018-02-17 21:16             ` Ludovic Courtès
2018-02-17 22:49               ` Mathieu Lirzin
2018-02-18 13:51                 ` Ludovic Courtès
2018-02-18 21:51                   ` Mathieu Lirzin

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=874lmhozml.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=30395@debbugs.gnu.org \
    --cc=mthl@gnu.org \
    /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).