From: David Miller <davem@davemloft.net>
To: ultralinux@vger.kernel.org
Subject: Re: sparc64 cross-compile errors in 2.6.18-mm3
Date: Wed, 04 Oct 2006 23:47:31 +0000 [thread overview]
Message-ID: <20061004.164731.78709872.davem@davemloft.net> (raw)
In-Reply-To: <20061004234437.GJ665@shell0.pdx.osdl.net>
From: Judith Lebzelter <judith@osdl.org>
Date: Wed, 4 Oct 2006 16:44:37 -0700
> I run cross-compiles on various architectures and the sparc64 which worked
> well for 2.6.18-mm2, has a major error for 2.6.18-mm3 kernel. Almost
> nothing compiles because they all include 'include/linux/compat.h', which
> has this error:
>
> include/linux/compat.h:231: error: parse error before '*' token
> include/linux/compat.h:231: warning: function declaration isn't a prototype
> make[1]: [init/main.o] Error 1 (ignored)
>
> Do I need to change a configuration option or something?
Fixed in Linus's current tree for at least 2 days.
I should remove Jakub, Eddie, and Anton from the MAINTAINERS
entry, they haven't been active in sparc maintainence for
years.
next prev parent reply other threads:[~2006-10-04 23:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-04 23:44 sparc64 cross-compile errors in 2.6.18-mm3 Judith Lebzelter
2006-10-04 23:47 ` David Miller [this message]
2006-10-05 0:12 ` Judith Lebzelter
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=20061004.164731.78709872.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ultralinux@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.