From: Mike Frysinger <vapier@gentoo.org>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH/submitted 01/10] sim: ppc: move long long test to top-level
Date: Tue, 9 Jan 2024 12:50:16 -0500 [thread overview]
Message-ID: <ZZ2HWLpSqQGwhe5A@vapier> (raw)
In-Reply-To: <87edeqwp8t.fsf@tromey.com>
[-- Attachment #1: Type: text/plain, Size: 878 bytes --]
On 09 Jan 2024 07:33, Tom Tromey wrote:
> >>>>> "Mike" == Mike Frysinger <vapier@gentoo.org> writes:
>
> Mike> While the sim code doesn't utilize HAVE_LONG_LONG itself, other code
> Mike> (like libiberty) seem to, so check for it in the top-level for all
> Mike> ports to leverage.
>
> FWIW gdb solves this problem with gdb/libiberty.m4. Really this is
> something that should be provided or fixed in a better way by libiberty.
in the mean time, seems like this file should get moved to gdbsupport/ since
gdb, gdbserver, and gdbsupport all rely on it ? then it'd be more reasonable
for sim to include that directly.
thinking beyond that, config/acinclude.m4 has CYG_AC_PATH_LIBERTY, but no one
seems to be using that. should we add config/libiberty.m4 and move all this
logic there ? and prob have it take care of exporting a LIBIBERTY_LIB var ?
-mike
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-01-09 17:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-02 5:36 Mike Frysinger
2024-01-02 5:36 ` [PATCH/submitted 02/10] sim: ppc: move struct statfs " Mike Frysinger
2024-01-02 5:36 ` [PATCH/submitted 03/10] sim: ppc: move termio defines to config.h Mike Frysinger
2024-01-02 5:36 ` [PATCH/submitted 04/10] sim: ppc: switch struct member checks to AC_CHECK_MEMBER Mike Frysinger
2024-01-02 5:36 ` [PATCH/submitted 05/10] sim: ppc: switch to AC_CACHE_CHECK Mike Frysinger
2024-01-02 5:36 ` [PATCH/submitted 06/10] sim: ppc: move termios probes to top-level Mike Frysinger
2024-01-02 5:36 ` [PATCH/submitted 07/10] sim: ppc: stop including headers from gdb/ Mike Frysinger
2024-01-02 5:36 ` [PATCH/submitted 08/10] sim: ppc: drop custom config.h header Mike Frysinger
2024-01-02 5:36 ` [PATCH/submitted 09/10] sim: ppc: drop configure compiler checks Mike Frysinger
2024-01-02 5:36 ` [PATCH/submitted 10/10] sim: ppc: move defines.h generation to the top-level Mike Frysinger
2024-01-09 14:33 ` [PATCH/submitted 01/10] sim: ppc: move long long test to top-level Tom Tromey
2024-01-09 17:50 ` Mike Frysinger [this message]
2024-01-09 19:05 ` Tom Tromey
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=ZZ2HWLpSqQGwhe5A@vapier \
--to=vapier@gentoo.org \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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.
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).