From: Steven Rostedt <rostedt@goodmis.org>
To: Jonathan Andrews <jon@jonshouse.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.38 Cant compile
Date: Fri, 18 Mar 2011 18:39:25 -0400 [thread overview]
Message-ID: <20110318223925.GK14675@home.goodmis.org> (raw)
In-Reply-To: <1300479562.18471.7.camel@jonspc>
On Fri, Mar 18, 2011 at 08:19:22PM +0000, Jonathan Andrews wrote:
> I didn't get very far...
>
> Sorry for posting here but google shed no light on this
>
> Any constructive comments welcome.
>
> Cheers,
> Jon
>
> # make
> CHK include/linux/version.h
> CHK include/generated/utsrelease.h
> CC arch/x86/kernel/asm-offsets.s
> In file included from /usr/src/linux-2.6.38/arch/x86/include/asm/bitops.h:449,
> from include/linux/bitops.h:22,
> from include/linux/kernel.h:17,
> from /usr/src/linux-2.6.38/arch/x86/include/asm/percpu.h:44,
> from /usr/src/linux-2.6.38/arch/x86/include/asm/current.h:5,
> from /usr/src/linux-2.6.38/arch/x86/include/asm/processor.h:15,
> from /usr/src/linux-2.6.38/arch/x86/include/asm/atomic.h:6,
> from include/linux/crypto.h:20,
> from arch/x86/kernel/asm-offsets_32.c:7,
> from arch/x86/kernel/asm-offsets.c:2:
> /usr/src/linux-2.6.38/arch/x86/include/asm/arch_hweight.h: In function `__arch_hweight32':
> /usr/src/linux-2.6.38/arch/x86/include/asm/arch_hweight.h:29: parse error before string constant
> make[1]: *** [arch/x86/kernel/asm-offsets.s] Error 1
> make: *** [prepare0] Error 2
Hmm, that happened in the ALTERNATIVE() macro. Could be a config
problem. Could you send me you .config you used.
>
> # gcc --version
> gcc (GCC) 3.2.2
This is also a pretty old gcc. Pretty much all distros are on 4.*
-- Steve
prev parent reply other threads:[~2011-03-18 22:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-18 20:19 Jonathan Andrews
2011-03-18 22:39 ` Steven Rostedt [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=20110318223925.GK14675@home.goodmis.org \
--to=rostedt@goodmis.org \
--cc=jon@jonshouse.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®