From: Thorsten Otto <admin@tho-otto.de>
To: dash@vger.kernel.org
Subject: Signal names when cross-compiling
Date: Wed, 04 Oct 2023 09:48:49 +0200 [thread overview]
Message-ID: <19502212.sIn9rWBj0N@earendil> (raw)
Hi,
when cross-compiling dash, signames.c is generated by a mksignames that was
compiled for the host. This will generate wrong signal mappings because
obviously this will use the signal numbers of the build system, not the
target.
I currently dont't have no idea how to solve that, other than populating the
signal_names array at runtime rather than compile time.
next reply other threads:[~2023-10-04 7:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 7:48 Thorsten Otto [this message]
2023-10-04 17:43 ` Signal names when cross-compiling Steffen Nurpmeso
2023-10-04 19:45 ` Kuhl, Brian
2023-10-04 20:16 ` Steffen Nurpmeso
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=19502212.sIn9rWBj0N@earendil \
--to=admin@tho-otto.de \
--cc=dash@vger.kernel.org \
/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