public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Markos Chandras <Markos.Chandras@imgtec.com>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
	Ralf Baechle <ralf@linux-mips.org>
Cc: <linux-kernel@vger.kernel.org>,
	Alex Smith <alex.smith@imgtec.com>,
	Matthew Fortune <matthew.fortune@imgtec.com>
Subject: Re: [PATCH] MIPS: fix build failure
Date: Wed, 28 Oct 2015 10:31:24 +0000	[thread overview]
Message-ID: <5630A3FC.9030007@imgtec.com> (raw)
In-Reply-To: <5630A0DC.4080700@imgtec.com>

On 10/28/2015 10:18 AM, Markos Chandras wrote:
> On 10/28/2015 10:08 AM, Sudip Mukherjee wrote:
>> While building for mips defconfig the build failed with the error:
>> In function 'create_elf_tables':
>> arch/mips/include/asm/elf.h:425:14: error: 
>> 'AT_SYSINFO_EHDR' undeclared (first use in this function)
>>
>> AT_SYSINFO_EHDR is defined in uapi/asm/auxvec.h which was not included
>> here.
>>
>> Fixes: c1fb442ade67 ("MIPS: Initial implementation of a VDSO")
>> Signed-off-by: Sudip Mukherjee <sudip@vectorindia.org>
>> ---
>>
>> This patch is based on mips-for-linux-next branch.
>>
> 
> Something is not right here. The <linux/auxvec.h> header is already
> included in that file which in turns includes uapi/asm/auxvec.h
> 
> I haven't seen this failure in Ralf's tree. Could you share your .config
> and perhaps the hash of the mips-for-linux-next tree you tried it on?
> 
> 
I believe your problem might be similar to this

https://www.linux-mips.org/archives/linux-mips/2015-10/msg00280.html

in other words either remove the generated headers or do a 'make
mrproper' (make sure to backup your .config) and try again

-- 
markos

  reply	other threads:[~2015-10-28 10:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-28 10:08 [PATCH] MIPS: fix build failure Sudip Mukherjee
2015-10-28 10:18 ` Markos Chandras
2015-10-28 10:31   ` Markos Chandras [this message]
2015-10-28 10:48     ` Sudip Mukherjee

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=5630A3FC.9030007@imgtec.com \
    --to=markos.chandras@imgtec.com \
    --cc=alex.smith@imgtec.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew.fortune@imgtec.com \
    --cc=ralf@linux-mips.org \
    --cc=sudipm.mukherjee@gmail.com \
    /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