linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Mar 3
Date: Thu, 3 Mar 2016 04:04:52 -0800	[thread overview]
Message-ID: <56D82864.6030904@roeck-us.net> (raw)
In-Reply-To: <20160303105910.GA2652@sudip-pc>

On 03/03/2016 03:00 AM, Sudip Mukherjee wrote:
> On Thu, Mar 03, 2016 at 05:09:26PM +1100, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20160302:
>
> With next-20160301 and next-20160302 I am having problem in allmodconfig
> build of x86_64. The error being:
>
> In file included from builtin-check.c:32:0:
> elf.h:22:18: fatal error: gelf.h: No such file or directory
> compilation terminated.
> In file included from elf.c:30:0:
> elf.h:22:18: fatal error: gelf.h: No such file or directoryIn file
> included from special.h:22:0,
> 	                  from special.c:26:
> elf.h:22:18: fatal error: gelf.h: No such file or directory
> compilation terminated.
>
> I have intsalled libelf-dev and now make allmodconfig && make -j8 works
> but if I am trying make O=nextbuild allmodconfig && make O=nextbuild -j8
> it again fails with the error:
> scripts/Makefile.include:3: *** O=nextbuild does not exist.  Stop.
>
> But this has been my normal workflow and I do have a valid directory
> called nextbuild.
>
> Am i the only one hitting this error? Do i need to bisect or it is a
> known issue?
>

Same problem here.

Guenter

  parent reply	other threads:[~2016-03-03 12:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-03  6:09 linux-next: Tree for Mar 3 Stephen Rothwell
2016-03-03 11:00 ` Sudip Mukherjee
2016-03-03 11:18   ` Sudip Mukherjee
2016-03-03 14:35     ` Josh Poimboeuf
2016-03-03 14:53       ` [PATCH] tools: Support relative directory path for 'O=' Josh Poimboeuf
2016-03-03 17:39       ` [PATCH] objtool: Warn if libelf is missing Josh Poimboeuf
2016-03-03 12:04   ` Guenter Roeck [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-03  2:16 linux-next: Tree for Mar 3 Stephen Rothwell
2022-03-03  9:20 Stephen Rothwell
2021-03-03  2:04 Stephen Rothwell
2020-03-03  7:01 Stephen Rothwell
2017-03-03  2:17 Stephen Rothwell
2015-03-03  6:08 Stephen Rothwell
2014-03-03  9:07 Stephen Rothwell

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=56D82864.6030904@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --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;
as well as URLs for NNTP newsgroup(s).