From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: Jeffrey Walton <noloader@gmail.com>, 42651@debbugs.gnu.org
Subject: bug#42651: emacs-27.1-rc1 and wrong GnuPG libraries
Date: Tue, 09 Nov 2021 07:42:07 +0100 [thread overview]
Message-ID: <87wnlhq18g.fsf@gnus.org> (raw)
In-Reply-To: <CADwFkmkHabPUd5Jwujc=67pcK1OHmDJiNzJO3EGM4CCMcuJPAQ@mail.gmail.com> (Stefan Kangas's message of "Mon, 11 Oct 2021 06:41:12 -0700")
Stefan Kangas <stefan@marxist.se> writes:
>> LDFLAGS is set. Here are the flags I use for every package I build on Linux.
>>
>> AUTOCONF_BUILD: x86_64-pc-linux-gnu
>> PKG_CONFIG_PATH: /usr/local/lib/pkgconfig
>> CPPFLAGS: -I/usr/local/include -DNDEBUG
>> ASFLAGS: -Wa,--noexecstack
>> CFLAGS: -g2 -O2 -march=native -fPIC -pthread
>> CXXFLAGS: -g2 -O2 -march=native -fPIC -pthread
>> LDFLAGS: -L/usr/local/lib -Wl,-R,'$ORIGIN/../lib'
>> -Wl,-R,/usr/local/lib -Wl,--enable-new-dtags -Wl,-z,relro -Wl,-z,now
>> -Wl,-z,noexecstack -Wl,-z,origin
>> LDLIBS: -ldl -lpthread
>
> Could you provide a recipe for reproducing this issue?
More information was requested, but no response was given within a
month, so I'm closing this bug report. If progress can be made,
please respond to this email and we'll reopen the bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2021-11-09 6:42 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
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 [this message]
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=87wnlhq18g.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=42651@debbugs.gnu.org \
--cc=noloader@gmail.com \
--cc=stefan@marxist.se \
/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).