This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: breakage with "switch to gdb version script"


> From: Mike Frysinger <vapier@gentoo.org>
> Date: Tue, 14 Apr 2015 23:18:04 +0200

> On 14 Apr 2015 22:43, Hans-Peter Nilsson wrote:
> > From: Mike Frysinger <vapier@gentoo.org>
> > > On 13 Apr 2015 16:35, Hans-Peter Nilsson wrote:
> > > > While that seems pretty trivial, you also need to adjust
> > > > src-release.sh to make sure "./src-release.sh -b sim" works,
> > > > in which a tool-specific create-version.sh is searched.
> > > 
> > > this probably does it, but i've never used src-release before ...
> > 
> > You use it to create a release-like tarball (example
> > command-line above), check that you can build and install $tool
> > (in this case sim) for any target from it; presto, testing
> > complete.
> 
> i tried that but it failed with weird gdb info error messags (which looked 
> unrelated to match patch) so i gave up

I saw no such problem at 69cb14a0d7, neither for sim nor gdb,
using an x86_64 Debian 7.1.  Info-files *are* being generated
with src-release.sh, as for a release, so your development tools
have to be complete.  You probably expected this kind of
reponse, but still: unless it was a temporary bug fixed between
your test and the commit above, I'd guess your makeinfo tools
are out of date or something similar, which would not be
something you can allow yourself to "give up" on, and just skip
testing.  Pretty please investigate.

Regarding using the gdb create-version.sh for sim, I'd rather we
increase separation between sim and gdb sources than making them
more intertwined like that.

Anyway, I committed the following after testing, building sim
and gdb ("make all"), for each untarring the created tarballs
and respectively building a native gdb and a bfin-elf sim.  The
need for gdb/common/create-version.sh should be obvious, but
JFTR, you'll otherwise get:
/bin/bash /tmp/fix/s/s2/sim-7.9.50.20150415/sim/bfin/../../move-if-change tmp-tmap.c targ-map.c
touch stamp-tvals
make[3]: *** No rule to make target `/tmp/fix/s/s2/sim-7.9.50.20150415/sim/bfin/../../gdb/common/create-version.sh', needed by `version.c'.  Stop.
make[3]: Leaving directory `/tmp/fix/s/s2/o/sim/bfin'

toplevel:
	Adjust src-release.sh for sim using the gdb create-version.sh.
	* src-release.sh (tar_compress): If there's a fifth parameter,
	use that in the getver call instead of $tool.
	(sim_release): Pass gdb as fifth parameter to tar_compress.
	(SIM_SUPPORT_DIRS): Add gdb/common/create-version.sh.

diff --git a/src-release.sh b/src-release.sh
index 9b985f0..40d0126 100755
--- a/src-release.sh
+++ b/src-release.sh
@@ -244,7 +244,8 @@ tar_compress()
     tool=$2
     support_files=$3
     compressors=$4
-    ver=$(getver $tool)
+    verdir=${5:-$tool}
+    ver=$(getver $verdir)
     do_proto_toplev $package $ver $tool "$support_files"
     do_md5sum
     do_tar $package $ver
@@ -295,13 +296,13 @@ gdb_release()
 }
 
 # Corresponding to the CVS "sim" module.
-SIM_SUPPORT_DIRS="bfd opcodes libiberty include intl gdb/version.in makefile.vms zlib"
+SIM_SUPPORT_DIRS="bfd opcodes libiberty include intl gdb/version.in gdb/common/create-version.sh makefile.vms zlib"
 sim_release()
 {
     compressors=$1
     package=sim
     tool=sim
-    tar_compress $package $tool "$SIM_SUPPORT_DIRS" "$compressors"
+    tar_compress $package $tool "$SIM_SUPPORT_DIRS" "$compressors" gdb
 }
 
 usage()

brgds, H-P


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]