public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Axel Siebenwirth <axel@pearbough.net>
Cc: linux-kernel@vger.kernel.org, aia21@cantab.net
Subject: Re: 2.6.2-rc1-mm1
Date: Thu, 22 Jan 2004 13:34:53 -0800	[thread overview]
Message-ID: <20040122133453.1932eae0.akpm@osdl.org> (raw)
In-Reply-To: <20040122132044.GA18954@neon>

Axel Siebenwirth <axel@pearbough.net> wrote:
>
> Hi!
> 
> On Thu, 22 Jan 2004, Andrew Morton wrote:
> 
> > 
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.2-rc1/2.6.2-rc1-mm1/
> > 
> > 
> > - Nothing very exciting, just lots of random fixes.
> > 
> > - The x86 gcc-3.4/gcc-3.5 support seems pretty much complete now.  There
> >   are enough fixes here to get a reasonably clean build with my .config but a
> >   full kernel build still will need work.
> 
> In my case it is NTFS causing the build failure.
> 
>   CC      fs/ntfs/inode.o
> fs/ntfs/inode.c: In function `ntfs_read_locked_inode':
> fs/ntfs/ntfs.h:186: sorry, unimplemented: inlining failed in call to
> 'ntfs2utc': function body not available

Yes, there are going to be a lot of these.   Lots of code does

foo.h:
	extern inline void foo(void);
foo.c:
	inline void foo(void) 
	{
	}

and latest gcc generates an error in this case (with the options we're
currently using, at least).

The fix is to remove the `inline' from the declaration in foo.h.  It's the
right thing to do anyway, so I'm thinking we should just get in there and
fix them all up.


  reply	other threads:[~2004-01-22 21:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-22  9:35 2.6.2-rc1-mm1 Andrew Morton
2004-01-22 11:03 ` 2.6.2-rc1-mm1 Christoph Hellwig
2004-01-22 15:19   ` 2.6.2-rc1-mm1 viro
2004-01-22 20:31     ` 2.6.2-rc1-mm1 Andrew Morton
2004-01-22 21:30       ` 2.6.2-rc1-mm1 Adrian Bunk
2004-01-22 23:38     ` 2.6.2-rc1-mm1 Greg KH
2004-01-23  0:24       ` 2.6.2-rc1-mm1 viro
2004-01-23  0:41         ` 2.6.2-rc1-mm1 Greg KH
2004-01-22 11:05 ` 2.6.2-rc1-mm1 Christoph Hellwig
2004-01-22 11:07 ` 2.6.2-rc1-mm1 Christoph Hellwig
2004-01-22 11:12   ` 2.6.2-rc1-mm1 Christoph Hellwig
2004-01-22 12:17   ` 2.6.2-rc1-mm1 Jeff Dike
2004-01-22 12:00     ` 2.6.2-rc1-mm1 Christoph Hellwig
2004-01-22 13:28       ` 2.6.2-rc1-mm1 Jeff Dike
2004-01-22 13:20 ` 2.6.2-rc1-mm1 Axel Siebenwirth
2004-01-22 21:34   ` Andrew Morton [this message]
2004-01-22 16:26 ` 2.6.2-rc1-mm1 (compile stats) John Cherry
2004-01-22 21:12 ` 2.6.2-rc1-mm1 Tom Rini

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=20040122133453.1932eae0.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=aia21@cantab.net \
    --cc=axel@pearbough.net \
    --cc=linux-kernel@vger.kernel.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