Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Karsten Merker <karsten@excalibur.cologne.de>
Cc: linux-mips@linux-mips.org
Subject: Re: Die ll/sc-Emulation ist immer noch kaputt...
Date: Mon, 28 Apr 2003 01:34:51 +0200	[thread overview]
Message-ID: <20030428013451.A13685@linux-mips.org> (raw)
In-Reply-To: <20030425180419.GB6120@excalibur.cologne.de>; from karsten@excalibur.cologne.de on Fri, Apr 25, 2003 at 08:04:19PM +0200

On Fri, Apr 25, 2003 at 08:04:19PM +0200, Karsten Merker wrote:

> mipsel-linux-gcc -D__KERNEL__ -I/tmp/linux-2.4/linux/include -Wall
> -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
> -fomit-frame-pointer
> -I /tmp/linux-2.4/linux/include/asm/gcc -G 0 -mno-abicalls -fno-pic -pipe
> -mcpu=r3000 -mips1   -nostdinc -iwithprefix include -DKBUILD_BASENAME=proc
> -c -o proc.o proc.c
> proc.c: In function \x13how_cpuinfo':
> proc.c:118: \fl_ops' undeclared (first use in this function)
> proc.c:118: (Each undeclared identifier is reported only once
> proc.c:118: for each function it appears in.)
> proc.c:119: \x13c_ops' undeclared (first use in this function)
> make[1]: *** [proc.o] Fehler 1
> make[1]: Leaving directory /tmp/linux-2.4/linux/arch/mips/kernel'
> 
> Bau Deine Kernels bitte mal mit defconfig-decstation, bevor Du sie
> eincheckst }:->

You got odd control characters in your mail ...

Somhow those ll/sc counters in their current form are rather useless as
they're only per system, not per thread so for now I'm removing them.
Yell if somebody minds - I just don't think they're really useful in
their current form ...

  Ralf

           reply	other threads:[~2003-04-27 23:34 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20030425180419.GB6120@excalibur.cologne.de>]

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=20030428013451.A13685@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=karsten@excalibur.cologne.de \
    --cc=linux-mips@linux-mips.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