Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Greg Weeks <greg.weeks@timesys.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Re: 24K malta
Date: Wed, 10 Aug 2005 11:00:40 -0400	[thread overview]
Message-ID: <42FA1698.2060104@timesys.com> (raw)
In-Reply-To: <20050810144947.GE2840@linux-mips.org>

Ralf Baechle wrote:

>On Wed, Aug 10, 2005 at 10:45:37AM -0400, Greg Weeks wrote:
>
>  
>
>>Current CVS fails to build the malta_defconfig with:
>>
>>
>>scripts/kconfig/mconf arch/mips/Kconfig
>>arch/mips/Kconfig:690: can't open file "arch/mips/tx4938/Kconfig"
>>make[1]: *** [menuconfig] Error 1
>>make: *** [menuconfig] Error 2
>>    
>>
>
>CVS pilot error.  cvs -q update -d -P and don't forget to bitch about it ;)
>
>  
>
Would bitching about it do any good? I expect I'd just get told to stick 
it in my .cvsrc which is what I just did.

Now I get this:

  AS      arch/mips/kernel/r4k_switch.o
  CC      arch/mips/kernel/vpe.o
{standard input}: Assembler messages:
{standard input}:1329: Error: unrecognized opcode `mftc0 $7,$2,4'
{standard input}:1333: Error: unrecognized opcode `mftc0 $6,$2,1'

Greg Weeks

  reply	other threads:[~2005-08-10 14:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-10 13:40 24K malta Greg Weeks
2005-08-10 14:02 ` Ralf Baechle
2005-08-10 14:13   ` Greg Weeks
2005-08-10 14:45     ` Greg Weeks
2005-08-10 14:49       ` Ralf Baechle
2005-08-10 15:00         ` Greg Weeks [this message]
2005-08-10 15:09           ` Ralf Baechle
2005-08-10 15:14             ` Greg Weeks
2005-08-10 15:15               ` Ralf Baechle
2005-08-10 19:14           ` Ralf Baechle
2005-08-10 15:02         ` Thiemo Seufer
2005-08-24 12:25   ` Greg Weeks
2005-08-24 13:35     ` Ralf Baechle
2005-08-10 18:00 ` Greg Weeks
2005-08-10 18:00   ` Greg Weeks

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=42FA1698.2060104@timesys.com \
    --to=greg.weeks@timesys.com \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@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