All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomas Szepe <szepe@pinerecords.com>
To: Dave Kleikamp <shaggy@austin.ibm.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: JFS compilation fix [was Re: Linux 2.6.7]
Date: Wed, 16 Jun 2004 15:05:23 +0200	[thread overview]
Message-ID: <20040616130523.GE1571@louise.pinerecords.com> (raw)
In-Reply-To: <1087390524.29047.10.camel@shaggy.austin.ibm.com>

On Jun-16 2004, Wed, 07:55 -0500
Dave Kleikamp <shaggy@austin.ibm.com> wrote:

> On Wed, 2004-06-16 at 03:07, Tomas Szepe wrote:
> > Here's a trivial patch to fix JFS compilation in 2.6.7.  The error
> > only happens in specific configs -- one such config can be found here:
> > http://www.pinerecords.com/kala/_nonpub/.config.louise26
> 
> I don't know why gcc-3.2.2 doesn't complain about this one, as I have
> compiled this numerous times.
> 
> Your patch has an unnecessary include of jfs_dtree.h.  jfs_dtree.h is
> included by jfs_inline.h, and is not needed in jfs_dtree.c.

Oh, right.

> > I don't have the time to narrow the problem down to the config
> > entry that gets jfs_dtree.c to include jfs_dtree.h (jfs_dtree.c
> > itself doesn't have any relevat ifdefs).
> 
> My guess is the config entry is CONFIG_JFS_FS. :^)

Well, it just so happens that I have two .config files, both listing
CONFIG_JFS_FS=m, and without the patch, exactly one of them fails
compilation (on the same cluster, distcc gcc 3.4.0).  That is why
I assumed the include was missing -- the moving of the declaration
in my patch was only meant as an extra clean up for bonus points.
;)

-- 
Tomas Szepe <szepe@pinerecords.com>

  parent reply	other threads:[~2004-06-16 13:08 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-16  5:56 Linux 2.6.7 Linus Torvalds
2004-06-16  6:58 ` Kalin KOZHUHAROV
2004-06-16 14:56   ` Jesper Juhl
2004-06-16  7:10 ` Jan De Luyck
2004-06-16  8:07 ` JFS compilation fix [was Re: Linux 2.6.7] Tomas Szepe
2004-06-16 12:55   ` Dave Kleikamp
2004-06-16 12:59     ` Dave Kleikamp
2004-06-16 13:05     ` Tomas Szepe [this message]
2004-06-16  9:58 ` Linux 2.6.7 (stty rows 50 columns 140 reports : No such device or address) Zilvinas Valinskas
2004-06-16 12:55   ` Jeff Garzik
2004-06-16 13:56     ` Benjamin Herrenschmidt
2004-06-16 16:38       ` jsimmons
2004-06-16 16:38         ` jsimmons
2004-06-16 14:17     ` Zilvinas Valinskas
2004-06-16 16:37       ` jsimmons
2004-06-16 16:37         ` jsimmons
2004-06-16 21:17         ` Egmont Koblinger
2004-06-16 21:17           ` Egmont Koblinger
2004-06-16 21:45           ` jsimmons
2004-06-16 21:45             ` jsimmons
2004-06-16 11:13 ` Linux 2.6.7 Tomas Szepe
2004-06-16 12:18   ` viro
2004-06-17  6:56     ` Tomas Szepe
2004-06-16 13:27 ` Linux 2.6.7 - problem with old gcc Eyal Lebedinsky
2004-06-16 16:09 ` Linux 2.6.7 (compile stats) John Cherry
2004-06-16 16:31 ` Linux 2.6.7 Dominik Karall
2004-06-16 18:53   ` Jeff Garzik
2004-06-16 17:42 ` Linux 2.6.7 - ACPI still broken Thomas Zehetbauer
2004-06-17  4:15   ` Kevin P. Fleming
2004-06-17 15:22 ` Linux 2.6.7 Sean Neakums
2004-06-18  4:36   ` Andrew Morton
2004-06-18 16:37 ` 2.6.7 Samba OOPS (in smb_readdir) Brice Goglin
2004-06-18 16:41   ` Brice Goglin
2004-06-18 17:11     ` Zwane Mwaikambo
2004-06-18 19:00       ` Christophe Saout
2004-06-18 19:22         ` Christophe Saout
2004-06-18 19:52           ` Zwane Mwaikambo
2004-06-19 20:35           ` Zwane Mwaikambo
2004-06-19 20:49             ` Zwane Mwaikambo
2004-06-19 20:52               ` Christophe Saout
2004-06-20  0:27               ` Zwane Mwaikambo
2004-06-20  0:28                 ` Christophe Saout
2004-06-20  0:36                   ` Zwane Mwaikambo
2004-06-20  0:40                     ` Christophe Saout

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=20040616130523.GE1571@louise.pinerecords.com \
    --to=szepe@pinerecords.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shaggy@austin.ibm.com \
    --cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.