This is the mail archive of the gdb-cvs@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]

src/gdb ChangeLog Makefile.in acinclude.m4 con ...


CVSROOT:	/cvs/src
Module name:	src
Changes by:	palves@sourceware.org	2013-07-03 13:25:46

Modified files:
	gdb            : ChangeLog Makefile.in acinclude.m4 configure 
	                 configure.ac 
	gdb/gdbserver  : ChangeLog Makefile.in acinclude.m4 configure 
	                 configure.ac 
Added files:
	gdb            : development.sh libmcheck.m4 

Log message:
	On mainline/development, also link GDBserver with -lmcheck.
	
	This factors --enable-libmcheck related bits from GDB's configure.ac
	and makes GDBserver use them too.  Specifically, the 'development'
	global is moved to a separate script to it can be sourced by both GDB
	and GDBserver, and the --enable-libmcheck/--disable-libmcheck bits
	proper are moved to a new m4 file.
	
	I started out by defining 'development' in the m4 file, but in the end
	decided against it, as a separate script has the advantage that
	changing it in release branches does not require regenerating
	configure, unlike today.
	
	I had also started out by making the new GDB_AC_LIBMCHECK itself
	handle the yes/no default fallback depending on release/developement,
	but since I had split out 'development' to a separate script, and, GDB
	needs the python checks anyway (hence we'd need to do the python
	checks in gdb's configure.ac, and pass in a 'default lmcheck yes/no'
	parameter to GDB_AC_LIBMCHECK anyway), I ended up keeping
	GDB_AC_LIBMCHECK isolated from the 'development' global.  IOW, it's
	the caller's business to handle it.
	
	Tested on x86_64 Fedora 17.  Built GDB and GDBserver with and without
	--enable-libmcheck, and observed --enable-libmcheck overrides the
	disablement of -lmcheck caused by python supporting threads, and that
	GDBserver links with -lmcheck when expected.  Also observed that
	changing the 'development' global, and issuing "make" triggers a
	relink, and '-lmcheck' is included or not from the link accordingly.
	
	gdb/
	2013-07-03  Pedro Alves  <palves@redhat.com>
	
	* Makefile.in (config.status): Depend on development.sh.
	(aclocal_m4_deps): Add libmcheck.m4.
	* acinclude.m4: Include libmcheck.m4.
	* configure.ac: Source development.sh instead of setting
	'development' here.  --enable-libmcheck/--disable-libmcheck code
	factored out to GDB_AC_LIBMCHECK.  Run it.
	* development.sh: New file.
	* libmcheck.m4: New file.
	* configure: Regenerate.
	
	gdb/gdbserver/
	2013-07-03  Pedro Alves  <palves@redhat.com>
	
	* Makefile.in (config.status): Depend on development.sh.
	* acinclude.m4: Include libmcheck.m4.
	* configure: Regenerate.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/development.sh.diff?cvsroot=src&r1=NONE&r2=1.1
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/libmcheck.m4.diff?cvsroot=src&r1=NONE&r2=1.1
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/ChangeLog.diff?cvsroot=src&r1=1.15780&r2=1.15781
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/Makefile.in.diff?cvsroot=src&r1=1.1260&r2=1.1261
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/acinclude.m4.diff?cvsroot=src&r1=1.43&r2=1.44
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/configure.diff?cvsroot=src&r1=1.398&r2=1.399
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/configure.ac.diff?cvsroot=src&r1=1.210&r2=1.211
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/gdbserver/ChangeLog.diff?cvsroot=src&r1=1.740&r2=1.741
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/gdbserver/Makefile.in.diff?cvsroot=src&r1=1.156&r2=1.157
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/gdbserver/acinclude.m4.diff?cvsroot=src&r1=1.11&r2=1.12
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/gdbserver/configure.diff?cvsroot=src&r1=1.83&r2=1.84
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/gdbserver/configure.ac.diff?cvsroot=src&r1=1.69&r2=1.70


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