From: Florian Lohoff <flo@rfc822.org>
To: Ian Chilton <ian@ichilton.co.uk>
Cc: linux-mips@oss.sgi.com
Subject: Re: Current Kernel in CVS Broken
Date: Fri, 14 Dec 2001 18:43:04 +0100 [thread overview]
Message-ID: <20011214174304.GA7510@paradigm.rfc822.org> (raw)
In-Reply-To: <20011214172739.A28669@woody.ichilton.co.uk>
[-- Attachment #1: Type: text/plain, Size: 1062 bytes --]
On Fri, Dec 14, 2001 at 05:27:39PM +0000, Ian Chilton wrote:
> 2.4 cvs broken
>
> mips-linux-gcc -I /home/ian/tmp/i2/linux/include/asm/gcc -D__KERNEL__
> -I/home/ian/tmp/i2/linux/include -Wall -Wstrict-prototypes
> -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing
> -fno-common -G 0 -mno-abicalls -fno-pic -mcpu=r4600 -mips2 -Wa,--trap
> -pipe -c -o ip22-setup.o ip22-setup.c
> ip22-setup.c: In function `sgi_request_irq':
> ip22-setup.c:64: `SGI_KEYBD_IRQ' undeclared (first use in this
> function)
> ip22-setup.c:64: (Each undeclared identifier is reported only once
> ip22-setup.c:64: for each function it appears in.)
> make[1]: *** [ip22-setup.o] Error 1
> make[1]: Leaving directory `/home/ian/tmp/i2/linux/arch/mips/sgi-ip22'
> make: *** [_dir_arch/mips/sgi-ip22] Error 2
You already have the fix in your inbox for a couple of hours which is a
one liner.
Flo
--
Florian Lohoff flo@rfc822.org +49-5201-669912
Nine nineth on september the 9th Welcome to the new billenium
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-12-14 18:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-14 17:27 Current Kernel in CVS Broken Ian Chilton
2001-12-14 17:43 ` Florian Lohoff [this message]
2001-12-14 18:08 ` Ian Chilton
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=20011214174304.GA7510@paradigm.rfc822.org \
--to=flo@rfc822.org \
--cc=ian@ichilton.co.uk \
--cc=linux-mips@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