From: Axel Siebenwirth <axel@pearbough.net>
To: linux-kernel@vger.kernel.org
Subject: Re: [2.4-bk] build error in page_alloc.c
Date: Wed, 17 Dec 2003 18:50:37 +0100 [thread overview]
Message-ID: <20031217175037.GB8593@neon> (raw)
In-Reply-To: <20031217174325.GA8593@neon>
Hi linux-kernel!
On Wed, 17 Dec 2003, Axel Siebenwirth wrote:
> Just tried to build 2.4 from current bk.
> config.gz is attached.
>
> gcc -D__KERNEL__ -I/usr/local/src/system/kernel/linus-2.4/include -Wall
> -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
> -pipe -mpreferred-stack-boundary=2 -march=pentium4 -nostdinc -iwithprefix
> include -DKBUILD_BASENAME=page_alloc -DEXPORT_SYMTAB -c page_alloc.c
> page_alloc.c: In function \x1f_alloc_pages':
> page_alloc.c:382: error: parse error before '{' token
> page_alloc.c:339: warning: unused variable \x06reed'
Sorry. Missing closing brace. Didn't check the list before I wrote my
report.
Regards,
Axel
prev parent reply other threads:[~2003-12-17 17:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-17 17:43 [2.4-bk] build error in page_alloc.c Axel Siebenwirth
2003-12-17 17:50 ` Axel Siebenwirth [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=20031217175037.GB8593@neon \
--to=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 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.