From: q66 <q66@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: pinebookpro-kernel: fix build w/ gcc10
Date: Sun, 06 Sep 2020 02:13:18 +0200 [thread overview]
Message-ID: <20200906001318.bm4KD5q-Ckt3Mu87ztFk5WgyAT3CXCJrwmRO7J6D_Og@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24699@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1041 bytes --]
New comment by q66 on void-packages repository
https://github.com/void-linux/void-packages/pull/24699#issuecomment-687678976
Comment:
also, there are no issues with `linux5.8-5.8.7` on `aarch64` here (so any config changes must be due to gcc10):
```
=> linux5.8-5.8.7_1: running do_configure ...
=> Detected a .config file for your arch, using it.
HOSTCC scripts/basic/fixdep
HOSTCC scripts/kconfig/conf.o
HOSTCC scripts/kconfig/confdata.o
HOSTCC scripts/kconfig/expr.o
YACC scripts/kconfig/parser.tab.[ch]
LEX scripts/kconfig/lexer.lex.c
HOSTCC scripts/kconfig/preprocess.o
HOSTCC scripts/kconfig/symbol.o
HOSTCC scripts/kconfig/util.o
HOSTCC scripts/kconfig/parser.tab.o
HOSTCC scripts/kconfig/lexer.lex.o
HOSTLD scripts/kconfig/conf
scripts/kconfig/conf --oldconfig Kconfig
#
# configuration written to .config
#
=> linux5.8-5.8.7_1: running pre-build hook: 02-script-wrapper ...
=> linux5.8-5.8.7_1: running do_build ...
scripts/kconfig/conf --syncconfig Kconfig
```
next prev parent reply other threads:[~2020-09-06 0:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-05 17:22 [PR PATCH] " pullmoll
2020-09-05 19:21 ` ericonr
2020-09-05 19:51 ` CameronNemo
2020-09-05 20:19 ` pullmoll
2020-09-05 20:23 ` pullmoll
2020-09-05 20:42 ` pullmoll
2020-09-05 23:58 ` pullmoll
2020-09-06 0:05 ` q66
2020-09-06 0:12 ` q66
2020-09-06 0:13 ` q66 [this message]
2020-09-22 21:19 ` [PR PATCH] [Closed]: " pullmoll
2020-09-30 1:01 ` CameronNemo
2020-09-30 6:10 ` pullmoll
2020-09-30 6:36 ` CameronNemo
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=20200906001318.bm4KD5q-Ckt3Mu87ztFk5WgyAT3CXCJrwmRO7J6D_Og@z \
--to=q66@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).