From: Tom de Vries <tdevries@suse.de>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb/build] Fix build on postmarketos
Date: Thu, 14 Mar 2024 17:32:56 +0100 [thread overview]
Message-ID: <57c12445-8c2b-4883-b3dd-2f7395427e39@suse.de> (raw)
In-Reply-To: <87zfv1kmqm.fsf@tromey.com>
On 3/14/24 13:43, Tom Tromey wrote:
>>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
>
> Tom> I tried building gdbserver on postmarketos (which is based on alpine linux,
> Tom> which uses musl libc), and ran into:
> Tom> ...
> Tom> gdbserver/linux-low.cc: In lambda function:
> Tom> gdbserver/linux-low.cc:1907:41: error: \
> Tom> 'W_EXITCODE' was not declared in this scope
> Tom> 1907 | mark_lwp_dead (leader_lp, W_EXITCODE (0, 0), true);
> Tom> | ^~~~~~~~~~
> Tom> ...
>
> Tom> The macro W_EXITCODE is not defined in gdbsupport/gdb_wait.h, but WSETEXIT is:
> Tom> ...
> Tom> /* These are not defined in POSIX, but are used by our programs. */
>
> Tom> #ifndef WSETEXIT
> Tom> # ifdef W_EXITCODE
> Tom> #define WSETEXIT(w,status) ((w) = W_EXITCODE(status,0))
> Tom> # else
> Tom> #define WSETEXIT(w,status) ((w) = (0 | ((status) << 8)))
> Tom> # endif
> Tom> #endif
> Tom> ...
>
> I think it'd be better to change this to define W_EXITCODE.
> WSETEXIT isn't used in the tree at all AFAICT.
Thanks for the review.
Fine by me, I've submitted a v2 here (
https://sourceware.org/pipermail/gdb-patches/2024-March/207288.html ).
Thanks,
- Tom
prev parent reply other threads:[~2024-03-14 16:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-14 9:54 Tom de Vries
2024-03-14 12:43 ` Tom Tromey
2024-03-14 16:32 ` Tom de Vries [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=57c12445-8c2b-4883-b3dd-2f7395427e39@suse.de \
--to=tdevries@suse.de \
--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).