From: iFoundSilentHouse <iFoundSilentHouse@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [WIP] wine: add aarch64 packaging
Date: Tue, 23 Apr 2024 10:07:16 +0200 [thread overview]
Message-ID: <20240423080716.35382200FB@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49943@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 966 bytes --]
New comment by iFoundSilentHouse on void-packages repository
https://github.com/void-linux/void-packages/pull/49943#issuecomment-2067924157
Comment:
Last build messages
```2024-04-20T23:27:02.1089756Z Stripped library: /usr/lib}/wine/aarch64-unix/wpcap.so
2024-04-20T23:27:02.1385459Z /usr/bin/aarch64-linux-gnu-strip: /destdir/aarch64-linux-gnu/wine-9.6/usr/lib}/wine/aarch64-windows/stFkt5Hx/stWgD4tY/atl.dll: warning: line number table read failed
2024-04-20T23:27:02.1388137Z /usr/bin/aarch64-linux-gnu-strip: /destdir/aarch64-linux-gnu/wine-9.6/usr/lib}/wine/aarch64-windows/stEbrjT4: file truncated
2024-04-20T23:27:02.1412601Z [1m[31m=> ERROR: wine-9.6_2: failed to strip /usr/lib}/wine/aarch64-windows/libatl.a
```
I do need help with:
- [x] Fixing this stripping
- [x] Building wine-tools
OR
- [ ] Add cross-aarch64-mingw -clang/gnu package (aarch64-w64-mingw32-clang/aarch64-w64-mingw32-gcc). Can't find a way to build something like this
next prev parent reply other threads:[~2024-04-23 8:07 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-20 20:47 [PR PATCH] " iFoundSilentHouse
2024-04-20 20:53 ` [PR REVIEW] " classabbyamp
2024-04-20 20:53 ` classabbyamp
2024-04-20 20:53 ` classabbyamp
2024-04-20 20:53 ` classabbyamp
2024-04-20 20:56 ` [PR PATCH] [Updated] " iFoundSilentHouse
2024-04-20 20:56 ` fvalasiad
2024-04-20 21:04 ` [PR REVIEW] " Calandracas606
2024-04-20 21:04 ` iFoundSilentHouse
2024-04-20 21:06 ` fvalasiad
2024-04-20 21:13 ` [PR PATCH] [Updated] " iFoundSilentHouse
2024-04-20 21:17 ` iFoundSilentHouse
2024-04-20 21:24 ` iFoundSilentHouse
2024-04-20 21:34 ` [PR REVIEW] " classabbyamp
2024-04-20 21:35 ` classabbyamp
2024-04-20 21:36 ` iFoundSilentHouse
2024-04-20 21:37 ` iFoundSilentHouse
2024-04-20 21:41 ` [PR PATCH] [Updated] " iFoundSilentHouse
2024-04-20 21:42 ` iFoundSilentHouse
2024-04-20 21:44 ` [PR PATCH] [Updated] " iFoundSilentHouse
2024-04-20 21:45 ` iFoundSilentHouse
2024-04-20 21:45 ` fvalasiad
2024-04-20 21:56 ` iFoundSilentHouse
2024-04-20 22:08 ` fvalasiad
2024-04-20 22:16 ` iFoundSilentHouse
2024-04-20 22:34 ` [PR PATCH] [Updated] " iFoundSilentHouse
2024-04-20 22:36 ` [PR REVIEW] " iFoundSilentHouse
2024-04-20 22:38 ` [PR PATCH] [Updated] " iFoundSilentHouse
2024-04-21 0:01 ` fvalasiad
2024-04-21 5:56 ` Hoshpak
2024-04-21 6:29 ` iFoundSilentHouse
2024-04-21 6:37 ` iFoundSilentHouse
2024-04-21 7:34 ` iFoundSilentHouse
2024-04-21 14:14 ` fvalasiad
2024-04-22 8:23 ` [PR PATCH] [Closed]: " iFoundSilentHouse
2024-04-22 8:23 ` [PR PATCH] [Updated] " iFoundSilentHouse
2024-04-22 8:25 ` iFoundSilentHouse
2024-04-22 10:34 ` iFoundSilentHouse
2024-04-22 10:37 ` [PR PATCH] [Updated] " iFoundSilentHouse
2024-04-22 10:39 ` iFoundSilentHouse
2024-04-22 10:44 ` [PR PATCH] [Updated] " iFoundSilentHouse
2024-04-22 10:49 ` iFoundSilentHouse
2024-04-22 11:53 ` iFoundSilentHouse
2024-04-22 11:54 ` iFoundSilentHouse
2024-04-22 12:09 ` iFoundSilentHouse
2024-04-22 12:09 ` iFoundSilentHouse
2024-04-22 12:10 ` iFoundSilentHouse
2024-04-22 12:12 ` iFoundSilentHouse
2024-04-22 12:13 ` iFoundSilentHouse
2024-04-22 12:17 ` iFoundSilentHouse
2024-04-22 13:24 ` zlice
2024-04-22 13:27 ` zlice
2024-04-22 16:35 ` Hoshpak
2024-04-22 16:49 ` iFoundSilentHouse
2024-04-22 16:50 ` iFoundSilentHouse
2024-04-22 17:01 ` iFoundSilentHouse
2024-04-22 19:52 ` fvalasiad
2024-04-23 8:04 ` [PR PATCH] [Updated] " iFoundSilentHouse
2024-04-23 8:07 ` iFoundSilentHouse [this message]
2024-04-23 8:13 ` iFoundSilentHouse
2024-04-23 9:18 ` iFoundSilentHouse
2024-04-25 17:39 ` iFoundSilentHouse
2024-05-14 3:30 ` zlice
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=20240423080716.35382200FB@inbox.vuxu.org \
--to=ifoundsilenthouse@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).