Github messages for voidlinux
 help / color / mirror / Atom feed
From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [WIP] Qt pyside 5.15.2
Date: Sat, 26 Dec 2020 20:57:02 +0100	[thread overview]
Message-ID: <20201226195702.iviomPtb37X4cBtEd7-dDOMXamDjE4tSTm17vN_PEnQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26962@inbox.vuxu.org>

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

New comment by ericonr on void-packages repository

https://github.com/void-linux/void-packages/pull/26962#issuecomment-751390575

Comment:
From IRC, about the issue with stubs-soft:

```
16:47 <q66> [q66@/home/q66/.xbps-src/masterdir-ppc64le /]$ clang -target armv7l-linux-gnueabihf -dM -E - < /dev/null|grep ARM_PCS_VFP
16:47 <q66> #define __ARM_PCS_VFP 1
16:47 <q66> bu that should also work by default
16:47 <q66> ohhhh
16:47 <q66> that gives me an idea
16:47 <q66> it's probably running clang, but for host
16:48 <ericonr> oh that would definitely explain it
16:48 <q66> i.e. target triplet is not passed to clang and as a result it does not have arm macros and fails to use the headers properly
```

Regarding armv6l, imo we can just use

```
if [ "$XBPS_TARGET_NO_ATOMIC8" ]; then
	broken="Requires 8-byte atomics"
fi
```

in the template, and then add the packages that will have to be removed to #23575 

  parent reply	other threads:[~2020-12-26 19:57 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-05 13:27 [PR PATCH] [WIP] Qt pyside 5.12.2 yopito
2020-12-05 22:49 ` ericonr
2020-12-05 23:18 ` ericonr
2020-12-05 23:19 ` ericonr
2020-12-06  9:06 ` yopito
2020-12-19 15:48 ` [PR PATCH] [Updated] [WIP] Qt pyside 5.15.2 yopito
2020-12-19 16:18 ` yopito
2020-12-19 17:53 ` yopito
2020-12-19 17:55 ` yopito
2020-12-20 10:43 ` [PR PATCH] [Updated] " yopito
2020-12-20 12:33 ` yopito
2020-12-20 12:35 ` yopito
2020-12-26  4:58 ` sgn
2020-12-26  5:10 ` ericonr
2020-12-26 11:13 ` yopito
2020-12-26 19:57 ` ericonr [this message]
2021-01-16 20:06 ` [PR PATCH] [Updated] " yopito
2021-01-16 20:14 ` yopito
2021-01-17  0:33 ` Qt pyside : update to 5.15.2 yopito
2021-01-17  1:27 ` ericonr
2021-01-17  3:11 ` q66
2021-01-17 10:27 ` yopito
2021-01-17 19:06 ` [WIP] " ericonr
2021-01-17 19:25 ` ericonr
2021-01-17 19:26 ` ericonr
2021-01-17 19:50 ` yopito
2021-01-17 20:01 ` ericonr
2021-01-17 20:04 ` ericonr
2021-01-18  0:27 ` ericonr
2021-01-18 19:29 ` yopito
2021-01-18 19:33 ` ericonr
2021-01-22 18:40 ` yopito
2021-01-22 18:51 ` yopito
2021-01-23 18:59 ` [PR PATCH] [Updated] " yopito
2021-01-23 22:35 ` yopito
2021-01-24  8:19 ` yopito
2021-01-26 21:22 ` [PR REVIEW] " ericonr
2021-01-26 21:38 ` q66
2021-01-26 22:46 ` yopito
2021-01-26 23:16 ` ericonr
2021-01-26 23:43 ` sgn
2021-01-27 19:10 ` [PR PATCH] [Updated] " yopito
2021-01-27 19:14 ` [PR REVIEW] " yopito
2021-01-27 22:15 ` ericonr
2021-01-27 22:55 ` [PR PATCH] [Updated] " yopito
2021-01-27 22:55 ` [PR REVIEW] " yopito
2021-01-28  0:15 ` q66
2021-01-28  3:33 ` [PR PATCH] [Closed]: " ericonr

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=20201226195702.iviomPtb37X4cBtEd7-dDOMXamDjE4tSTm17vN_PEnQ@z \
    --to=ericonr@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).