From: zoran.stojsavljevic.de@gmail.com (Zoran S)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] powerpc build with Kernel v4.4
Date: Sun, 28 Jul 2019 06:22:17 +0200 [thread overview]
Message-ID: <CAEss1E+JD=vvXDAsz-tpisBsCAGnwbxnRNaiWJb9f+eJ+3+68A@mail.gmail.com> (raw)
In-Reply-To: <TYAPR01MB2285895BCD78ABB88C823A5DB7C30@TYAPR01MB2285.jpnprd01.prod.outlook.com>
Quick ad-hoc observation:
[1] From https://gitlab.com/cip-project/cip-kernel/linux-cip/-/jobs/260410825
> /opt/build_kernel.sh: line 123: [: /opt/cip-kernel-config/4.4/powerpc/toshiba_defconfig: unary operator expected
Interesting line...WTH is wrong with the line 123 (CONFIG_SPI_DEBUG=y)?
[2] From https://lkml.org/lkml/2019/2/27/106
On Tue, Feb 26, 2019 at 09:29:40AM -0800, Guenter Roeck wrote:
> In function ?user_regset_copyin?,
> inlined from ?vr_set? at arch/powerpc/kernel/ptrace.c:490:9:
> include/linux/regset.h:258:4: error:
> ?memcpy? offset [-527, -529] is out of the bounds [0, 16] of object ?vrsave?
> with type ?union <anonymous>?
>
> The problem is not new. It is seen now because I switched to use
> gcc 8.3.0. The problem is fixed in linux-next.
You should contact Guenter Roeck and ask him about the following:
> The problem is not new. It is seen now because I switched to use
> gcc 8.3.0. The problem is fixed in linux-next.
Stress on: "The problem is fixed in linux-next".
My two cent worth thinking,
Zoran
_______
On Sat, Jul 27, 2019 at 11:29 PM Chris Paterson
<Chris.Paterson2@renesas.com> wrote:
>
> Hello all,
>
> I'm trying to build the toshiba_defconfig [1] for the powerpc architecture using the CIP v4.4 Kernel but I'm hitting some problems. The log from the build can be seen on GitLab [2].
>
> Has anyone tried building this configuration recently?
>
> I'm using gcc compiler v8.1.0. I mention this because I've see a half-related discussion [3] when Googling. From this mail thread I wonder if there are some patches we need to backport?
>
>
> [1] https://gitlab.com/cip-project/cip-kernel/cip-kernel-config/blob/master/4.4/powerpc/toshiba_defconfig
> [2] https://gitlab.com/cip-project/cip-kernel/linux-cip/-/jobs/260410825
> [3] https://lkml.org/lkml/2019/2/27/106
>
> Kind regards, Chris
>
> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev
next prev parent reply other threads:[~2019-07-28 4:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-27 21:29 [cip-dev] powerpc build with Kernel v4.4 Chris Paterson
2019-07-28 4:22 ` Zoran S [this message]
2019-07-30 12:54 ` Chris Paterson
2019-07-28 7:40 ` Pavel Machek
2019-07-28 8:49 ` Pavel Machek
2019-07-30 13:01 ` Chris Paterson
2019-07-30 14:30 ` Zoran S
2019-07-30 14:41 ` Chris Paterson
2019-07-31 6:23 ` Zoran S
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='CAEss1E+JD=vvXDAsz-tpisBsCAGnwbxnRNaiWJb9f+eJ+3+68A@mail.gmail.com' \
--to=zoran.stojsavljevic.de@gmail.com \
--cc=cip-dev@lists.cip-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.