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 : update to 5.15.2
Date: Mon, 18 Jan 2021 20:33:38 +0100	[thread overview]
Message-ID: <20210118193338.ZuJ1AUZYjHUL1vK2wr_444Lqr1Dp3_cSrQjhuIcbD-o@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: 1551 bytes --]

New comment by ericonr on void-packages repository

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

Comment:
@yopito there were some more suggestions for some include paths, since clang apparently gets them very wrong. I have yet to try and implement them, see:

```
2021-01-17 22:00:11     q66     -isystem /usr/${XBPS_CROSS_TRIPLET}/usr/include/c++/`${XBPS_CROSS_TRIPLET}-gcc -dumpversion`
2021-01-17 22:00:40     q66     to the flags passed to clang
2021-01-17 22:01:00     ericonr does that manage to find c++config.h?
2021-01-17 22:01:08     ericonr it's in a really weird location
2021-01-17 22:01:28     ericonr like /usr/include/c++/9.3/$triplet
2021-01-17 22:02:27     q66     ah, no it won't
2021-01-17 22:02:31     q66     you'll have to add three paths
2021-01-17 22:03:11     q66     particularly /usr/triplet/usr/include/c++/<ver>, and then also its subdirs <triplet>, and backward
2021-01-17 22:03:57     q66     just add them all with -isystem
2021-01-17 22:04:09     q66     probably something like
2021-01-17 22:04:21     q66     local gcc_ver=`${XBPS_CROSS_TRIPLET}-gcc -dumpversion`
2021-01-17 22:04:26     ericonr by backward do you mean literally "backward"?
2021-01-17 22:04:34     q66     local inc_root=/usr/${XBPS_CROSS_TRIPLET}/usr/include/c++/${gcc_ver}
2021-01-17 22:04:35     q66     and then
2021-01-17 22:04:52     q66     -isystem ${inc_root} -isystem ${inc_root}/${XBPS_CROSS_TRIPLET} -isystem ${inc_root}/backward
```

Also, I believe you should still keep sysroot

  parent reply	other threads:[~2021-01-18 19:33 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
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 [this message]
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=20210118193338.ZuJ1AUZYjHUL1vK2wr_444Lqr1Dp3_cSrQjhuIcbD-o@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).