From: pullmoll <pullmoll@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: crosstoolchain build-style
Date: Tue, 29 Dec 2020 12:20:58 +0100 [thread overview]
Message-ID: <20201229112058.w3P9gtRJ3ACURrOGaVOfdfWu10Isukj8PgezdcdY4hw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27412@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1203 bytes --]
New comment by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/pull/27412#issuecomment-752041351
Comment:
Successfully built all cross compilers for the 4 native architectures.
Noticed there are quite a few more now: all the 32 bit host to 64 bit target compilers.
Still uploading to https://misc.voidlinux.de/binpkgs but already using them to cross compile further packages.
So far looking good. The problems observed have reasons other than the cross compilers.
Most problems are due to missing aclocal-1.16 when packages need to regenerate files because of touched Makefile{,.in,.am} or other parts of the autoconf cruft; issues with wxWidgets and including wx/setup.h; or simply broken / non cross compiling packages.
BTW: I think the `gir` and/or `qemu` build helpers should detect `ppcle{,-musl}` and error out early because there is no `qemu-ppcle-static` and the `XBPS_TARGET_QEMU_MACHINE="ppc"` in the `ppcle.sh` cross profile is wrong anyway. This leads to (big) packages being built only to eventually fail after linking when trying to generate the introspection files. This unnecessarily slows down the try to build as much as possible for ppcle.
next prev parent reply other threads:[~2020-12-29 11:20 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-24 23:54 [PR PATCH] [RFC WIP] " q66
2020-12-25 13:49 ` [PR REVIEW] " pullmoll
2020-12-25 13:49 ` pullmoll
2020-12-25 13:51 ` pullmoll
2020-12-25 14:04 ` q66
2020-12-25 14:36 ` sgn
2020-12-25 14:36 ` sgn
2020-12-25 15:41 ` q66
2020-12-25 15:42 ` q66
2020-12-25 15:50 ` [PR PATCH] [Updated] " q66
2020-12-25 15:51 ` q66
2020-12-25 16:46 ` [PR PATCH] [Updated] " q66
2020-12-25 17:10 ` [PR REVIEW] " q66
2020-12-25 17:11 ` [PR PATCH] [Updated] " q66
2020-12-25 17:25 ` q66
2020-12-25 19:10 ` pullmoll
2020-12-25 19:11 ` pullmoll
2020-12-25 19:12 ` [PR PATCH] [Updated] " q66
2020-12-25 19:15 ` q66
2020-12-25 19:16 ` q66
2020-12-25 19:16 ` pullmoll
2020-12-25 19:18 ` pullmoll
2020-12-25 19:20 ` q66
2020-12-25 19:21 ` q66
2020-12-25 19:22 ` q66
2020-12-25 19:24 ` pullmoll
2020-12-25 19:25 ` pullmoll
2020-12-25 19:28 ` q66
2020-12-25 20:32 ` [PR PATCH] [Updated] " q66
2020-12-25 20:39 ` q66
2020-12-25 23:14 ` q66
2020-12-25 23:29 ` [PR REVIEW] " ericonr
2020-12-25 23:29 ` ericonr
2020-12-26 0:13 ` [PR PATCH] [Updated] " q66
2020-12-26 1:22 ` q66
2020-12-26 18:17 ` q66
2020-12-27 4:27 ` q66
2020-12-27 4:30 ` q66
2020-12-27 4:50 ` [PR PATCH] [Updated] " q66
2020-12-27 13:01 ` [PR REVIEW] " pullmoll
2020-12-27 17:13 ` [PR PATCH] [Updated] " q66
2020-12-28 12:53 ` [PR REVIEW] " pullmoll
2020-12-28 12:54 ` pullmoll
2020-12-28 12:56 ` pullmoll
2020-12-28 13:46 ` [PR PATCH] [Updated] " q66
2020-12-28 13:47 ` q66
2020-12-28 13:53 ` [PR PATCH] [Updated] " q66
2020-12-28 14:09 ` [PR REVIEW] " sgn
2020-12-28 14:22 ` sgn
2020-12-28 14:24 ` sgn
2020-12-28 14:26 ` sgn
2020-12-28 19:01 ` pullmoll
2020-12-28 19:43 ` pullmoll
2020-12-28 20:05 ` pullmoll
2020-12-28 20:18 ` pullmoll
2020-12-28 20:24 ` pullmoll
2020-12-28 20:48 ` ericonr
2020-12-29 11:20 ` pullmoll [this message]
2020-12-29 11:22 ` pullmoll
2020-12-29 22:10 ` pullmoll
2020-12-29 22:48 ` q66
2020-12-29 23:24 ` pullmoll
2020-12-29 23:26 ` [PR PATCH] [Updated] " q66
2020-12-29 23:29 ` q66
2020-12-29 23:42 ` [PR PATCH] [Updated] " q66
2020-12-29 23:44 ` q66
2020-12-31 0:35 ` fosslinux
2020-12-31 22:48 ` [PR PATCH] [Merged]: " q66
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=20201229112058.w3P9gtRJ3ACURrOGaVOfdfWu10Isukj8PgezdcdY4hw@z \
--to=pullmoll@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).