Linux-Next discussions
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Peter Foley <pefoley2@pefoley.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the rd-docs tree
Date: Wed, 17 Sep 2014 09:00:20 +1000	[thread overview]
Message-ID: <20140917090020.1f3c2c30@canb.auug.org.au> (raw)
In-Reply-To: <CAOFdcFMDnR50cS-Geb0S1S2VRPzZqDr9zzqUp-DpMYLfF0qtvQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 690 bytes --]

Hi Peter,

On Tue, 16 Sep 2014 13:19:07 -0400 Peter Foley <pefoley2@pefoley.com> wrote:
>
> On Tue, Sep 16, 2014 at 3:11 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > After merging the rd-docs tree, today's linux-next build (powerpc
> > allyesconfig) failed like this:
> >
> > Documentation/vDSO/vdso_test.c:15:22: fatal error: sys/auxv.h: No such file or directory
> >
> 
> What glibc version are you running?
> It appears the function getauxval (and I assume the missing header)
> were only added in glibc 2.16.

My build machine runs Debian stable which only has libc6 version 2.13.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2014-09-16 23:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-16  7:11 linux-next: build failure after merge of the rd-docs tree Stephen Rothwell
2014-09-16 17:19 ` Peter Foley
2014-09-16 23:00   ` Stephen Rothwell [this message]
2014-09-16 23:18     ` Peter Foley
2014-09-16 23:38       ` Randy Dunlap
2014-09-17  0:02         ` Peter Foley

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=20140917090020.1f3c2c30@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=pefoley2@pefoley.com \
    --cc=rdunlap@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox