From: Eli Zaretskii <eliz@gnu.org>
To: noloader@gmail.com
Cc: 42651@debbugs.gnu.org
Subject: bug#42651: emacs-27.1-rc1 and wrong GnuPG libraries
Date: Sat, 01 Aug 2020 18:17:13 +0300 [thread overview]
Message-ID: <83pn8acs5i.fsf@gnu.org> (raw)
In-Reply-To: <CAH8yC8mYEsY6D1EAmp_mMxss=1Oaj0NBcc90ty3EXgh2-jT_Cw@mail.gmail.com> (message from Jeffrey Walton on Sat, 1 Aug 2020 11:14:25 -0400)
> From: Jeffrey Walton <noloader@gmail.com>
> Date: Sat, 1 Aug 2020 11:14:25 -0400
> Cc: 42651@debbugs.gnu.org
>
> On Sat, Aug 1, 2020 at 11:11 AM Eli Zaretskii <eliz@gnu.org> wrote:
> >
> > > From: Jeffrey Walton <noloader@gmail.com>
> > > Date: Sat, 1 Aug 2020 11:05:00 -0400
> > > Cc: 42651@debbugs.gnu.org
> > >
> > > On Sat, Aug 1, 2020 at 11:04 AM Eli Zaretskii <eliz@gnu.org> wrote:
> > > >
> > > > > From: Jeffrey Walton <noloader@gmail.com>
> > > > > Date: Sat, 1 Aug 2020 10:51:54 -0400
> > > > >
> > > > > I was looking at the ldd dependencies of emacs-27.1-rc1. It shows a
> > > > > dependency on GnuPG warez:
> > > >
> > > > Why is that a problem?
> > >
> > > The wrong library.
> >
> > Which one?
>
> Both libgcrypt.so and libgpg-error.so.
So you would like your own libraries linked into Emacs, is that the
issue here? If so, I think you need to set up your build to look
there, by setting LDFLAGS at configure time. Would that solve the
problem?
next prev parent reply other threads:[~2020-08-01 15:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-01 14:51 bug#42651: emacs-27.1-rc1 and wrong GnuPG libraries Jeffrey Walton
2020-08-01 15:04 ` Eli Zaretskii
2020-08-01 15:05 ` Jeffrey Walton
2020-08-01 15:11 ` Eli Zaretskii
2020-08-01 15:14 ` Jeffrey Walton
2020-08-01 15:15 ` Jeffrey Walton
2020-08-01 15:17 ` Eli Zaretskii [this message]
2020-08-01 15:21 ` Jeffrey Walton
2020-08-01 15:22 ` Jeffrey Walton
2021-10-11 13:41 ` Stefan Kangas
2021-11-09 6:42 ` Lars Ingebrigtsen
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83pn8acs5i.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=42651@debbugs.gnu.org \
--cc=noloader@gmail.com \
/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/emacs.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).