forked from Imagelibrary/binutils-gdb
39dea61079
This patch changes the GDB build system in order to use libtool to
link the several built executables. This makes it possible to refer
to libtool libraries (.la files) in CLIBS.
As an application of the above,
BFD now refers to ../libbfd/libbfd.la
OPCODES now refers to ../opcodes/libopcodes.la
LIBBACKTRACE_LIB now refers to ../libbacktrace/libbacktrace.la
LIBCTF now refers to ../libctf/libctf.la
NOTE1: The addition of libtool adds a few new configure-time options
to GDB. Among these, --enable-shared and --disable-shared, which were
previously ignored. Now GDB shall honor these options when linking,
picking up the right version of the referred libtool libraries
automagically.
NOTE2: I have not tested the insight build.
NOTE3: For regenerating configure I used an environment with Autoconf
2.69 and Automake 1.15.1. This should match the previously
used version as announced in the configure script.
NOTE4: Now the installed shared object libbfd.so is used by gdb
if binutils is installed with --enable-shared.
Testing performed:
- --enable-shared and --disable-shared (the default in binutils) work
as expected: the linked executables link with the archive or shared
libraries transparently.
- Makefile.in modified for EXEEXT = .exe. It installs the binaries
just fine. The installed gdb.exe runs fine.
- Native build regtested in x86_64. The installed gdb runs fine.
In the regression testing I'm observing that the following tests
doesn't seem to be deterministic:
gdb.base/step-over-syscall.exp
gdb.threads/process-dies-while-detaching.exp
gdb.threads/process-dies-while-handling-bp.exp
Sometimes some of the the tests in these files unexpectedly fail,
like in:
-PASS: gdb.threads/process-dies-while-detaching.exp: single-process: \
continue: detach: continue
+FAIL: gdb.threads/process-dies-while-detaching.exp: single-process: \
continue: detach: continue
Sometimes they unexpectedly pass:
-KFAIL: gdb.base/step-over-syscall.exp: clone: displaced=on: \
check_pc_after_cross_syscall: single step over clone \
final pc (PRMS: gdb/19675)
+PASS: gdb.base/step-over-syscall.exp: clone: displaced=on: \
check_pc_after_cross_syscall: single step over clone final pc
-KFAIL: gdb.threads/process-dies-while-handling-bp.exp: \
non_stop=on: cond_bp_target=0: inferior 1 exited \
(prompt) (PRMS: gdb/18749)
+PASS: gdb.threads/process-dies-while-handling-bp.exp: \
non_stop=on: cond_bp_target=0: inferior 1 exited
- Cross build for aarch64-linux-gnu built to exercise
program_transform_name and friends. The installed
aarch64-linux-gnu-gdb runs fine.
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=29372
README for GNU development tools This directory contains various GNU compilers, assemblers, linkers, debuggers, etc., plus their support routines, definitions, and documentation. If you are receiving this as part of a GDB release, see the file gdb/README. If with a binutils release, see binutils/README; if with a libg++ release, see libg++/README, etc. That'll give you info about this package -- supported targets, how to use it, how to report bugs, etc. It is now possible to automatically configure and build a variety of tools with one command. To build all of the tools contained herein, run the ``configure'' script here, e.g.: ./configure make To install them (by default in /usr/local/bin, /usr/local/lib, etc), then do: make install (If the configure script can't determine your type of computer, give it the name as an argument, for instance ``./configure sun4''. You can use the script ``config.sub'' to test whether a name is recognized; if it is, config.sub translates it to a triplet specifying CPU, vendor, and OS.) If you have more than one compiler on your system, it is often best to explicitly set CC in the environment before running configure, and to also set CC when running make. For example (assuming sh/bash/ksh): CC=gcc ./configure make A similar example using csh: setenv CC gcc ./configure make Much of the code and documentation enclosed is copyright by the Free Software Foundation, Inc. See the file COPYING or COPYING.LIB in the various directories, for a description of the GNU General Public License terms under which you can copy the files. REPORTING BUGS: Again, see gdb/README, binutils/README, etc., for info on where and how to report problems.