public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	uml-devel <user-mode-linux-devel@lists.sourceforge.net>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Michael Ellerman <michael@ellerman.id.au>
Subject: Re: [uml-devel] Build regressions/improvements in v3.18-rc4
Date: Wed, 12 Nov 2014 11:25:51 +0100	[thread overview]
Message-ID: <546335AF.7030301@nod.at> (raw)
In-Reply-To: <CAMuHMdWP=9c4w2-H1QGT37qePZzZ8TL-vGuCRB00CH6+60LZkA@mail.gmail.com>

Am 12.11.2014 um 11:22 schrieb Geert Uytterhoeven:
> On Wed, Nov 12, 2014 at 11:19 AM, Richard Weinberger
> <richard.weinberger@gmail.com> wrote:
>>>   + /home/kisskb/slave/src/fs/hostfs/hostfs_user.c: error: 'AT_FDCWD'
>>> undeclared (first use in this function):  => 378
>>>   + /home/kisskb/slave/src/fs/hostfs/hostfs_user.c: error: (Each
>>> undeclared identifier is reported only once:  => 378
>>>   + /home/kisskb/slave/src/fs/hostfs/hostfs_user.c: error: for each
>>> function it appears in.):  => 378
>>
>> I've never seen this failure.
>> Both 3.18-rc3/4 x86_64/i386 build fine here.
>>
>> What toolchain are you using?
>> It looks like AT_FDCWD is missing on your host side.
> 
> There's obviously more wrong with the host side:
> http://kisskb.ellerman.id.au/kisskb/buildresult/12305953/

Hmm, I bet this is a x86 cross-toolchain with horrible
outdated linux-headers.

Thanks,
//richard

      reply	other threads:[~2014-11-12 10:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-12  9:46 Build regressions/improvements in v3.18-rc4 Geert Uytterhoeven
2014-11-12  9:48 ` Geert Uytterhoeven
2014-11-12 10:19   ` [uml-devel] " Richard Weinberger
2014-11-12 10:22     ` Geert Uytterhoeven
2014-11-12 10:25       ` Richard Weinberger [this message]

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=546335AF.7030301@nod.at \
    --to=richard@nod.at \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael@ellerman.id.au \
    --cc=sfr@canb.auug.org.au \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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