From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1221 invoked by alias); 19 May 2005 18:56:37 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 25405 invoked from network); 19 May 2005 18:07:52 -0000 Received: from unknown (HELO dair.pair.com) (209.68.1.49) by sourceware.org with SMTP; 19 May 2005 18:07:52 -0000 Received: (qmail 67201 invoked by uid 20157); 19 May 2005 18:07:52 -0000 Date: Thu, 19 May 2005 19:31:00 -0000 From: Hans-Peter Nilsson X-X-Sender: hp@dair.pair.com To: Andrew Cagney cc: gdb-patches@sources.redhat.com Subject: Re: [commit] note non-building architectures In-Reply-To: <428CBDD9.1060707@gnu.org> Message-ID: References: <42756233.5080809@gnu.org> <428CBDD9.1060707@gnu.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2005-05/txt/msg00478.txt.bz2 On Thu, 19 May 2005, Andrew Cagney wrote: > /bin/sh /home/cagney/PENDING/Werror/src/sim/cris/../common/genmloop.sh \ > -mono -no-fast -pbb -switch semcrisv10f-switch.c \ > -cpu crisv10f -infile > /home/cagney/PENDING/Werror/src/sim/cris/mloop.in > /bin/sh /home/cagney/PENDING/Werror/src/sim/cris/../common/genmloop.sh \ > -mono -no-fast -pbb -switch semcrisv32f-switch.c \ > -cpu crisv32f -infile > /home/cagney/PENDING/Werror/src/sim/cris/mloop.in > /bin/sh /home/cagney/PENDING/Werror/src/sim/cris/../../move-if-change > eng.hin engv10.h > /bin/sh /home/cagney/PENDING/Werror/src/sim/cris/../../move-if-change > mloop.cin mloopv10f.c > mv: cannot stat `mloop.cin': No such file or directory > gmake[2]: *** [stamp-v10fmloop] Error 1 Hmm, this seems like a parallel make breaking on a rule not handling building in parallel. Oops. It would *really* have helped to know that before, as simple as mentioning how you invoked gdb_mbuild.sh. Bug-report details, you know... It also disagrees a bit with the breakage note you put in MAINTAINERS: "(sim/cris/modelv10.c:4181 crisv10f_engine_run_full?)" which tricked me into thinking you were seeing the previous problem still. I'll see to fixing that, and then revert the "breakage" note for the CRIS port in MAINTAINERS. brgds, H-P