This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug build/15916] New: gdb assumes lib(bfd,opcodes) are static
- From: "dilyan.palauzov at aegee dot org" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Sat, 31 Aug 2013 12:26:39 +0000
- Subject: [Bug build/15916] New: gdb assumes lib(bfd,opcodes) are static
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=15916
Bug ID: 15916
Summary: gdb assumes lib(bfd,opcodes) are static
Product: gdb
Version: 7.6
Status: NEW
Severity: normal
Priority: P2
Component: build
Assignee: unassigned at sourceware dot org
Reporter: dilyan.palauzov at aegee dot org
In my /usr/local/etc/config.site I have
export enable_static=no
export enable_shared=yes
which means that a "./configure" always generates only shared and no static
libraries. For this reason, when I compile gdb, only shared libbfd is created.
However gdb/Makefile.in on line 134
# Where is the BFD library? Typically in ../bfd.
BFD_DIR = ../bfd
BFD = $(BFD_DIR)/libbfd.a <===== here
BFD_SRC = $(srcdir)/$(BFD_DIR)
BFD_CFLAGS = -I$(BFD_DIR) -I$(BFD_SRC)
assumes, that a static libbfd.a is going to be created, which is not the case.
Proposal:
replace BFD with -lbfd and add in CLIBS (gbd/Makefile.in, line 476)
-L$(BFD_DIR) before $(BFD)
Second proposal:
move libbfd to a separate package, on which binutils and gdb depend, no
matter if libbfd is static or shared.
Exactly the same observations apply for libopcodes.
--
You are receiving this mail because:
You are on the CC list for the bug.