From: Andrew Cagney <ac131313@cygnus.com>
To: Richard.Earnshaw@arm.com
Cc: gdb@sources.redhat.com
Subject: Re: Results of a multi-build (not good)
Date: Tue, 12 Mar 2002 09:35:00 -0000 [thread overview]
Message-ID: <3C8E3C6F.9040706@cygnus.com> (raw)
In-Reply-To: <200203121113.LAA09004@cam-mail2.cambridge.arm.com>
> I've been asked if I could release the multi-build script. It's attached
> below.
>
> Note that it only builds the debuggers, it doesn't run any tests on them.
> To do that I would need to build and install about 36 sets of complete
> tool chains, which I just don't have space for. Further, most of them
> wouldn't be much use without either a simulator or a real piece of
> hardware to test them on.
>
> You will need to tweak the variables at the top of the script to your
> local configuration.
Nice. Having a script to run is going to be easier than pointing at
that awk.
One tweak is to try starting each GDB after it is built - this catches
many multi-arch problems. Having the script restartable (and leave
around broken builds) can also be useful.
Andrew
next prev parent reply other threads:[~2002-03-12 17:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-11 10:52 Richard Earnshaw
2002-03-11 11:08 ` Andrew Cagney
2002-03-12 2:12 ` Richard Earnshaw
2002-03-11 12:02 ` Andrew Cagney
2002-03-12 2:14 ` Richard Earnshaw
2002-03-12 9:27 ` Andrew Cagney
2002-03-11 22:13 ` Eli Zaretskii
2002-03-12 9:11 ` Andrew Cagney
2002-03-12 11:24 ` Eli Zaretskii
2002-03-13 2:00 ` Richard Earnshaw
2002-03-12 3:14 ` Richard Earnshaw
2002-03-12 9:35 ` Andrew Cagney [this message]
2002-03-12 9:45 ` Richard Earnshaw
2002-03-14 6:06 ` Richard Earnshaw
2002-03-23 10:45 ` Andrew Cagney
2002-03-23 10:52 ` Richard Earnshaw
2002-03-23 11:33 ` Andrew Cagney
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=3C8E3C6F.9040706@cygnus.com \
--to=ac131313@cygnus.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gdb@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