| To: | Philippe De Swert <philippedeswert@scarlet.be> |
|---|---|
| Subject: | Re: [Fwd: kernel compilation fails] |
| From: | Ralf Baechle <ralf@linux-mips.org> |
| Date: | Thu, 16 Jun 2005 11:20:55 +0100 |
| Cc: | tom <tom@voda.cz>, linux-mips <linux-mips@linux-mips.org> |
| In-reply-to: | <II68V7$710BD802DB90EFADDBE27A92E7C5B2C2@scarlet.be> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <II68V7$710BD802DB90EFADDBE27A92E7C5B2C2@scarlet.be> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mutt/1.4.1i |
On Thu, Jun 16, 2005 at 10:54:43AM +0100, Philippe De Swert wrote:
> Basically 2.4.18 code is too old to compile as is with gcc 3.3.4. The
> assembler code needs to be inlined with a different syntax. Just look at
> similar files to see how it is done.
Not true. Gcc 3.3 is probably even is the most commonly used compiler
with 2.4-based systems. Builds with gcc 3.4 will fail for some 2.4
kernel configurations but at the very least throw loads of warnings.
> As a quick hint here is some code to show how it should look like.
>
>
> __asm__(".set\tmips3\n\t"
> "wait\n\t"
> ".set\tmips0");
>
> Notice the \n and \t parts. You are probabely missing those.
Actually more and more code it being formatted using tabs instead of the
\t escape sequence for readability.
Ralf
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: kernel compilation fails, Ralf Baechle |
|---|---|
| Next by Date: | Updated Indigo2 IP28 patches., peter fuerst |
| Previous by Thread: | Re:[Fwd: kernel compilation fails], Philippe De Swert |
| Next by Thread: | Updated Indigo2 IP28 patches., peter fuerst |
| Indexes: | [Date] [Thread] [Top] [All Lists] |