From: Tom Tromey <tom@tromey.com>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH][gdb/build] Workaround pcre2_posix linking problem
Date: Mon, 19 Apr 2021 13:44:49 -0600 [thread overview]
Message-ID: <87o8eacb4e.fsf@tromey.com> (raw)
In-Reply-To: <20210406131645.GA1220@delia> (Tom de Vries's message of "Tue, 6 Apr 2021 15:16:46 +0200")
>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
Tom> On openSUSE Tumbleweed, the ncurses package got the --with-pcre2 configure
Tom> switch enabled, and solved the resulting dependencies using:
Tom> ...
Tom> $ cat /usr/lib64/libncursesw.so
Tom> /* GNU ld script */
Tom> -INPUT(/lib64/libncursesw.so.6 AS_NEEDED(-ltinfo -ldl))
Tom> +INPUT(/lib64/libncursesw.so.6 AS_NEEDED(-ltinfo -ldl -lpcre2-posix -lpcre2-8))
Tom> ...
Tom> [gdb/build] Workaround pcre2_posix linking problem
Tom> gdb/ChangeLog:
Tom> 2021-04-06 Tom de Vries <tdevries@suse.de>
Tom> PR build/27681
Tom> * Makefile.in (CDEFS): Add @LIBC@ before @LIBS@.
Tom> * configure.ac: Define LIBC.
Tom> * configure: Regenerate.
Just to be clear, I think this one is also addressed by the other patch
to simply always use the libiberty regex.
On the whole I suppose that one is preferable.
Tom
prev parent reply other threads:[~2021-04-19 19:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 13:16 Tom de Vries
2021-04-19 19:44 ` Tom Tromey [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o8eacb4e.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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