Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@arm.com>
To: gdb@sources.redhat.com
Cc: Richard.Earnshaw@arm.com
Subject: Re: Results of a multi-build (not good)
Date: Tue, 12 Mar 2002 03:14:00 -0000	[thread overview]
Message-ID: <200203121113.LAA09004@cam-mail2.cambridge.arm.com> (raw)
In-Reply-To: Your message of "Mon, 11 Mar 2002 18:52:05 GMT." <200203111852.SAA25970@cam-mail2.cambridge.arm.com>

[-- Attachment #1: Type: text/plain, Size: 496 bytes --]

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.

R.



[-- Attachment #2: build_gdb_all --]
[-- Type: text/x-script , Size: 2994 bytes --]

#! /bin/sh

# Copyright (C) 2002 Free Software Foundation.
#
# This file is part of GDB.
#
# GDB is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2, or (at your option)
# any later version.
#
# GDB is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with GDB; see the file COPYING.  If not, write to
# the Free Software Foundation, 59 Temple Place - Suite 330,
# Boston, MA 02111-1307, USA.
#
########################################################################
#
# VARIOUS OPTIONS YOU WILL NEED TO CONFIGURE FOR LOCAL USE

# Where builds will live
builddir=/home/rearnsha/gnu/gdb-allcross

# Where the sources live
srcdir=/home/rearnsha/gnusrc/utils/src

# Where logs will go.  NB. Must not be a sub-dir of builddir or you 
# will loose them.
logdir=/home/rearnsha/gnu/gdb-logdir

# Must be GNU awk
awk=awk

# Where to look for the list of targets to test
maintainers=${srcdir}/gdb/MAINTAINERS

# Version of make to use; must be GNU make for parallel makes
make=gnumake

# Number of parallel make jobs
par="10"

# END OF CONFIGURATION OPTIONS
#
########################################################################


# Get the list of targets and the build options
alltarg=`${awk} < "${maintainers}" '
  $2 ~ /--target=.*/ {
    targets = gensub (/^.*--target=/, "", 1, $2)
    warnings = gensub (/[)]*$/, "", 1, $3)
    split (targets, targ, /,/)
    for (i in targ) {
        print targ[i], warnings
    }
  }'`

# Back up the log files
cd ${logdir}

if [ -f build.out ]
then
	mv build.out build.old
fi
if [ -f config.out ]
then
	mv config.out config.old
fi
if [ -f fail.sum ]
then
	mv fail.sum fail.old
fi

if [ ! -d ${builddir} ]
then
	echo ${builddir} does not exist
	exit 1
fi

cd ${builddir}

MAKE=${make}
export MAKE

jobs=1
# For each target, configure and build it.
while read targ opts
do
	if [ ${opts} != "broken" ]
	then
		trap 'echo cleaning up ...; rm -rf ${builddir}/*; exit 1' 1 2 15
		echo ${targ}
		mkdir ${targ}
		cd ${targ}
		${srcdir}/configure --target=$targ \
		  --enable-gdb-build-warnings=$opts \
		  >> ${logdir}/config.tout.$targ 2>&1 &
		cd ..
		jobs=`expr ${jobs} + 1`
		if [ ${jobs} -gt ${par} ]
		then
			wait
			jobs=1
		fi
	fi
done << EOF
$alltarg
EOF

wait

cat ${logdir}/config.tout.* > ${logdir}/config.out
rm -f ${logdir}/config.tout.*

for targ in *
do
	cd $targ
	if  ${make} -j ${par} all-gdb >> ${logdir}/build.out 2>&1
	then
		true
	else
		echo ">>>>>>>>>>>>>" >> ${logdir}/fail.sum
		echo "$targ (${opts})" >> ${logdir}/fail.sum 
		tail -20 ${logdir}/build.out >> ${logdir}/fail.sum
		echo >> ${logdir}/fail.sum
		echo $targ build failed
	fi
	rm -rf *
	cd ..
done

  parent reply	other threads:[~2002-03-12 11:14 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 [this message]
2002-03-12  9:35   ` Andrew Cagney
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=200203121113.LAA09004@cam-mail2.cambridge.arm.com \
    --to=rearnsha@arm.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