Github messages for voidlinux
 help / color / mirror / Atom feed
From: pullmoll <pullmoll@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Tracking: rebuild armv7l-musl w/ musl-1.20.1
Date: Sun, 29 Nov 2020 23:48:44 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26811@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1705 bytes --]

New issue by pullmoll on void-packages repository

https://github.com/void-linux/void-packages/issues/26811

Description:
Based on @ericonr 's branch [musl-1.20.0](https://github.com/ericonr/void-packages/tree/musl-1.2.0), which now really is for musl-1.20.1, I found a patch to get `cross-armv7l-linux-musleabihf` built:
`srcpkgs/cross-armv7l-linux-musleabihf/patches/fix-_stat-sed,patch`
```
--- gcc-9.3.0/libgo/mksysinfo.sh        2020-11-29 23:07:46.793838127 +0100
+++ gcc-9.3.0/libgo/mksysinfo.sh        2020-11-29 23:27:18.520794067 +0100
@@ -506,9 +506,9 @@
          -e 's/st_size/Size/' \
          -e 's/st_blksize/Blksize/' \
          -e 's/st_blocks/Blocks/' \
-         -e 's/st_atim/Atim/' \
-         -e 's/st_mtim/Mtim/' \
-         -e 's/st_ctim/Ctim/' \
+         -e 's/st_atim/Atim/g' \
+         -e 's/st_mtim/Mtim/g' \
+         -e 's/st_ctim/Ctim/g' \
          -e 's/\([^a-zA-Z0-9_]\)_timeval\([^a-zA-Z0-9_]\)/\1Timeval\2/g' \
          -e 's/\([^a-zA-Z0-9_]\)_timespec_t\([^a-zA-Z0-9_]\)/\1Timespec\2/g' \
          -e 's/\([^a-zA-Z0-9_]\)_st_timespec_t\([^a-zA-Z0-9_]\)/\1StTimespec\2/g' \
```

So basically the replacement needs to take place on the entire line. This is because before the `st_atim` etc. there is a `__st_atim32` which is replaced and the `sed` is done without modifying the interesting `st_atim` which follows.

Perhaps you @ericonr can update the branch to upstream master once more?
And we should integrate this patch with `gcc` and use the `cross-*-musl/files/something.patch` symbolic links to the `gcc/patches/something.patch` style for it.

I think I could now build all packages for `armv7l-musl` which will take about 2 days.

             reply	other threads:[~2020-11-29 22:48 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-29 22:48 pullmoll [this message]
2020-11-30  0:18 ` pullmoll
2020-11-30  0:21 ` pullmoll
2020-11-30  0:27 ` pullmoll
2020-11-30  6:15 ` pullmoll
2020-11-30 12:49 ` Tracking: rebuild armv7l-musl w/ musl-1.2.1 pullmoll
2020-11-30 12:52 ` pullmoll
2020-11-30 12:59 ` pullmoll
2020-11-30 13:01 ` pullmoll
2020-11-30 15:29 ` pullmoll
2020-11-30 18:30 ` pullmoll
2020-11-30 20:08 ` pullmoll
2020-12-01 17:15 ` pullmoll
2020-12-04  3:16 ` fosslinux
2020-12-04 13:55 ` pullmoll
2020-12-07 22:19 ` pullmoll
2020-12-14 16:33 ` pullmoll
2020-12-15 19:51 ` pullmoll
2020-12-15 19:51 ` [ISSUE] [CLOSED] " pullmoll

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26811@inbox.vuxu.org \
    --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).