From: Chocimier <Chocimier@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New packages: datovka-4.21.1, libdatovka-0.2.1
Date: Tue, 10 Jan 2023 23:04:39 +0100 [thread overview]
Message-ID: <20230110220439.fS1P6bPblEzE81mAKGrGR14besL6YcVI5Q8WY6KCGUs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41566@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 885 bytes --]
New comment by Chocimier on void-packages repository
https://github.com/void-linux/void-packages/pull/41566#issuecomment-1377953590
Comment:
Please split `-devel` from library. `-devel`s go to makedepends, library needs gettext-devel-tools in hostmakedepends, application needs qt5-host-tools, then it cross-compiles. On musl it still fails with
> aarch64-linux-musl-c++ -c -g -O0 -std=c++11 -O2 -Wall -Wextra -fPIC -I. -I/usr/aarch64-linux-musl/usr/include/libxml2 -I../../.target-spec/linux-g++ -o main.o main.cpp
> In file included from main.cpp:11:
> /usr/aarch64-linux-musl/usr/include/libdatovka/isds.h:442:5: error: '_Bool' does not name a type; did you mean 'UBool'?
> 442 | _Bool *dbEffectiveOVM; /* Box has OVM role (§ 5a) */
discussed at <https://www.openwall.com/lists/musl/2017/07/28/1>, concluding that C and C++ polyglot headers are hard.
next prev parent reply other threads:[~2023-01-10 22:04 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 20:15 [PR PATCH] " realcharmer
2023-01-10 20:23 ` [PR PATCH] [Updated] " realcharmer
2023-01-10 20:26 ` realcharmer
2023-01-10 20:35 ` realcharmer
2023-01-10 21:58 ` kruceter
2023-01-10 21:59 ` kruceter
2023-01-10 22:04 ` Chocimier [this message]
2023-01-11 16:23 ` [PR PATCH] [Updated] " realcharmer
2023-01-11 16:41 ` realcharmer
2023-01-11 16:44 ` realcharmer
2023-01-11 16:52 ` realcharmer
2023-01-11 16:56 ` kruceter
2023-01-11 16:58 ` realcharmer
2023-01-11 17:02 ` [PR PATCH] [Updated] " realcharmer
2023-01-11 17:10 ` [PR REVIEW] " kruceter
2023-01-11 17:10 ` kruceter
2023-01-11 17:11 ` [PR PATCH] [Updated] " realcharmer
2023-01-11 17:12 ` [PR REVIEW] " realcharmer
2023-01-11 17:13 ` [PR PATCH] [Updated] " realcharmer
2023-01-11 17:15 ` realcharmer
2023-01-11 18:31 ` [PR REVIEW] " kruceter
2023-01-11 18:31 ` kruceter
2023-01-11 19:14 ` [PR PATCH] [Updated] " realcharmer
2023-01-11 19:15 ` [PR REVIEW] " realcharmer
2023-01-19 18:32 ` realcharmer
2023-02-21 14:24 ` [PR PATCH] [Updated] " realcharmer
2023-02-21 14:25 ` realcharmer
2023-02-21 14:31 ` [PR PATCH] [Updated] New packages: datovka-4.22.0, libdatovka-0.3.0 realcharmer
2023-02-21 14:33 ` realcharmer
2023-04-02 17:18 ` [PR PATCH] [Updated] " realcharmer
2023-05-30 14:12 ` realcharmer
2023-05-30 14:13 ` realcharmer
2023-06-19 10:22 ` [PR PATCH] [Updated] New packages: datovka-4.22.1, libdatovka-0.3.0 realcharmer
2023-06-19 10:23 ` realcharmer
2023-06-19 10:23 ` realcharmer
2023-09-18 1:45 ` github-actions
2023-09-20 10:00 ` [PR PATCH] [Updated] " realcharmer
2023-09-20 10:01 ` realcharmer
2023-09-20 10:11 ` [PR PATCH] [Updated] New packages: datovka-4.22.1, libdatovka-0.4.0 realcharmer
2023-09-20 10:11 ` realcharmer
2023-11-09 11:28 ` [PR PATCH] [Updated] " realcharmer
2023-11-09 14:40 ` [PR PATCH] [Updated] New packages: datovka-4.22.1, libdatovka-0.5.1 realcharmer
2023-11-09 14:41 ` realcharmer
2023-12-14 21:37 ` [PR PATCH] [Updated] " realcharmer
2023-12-14 21:37 ` New packages: datovka-4.23.1, libdatovka-0.5.1 realcharmer
2024-03-14 1:44 ` github-actions
2024-03-22 12:34 ` [PR PATCH] [Updated] " realcharmer
2024-03-22 12:44 ` realcharmer
2024-03-22 12:45 ` realcharmer
2024-04-25 11:12 ` [PR PATCH] [Updated] New packages: datovka-4.23.6, libdatovka-0.6.2 realcharmer
2024-04-25 11:13 ` New packages: datovka-4.23.7, libdatovka-0.6.2 realcharmer
2024-04-25 11:14 ` [PR PATCH] [Updated] " realcharmer
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=20230110220439.fS1P6bPblEzE81mAKGrGR14besL6YcVI5Q8WY6KCGUs@z \
--to=chocimier@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).