From: Tom Rini <trini@kernel.crashing.org>
To: Remco Post <r.post@sara.nl>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux v2.5.33, compile error on powermac
Date: Mon, 2 Sep 2002 12:38:41 -0700 [thread overview]
Message-ID: <20020902193841.GG761@opus.bloom.county> (raw)
In-Reply-To: <B0754740-BE6F-11D6-9030-000393911DE2@sara.nl>
On Mon, Sep 02, 2002 at 02:29:56PM +0200, Remco Post wrote:
> make[2]: Entering directory `/usr/src/linux-2.5.33/fs/reiserfs'
> gcc -Wp,-MD,./.resize.o.d -D__KERNEL__ -I/usr/src/linux-2.5.33/include
> - -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
> - -fno-strict-aliasing -fno-common -I/usr/src/linux-2.5.33/arch/ppc
> - -fsigned-char -msoft-float -pipe -ffixed-r2 -Wno-uninitialized
> - -mmultiple -mstring -nostdinc -iwithprefix include -O1
> - -DKBUILD_BASENAME=resize -c -o resize.o resize.c
> In file included from resize.c:12:
> /usr/src/linux-2.5.33/include/linux/vmalloc.h:26: parse error before
> `pgprot_t'
> /usr/src/linux-2.5.33/include/linux/vmalloc.h:26: warning: function
> declaration isn't a prototype
> /usr/src/linux-2.5.33/include/linux/vmalloc.h:37: parse error before
> `pgprot_t'
> /usr/src/linux-2.5.33/include/linux/vmalloc.h:38: warning: function
> declaration isn't a prototype
> make[2]: *** [resize.o] Error 1
> make[2]: Leaving directory `/usr/src/linux-2.5.33/fs/reiserfs'
> make[1]: *** [reiserfs] Error 2
> make[1]: Leaving directory `/usr/src/linux-2.5.33/fs'
> make: *** [fs] Error 2
fs/reiserfs/resize.c needs to include <linux/mm.h>, iirc. Make a patch
and send it to the trivial patch monkey and/or Linus.
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2002-09-02 19:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-31 22:22 Linux v2.5.33 Linus Torvalds
2002-09-02 12:29 ` Linux v2.5.33, compile error on powermac Remco Post
2002-09-02 19:38 ` Tom Rini [this message]
2002-09-02 20:55 ` [TRIVIAL] reiserfs patch, was " Remco Post
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=20020902193841.GG761@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=r.post@sara.nl \
/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.