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 11:14:46 +0100	[thread overview]
Message-ID: <87k1vdqm09.fsf@gnu.org> (raw)
In-Reply-To: <87vaf72y9w.fsf@gnu.org> (Mathieu Lirzin's message of "Thu, 08 Feb 2018 18:20:59 +0100")

Hi Mathieu,

Mathieu Lirzin <mthl@gnu.org> skribis:

> I have been facing a weird issue where some shitty build tool I was
> using has tried to run ‘cmake’ after setting LD_LIBRARY_PATH.  The
> result was a non terminating call to ‘collect2’.
>
> Here is a way to reproduce the issue:
>
>   $ guix environment --pure --ad-hoc gcc-toolchain
>   $ echo "int main() { return 0; }" > foo.c
>   $ LD_LIBRARY_PATH="$HOME/.guix-profile/lib" gcc foo.c

That works for me (i.e., ‘gcc’ runs to completion just fine.)

But I suppose this depends on what’s in ~/.guix-profile/lib.  If you
have a conflicting GCC version there (which is not the case for me), it
could break.

Could you run the snippet you provided above with ‘--verbose’ passed to
‘gcc’?  That will allow us to see what libraries and tools it picks up.

> When adding ‘binutils’ to the environment, the problem dissapears since
> ‘ld-wrapper’ is not used anymore.

What makes you think ‘ld-wrapper’ is involved?

Anyway, the ‘--verbose’ output should give us more insight.

Thanks,
Ludo’.

  reply	other threads:[~2018-02-16 10:15 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 [this message]
2018-02-16 12:01   ` Mathieu Lirzin
2018-02-16 13:03     ` Ludovic Courtès
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=87k1vdqm09.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).