From: Hans-Peter Nilsson <hp@bitrange.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [commit] note non-building architectures
Date: Thu, 19 May 2005 19:31:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.58.0505191350500.44062@dair.pair.com> (raw)
In-Reply-To: <428CBDD9.1060707@gnu.org>
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
prev parent reply other threads:[~2005-05-19 18:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-01 23:14 Andrew Cagney
2005-05-01 23:32 ` Mark Kettenis
2005-05-01 23:54 ` Andreas Schwab
2005-05-02 15:58 ` Andrew Cagney
2005-05-02 16:35 ` Mark Kettenis
2005-05-02 16:50 ` Stan Shebs
2005-05-10 3:47 ` Hans-Peter Nilsson
2005-05-19 16:53 ` Andrew Cagney
2005-05-19 19:31 ` Hans-Peter Nilsson [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=Pine.BSF.4.58.0505191350500.44062@dair.pair.com \
--to=hp@bitrange.com \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
/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