From: Anthony Quizon <anthoq88@gmail.com>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: help-guix@gnu.org
Subject: Re: libssl not symlinking from openssl package?
Date: Mon, 13 Jul 2020 14:47:33 +1000 [thread overview]
Message-ID: <CAPHgq+Jfx8bVn2FrfcWhXeKJzu8ookjhNg_oh66eW23rNDqpQQ@mail.gmail.com> (raw)
In-Reply-To: <20200701064511.GE14409@E5400>
Thanks for that - however, it seems to be the same.
I've removed coreutils, binutils-gold and added pkg-config and still are
getting missing links with ldd.
I've just manually set the paths for now as you suggested.
I'm using guix on top of debian - there might be some sort of clash with
the systems environment.
Thanks,
Anthony
On Wed, Jul 1, 2020 at 4:45 PM Efraim Flashner <efraim@flashner.co.il>
wrote:
> On Wed, Jul 01, 2020 at 03:09:03PM +1000, Anthony Quizon wrote:
> > Ok so when I use gcc-toolchain and do a ldd on my binary, I get "not
> found"
> > for the libssl and libcrypto links.
> > However, all other libraries seem to resolve correctly.
> >
> > linux-vdso.so.1 (0x00007ffe86dd2000)
> > libresolv.so.2 =>
> > /gnu/store/fa6wj5bxkj5ll1d7292a70knmyl7a0cr-glibc-2.31/lib/libresolv.so.2
> > (0x00007fcaa9e1c000)
> > libssl.so.1.1 => not found
> > libcrypto.so.1.1 => not found
> > libpthread.so.0 =>
> >
> /gnu/store/fa6wj5bxkj5ll1d7292a70knmyl7a0cr-glibc-2.31/lib/libpthread.so.0
> > (0x00007fcaa9dfb000)
> > libm.so.6 =>
> > /gnu/store/fa6wj5bxkj5ll1d7292a70knmyl7a0cr-glibc-2.31/lib/libm.so.6
> > (0x00007fcaa9cba000)
> > librt.so.1 =>
> > /gnu/store/fa6wj5bxkj5ll1d7292a70knmyl7a0cr-glibc-2.31/lib/librt.so.1
> > (0x00007fcaa9cb0000)
> > libdl.so.2 =>
> > /gnu/store/fa6wj5bxkj5ll1d7292a70knmyl7a0cr-glibc-2.31/lib/libdl.so.2
> > (0x00007fcaa9ca9000)
> > ....
> >
> > Do you know what would make libssl and libcrypto different from the other
> > links?
> >
> > I'm using a manifest file with these packages:
> >
> > (specifications->manifest
> > '("glib"
> > "gcc-toolchain"
> > "binutils-gold"
> >
> >
> >
> > "coreutils"
> > "openssl"
> > ))
>
> I would drop coreutils from the manifest, it should be included in
> gcc-toolchain. binutils-gold also unless you need the gold linker. Do
> you have pkg-config in the manifest? The libraries that I see as linked
> are all from glibc. Alternatively you might need to add the linker flags
> yourself, ie: -l$(GUIX_ENVIRONMENT)/lib/libssl (or however it goes,
> assuming you're using 'guix environment' and not a permanent profile).
>
> >
> > On Wed, Jul 1, 2020 at 7:49 AM Anthony Quizon <anthoq88@gmail.com>
> wrote:
> >
> > > Oh sorry, stupid mistake.
> > > That's the environment variable I set to point to
> > > "$HOME/.guix-profile/lib". I was wondering if the openssl lib files
> were
> > > meant to be populated there.
> > > But now I can see that its actually in $LIBRARY_PATH when
> gcc-toolchain is
> > > installed like you said.
> > >
> > >
> > > On Tue, Jun 30, 2020 at 11:43 PM Ricardo Wurmus <rekado@elephly.net>
> > > wrote:
> > >
> > >>
> > >> Anthony Quizon <anthoq88@gmail.com> writes:
> > >>
> > >> > I've run `guix install openssl` but it seems like the libraries are
> not
> > >> > populated in $GUIX_LIBRARY_PATH
> > >>
> > >> What is GUIX_LIBRARY_PATH supposed to be?
> > >>
> > >> The LIBRARY_PATH variable is set when you have gcc-toolchain
> installed.
> > >> GUIX_LIBRARY_PATH is not set by anything in Guix as far as I know.
> > >>
> > >> --
> > >> Ricardo
> > >>
> > >
>
> --
> Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
> GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
> Confidentiality cannot be guaranteed on emails sent or received unencrypted
>
next prev parent reply other threads:[~2020-07-13 4:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 1:55 libssl not symlinking from openssl package? Anthony Quizon
2020-06-30 13:43 ` Ricardo Wurmus
2020-06-30 21:49 ` Anthony Quizon
2020-07-01 5:09 ` Anthony Quizon
2020-07-01 6:45 ` Efraim Flashner
2020-07-13 4:47 ` Anthony Quizon [this message]
2020-07-13 9:09 ` Efraim Flashner
2020-07-20 6:04 ` Anthony Quizon
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=CAPHgq+Jfx8bVn2FrfcWhXeKJzu8ookjhNg_oh66eW23rNDqpQQ@mail.gmail.com \
--to=anthoq88@gmail.com \
--cc=efraim@flashner.co.il \
--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).