From: Eric Sandeen <sandeen@sandeen.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: David Chinner <david@fromorbit.com>,
xfs-masters@oss.sgi.com, linux-next@vger.kernel.org,
Christoph Hellwig <hch@lst.de>, Lachlan McIlroy <lachlan@sgi.com>
Subject: Re: linux-next: xfs tree build failure
Date: Wed, 03 Dec 2008 23:20:10 -0600 [thread overview]
Message-ID: <4937688A.9030607@sandeen.net> (raw)
In-Reply-To: <20081204101612.ec0d4d7c.sfr@canb.auug.org.au>
Stephen Rothwell wrote:
> Hi David,
>
> The build of next-20081203 (sh titan_defconfig, powerpc ppc6xx_defconfig,
> mips defconfig, m68k defconfig and others) failed like this:
>
> In file included from fs/xfs/linux-2.6/xfs_file.c:40:
> fs/xfs/linux-2.6/xfs_ioctl32.h:50: error: expected specifier-qualifier-list before 'compat_time_t'
> fs/xfs/linux-2.6/xfs_ioctl32.h:79: error: expected specifier-qualifier-list before 'compat_uptr_t'
> fs/xfs/linux-2.6/xfs_ioctl32.h:94: error: expected specifier-qualifier-list before 'compat_uptr_t'
> fs/xfs/linux-2.6/xfs_ioctl32.h:131: error: expected specifier-qualifier-list before 'compat_uptr_t'
> fs/xfs/linux-2.6/xfs_ioctl32.h:142: error: expected specifier-qualifier-list before 'compat_uptr_t'
> fs/xfs/linux-2.6/xfs_ioctl32.h:152: error: expected specifier-qualifier-list before 'compat_uptr_t'
> fs/xfs/linux-2.6/xfs_ioctl32.h:161: error: expected specifier-qualifier-list before 'compat_uptr_t'
>
> a and few other errors depending on which arch and config.
>
> I have dropped the xfs tree for today.
My fault, grr. Christoph sent a patch to fix it which had a problem of
its own, but the sgi guys know about it all and a fix should be in their
tree soon. Sorry about that!
Thanks,
-Eric
next prev parent reply other threads:[~2008-12-04 5:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 23:16 linux-next: xfs tree build failure Stephen Rothwell
2008-12-04 5:20 ` Eric Sandeen [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-09-02 1:25 Stephen Rothwell
2009-09-02 1:28 ` Christoph Hellwig
2009-09-02 1:54 ` Felix Blyakher
2009-09-02 2:00 ` Stephen Rothwell
2009-07-03 0:05 Stephen Rothwell
2009-03-10 2:45 Stephen Rothwell
2009-03-11 22:52 ` Dave Chinner
2009-03-12 1:04 ` Stephen Rothwell
2009-03-15 12:18 ` Dave Chinner
2008-10-30 2:23 Stephen Rothwell
2008-10-30 9:08 ` Dave Chinner
2008-11-05 2:20 ` Stephen Rothwell
2008-11-05 20:47 ` Dave Chinner
2008-11-06 15:27 ` Christoph Hellwig
2008-11-07 5:06 ` Stephen Rothwell
2008-11-11 2:05 ` Lachlan McIlroy
2008-11-11 2:11 ` 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=4937688A.9030607@sandeen.net \
--to=sandeen@sandeen.net \
--cc=david@fromorbit.com \
--cc=hch@lst.de \
--cc=lachlan@sgi.com \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=xfs-masters@oss.sgi.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).