From: "Huang\, Ying" <huang_ying_caritas@163.com>
To: help-guix <help-guix@gnu.org>
Subject: Re: Link to ~/.guix-profile/lib/*.so
Date: Sun, 19 Feb 2017 16:10:53 +0800 [thread overview]
Message-ID: <87tw7qtxbm.fsf@163.com> (raw)
In-Reply-To: <871suuyen5.fsf@163.com> (Ying Huang's message of "Sun, 19 Feb 2017 12:43:10 +0800")
"Huang, Ying" <huang_ying_caritas@163.com> writes:
> I tried to build Linux kernel by hand with Guix. But run `make
> menuconfig` failed. I checked the menuconfig program, found some
> library couldn't be found.
>
> $ ldd scripts/kconfig/mconf
> linux-vdso.so.1 (0x00007ffe87fe8000)
> libncursesw.so.6 => not found
> libgcc_s.so.1 => /gnu/store/vfvd0r69nv3221p907nb7cgk7inzmf9q-gcc-6.3.0-lib/lib/libgcc_s.so.1 (0x00007fd7fd492000)
> libc.so.6 => /gnu/store/iwgi9001dmmihrjg4rqhd6pa6788prjw-glibc-2.24/lib/libc.so.6 (0x00007fd7fd0f3000)
> /gnu/store/iwgi9001dmmihrjg4rqhd6pa6788prjw-glibc-2.24/lib/ld-linux-x86-64.so.2 (0x00007fd7fd6a9000)
>
> $ ls ~/.guix-profile/lib/libncursesw.so.6
> /home/<user>/.guix-profile/lib/libncursesw.so.6@
>
> Set LD_LIBRARY_PATH=$HOME/.guix-profile/lib could solve this, but it is
> said that is not a good solution. So I think we need a solution to make
> $HOME/.guix-profile/lib the fallback to search dynamic linked library.
I can fix this via adding -Wl,-rpath=xxx into gcc command line when
compiling scripts/kconfig/mconf. Is there any better solution?
A more general use case, say I want to develop a GTK application, so I
use pkg-config to get the compiler options. But it appears that this
doesn't work on Guix because the RUN_PATH doesn't set in the built
binaries. How to do that in Guix?
Best Regards,
Huang, Ying
next prev parent reply other threads:[~2017-02-19 8:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-19 4:43 Link to ~/.guix-profile/lib/*.so Huang, Ying
2017-02-19 8:10 ` Huang, Ying [this message]
2017-02-19 8:29 ` Mathieu OTHACEHE
2017-02-19 8:49 ` Huang, Ying
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=87tw7qtxbm.fsf@163.com \
--to=huang_ying_caritas@163.com \
--cc=help-guix@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.
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).