From: Heinrich Schuchardt <xypron.glpk@gmx.de>
To: lkml <linux-kernel@vger.kernel.org>, linux-mips@linux-mips.org
Cc: Ralf Baechle <ralf@linux-mips.org>,
Paul Burton <paul.burton@imgtec.com>,
James Hogan <james.hogan@imgtec.com>
Subject: Re: cannot build Linux 4.4: arch/mips/kernel/signal.c:142:12: error: ‘struct ucontext’ has no member named ‘uc_extcontext’
Date: Sun, 17 Jan 2016 15:48:27 +0100 [thread overview]
Message-ID: <569BA9BB.3080508@gmx.de> (raw)
In-Reply-To: <569B9CFE.1090007@gmx.de>
On 01/17/2016 02:54 PM, Heinrich Schuchardt wrote:
>
> HEAD is now at afd2ff9... Linux 4.4
> arch/mips/kernel/signal.c: In function ‘sc_to_extcontext’:
> arch/mips/kernel/signal.c:142:12: error: ‘struct ucontext’ has no member
> named ‘uc_extcontext’
> return &uc->uc_extcontext;
> ^
> In file included from include/linux/poll.h:11:0,
> from include/linux/ring_buffer.h:7,
> from include/linux/trace_events.h:5,
> from include/trace/syscall.h:6,
> from include/linux/syscalls.h:81,
> from arch/mips/kernel/signal.c:26:
> arch/mips/kernel/signal.c: In function ‘save_msa_extcontext’:
> arch/mips/kernel/signal.c:170:40: error: dereferencing pointer to
> incomplete type
>
The problem stemmed from make not recognizing that this file was outdated:
Oct 16 2014 arch/mips/include/generated/asm/ucontext.h
Shouldn't make automatically regenerate outdated files?
Best regards
Heinrich Schuchardt
next prev parent reply other threads:[~2016-01-17 14:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-17 13:54 cannot build Linux 4.4: arch/mips/kernel/signal.c:142:12: error: ‘struct ucontext’ has no member named ‘uc_extcontext’ Heinrich Schuchardt
2016-01-17 14:48 ` Heinrich Schuchardt [this message]
2016-01-19 2:22 ` Florian Fainelli
2016-01-19 9:06 ` Ralf Baechle
2016-01-19 10:01 ` James Hogan
2016-01-19 10:01 ` James Hogan
2016-01-19 10:31 ` [PATCH] kbuild: Remove stale asm-generic wrappers James Hogan
2016-01-19 10:31 ` James Hogan
2016-01-19 10:42 ` kbuild test robot
2016-01-19 10:42 ` kbuild test robot
2016-01-19 10:42 ` kbuild test robot
2016-01-19 11:04 ` kbuild test robot
2016-01-19 11:04 ` kbuild test robot
2016-01-19 11:04 ` kbuild test robot
2016-01-19 11:20 ` kbuild test robot
2016-01-19 11:20 ` kbuild test robot
2016-01-19 11:20 ` kbuild test robot
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=569BA9BB.3080508@gmx.de \
--to=xypron.glpk@gmx.de \
--cc=james.hogan@imgtec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=paul.burton@imgtec.com \
--cc=ralf@linux-mips.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.