From: James Hogan <james.hogan@imgtec.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Heinrich Schuchardt <xypron.glpk@gmx.de>,
lkml <linux-kernel@vger.kernel.org>, <linux-mips@linux-mips.org>,
Ralf Baechle <ralf@linux-mips.org>,
Paul Burton <paul.burton@imgtec.com>,
<linux-kbuild@vger.kernel.org>, Michal Marek <mmarek@suse.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: Tue, 19 Jan 2016 10:01:55 +0000 [thread overview]
Message-ID: <20160119100154.GJ30608@jhogan-linux.le.imgtec.org> (raw)
In-Reply-To: <569D9DDD.7080909@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2828 bytes --]
Hi Florian,
On Mon, Jan 18, 2016 at 06:22:21PM -0800, Florian Fainelli wrote:
> Le 17/01/2016 06:48, Heinrich Schuchardt a écrit :
> > 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?
>
> The reduced test case can be simplified to these steps:
>
> git co f1fe2d21f4e1aca8644cea888dc618f0183ad671\^1
> configure your kernel
> ARCH=mips make arch/mips/kernel/signal.o
> git co f1fe2d21f4e1aca8644cea888dc618f0183ad671
> ARCH=mips make arch/mips/kernel/signal.o
>
> The problem seems to be that if there was a previous build which
> resulted in creating an asm-generic wrapper for a file
> (arch/mips/include/generated/asm/ucontext.h in that case), but this file
> was later moved into an arch-specific, non asm-generic header file, then
> we are just not going to automatically remove this auto-generated
> wrapper, and generate the new one.
>
> This seems to be aggravated by the fact that commit
> f1fe2d21f4e1aca8644cea888dc618f0183ad671 does not add ucontext.h to
> arch/mips/include/uapi/Kbuild, Paul, James is that intentional?
I suspect it was intended to be exported in kernel headers, for
libc/signal handlers to use, although it isn't referenced by other
headers. Paul?
>
> After trying to mess a bit with a clean solution, I just gave up and
> decided that this was not worth fixing since it is a very infrequent
> problem.
Thing is it isn't that uncommon. I've lost count of the number of times
I've hit this specific case (especially during bisection), and as Ralf
says, several others have mentioned it on the list, but rm -fr
arch/mips/include/generated always seemed so much easier than fixing
the actual problem.
Anyway, after a bit of fiddling around I think i've fixed this properly
now. I'll submit the patch asap.
Cheers
James
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-01-19 10:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-17 13:54 Heinrich Schuchardt
2016-01-17 14:48 ` Heinrich Schuchardt
2016-01-19 2:22 ` Florian Fainelli
2016-01-19 9:06 ` Ralf Baechle
2016-01-19 10:01 ` James Hogan [this message]
2016-01-19 10:31 ` [PATCH] kbuild: Remove stale asm-generic wrappers James Hogan
2016-01-19 10:42 ` kbuild test robot
2016-01-19 11:04 ` 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=20160119100154.GJ30608@jhogan-linux.le.imgtec.org \
--to=james.hogan@imgtec.com \
--cc=f.fainelli@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=mmarek@suse.com \
--cc=paul.burton@imgtec.com \
--cc=ralf@linux-mips.org \
--cc=xypron.glpk@gmx.de \
/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
Powered by JetHome