This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug sim/16827] New: Duplication symbol _sim_addr_range_hit_p in sim common on Mavrick
- From: "chrisj at rtems dot org" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Thu, 10 Apr 2014 05:12:20 +0000
- Subject: [Bug sim/16827] New: Duplication symbol _sim_addr_range_hit_p in sim common on Mavrick
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=16827
Bug ID: 16827
Summary: Duplication symbol _sim_addr_range_hit_p in sim common
on Mavrick
Product: gdb
Version: 7.7
Status: NEW
Severity: normal
Priority: P2
Component: sim
Assignee: unassigned at sourceware dot org
Reporter: chrisj at rtems dot org
CC: vapier at gentoo dot org
Created attachment 7544
--> https://sourceware.org/bugzilla/attachment.cgi?id=7544&action=edit
Clean up and fix the inline of the sim-arange code.
Building RTEMS targets with a simulator fail on Mavrick using cc etc with:
duplicate symbol _sim_addr_range_hit_p in:
nrun.o
libsim.a(sim-cpu.o)
printed once for each object file libsim.a. The failure happens with the bfin
and h8300 targets and I suspect all will fail. The same targets build on
FreeBSD 10.
The configure command line is:
../gdb-7.7/configure --build=x86_64-apple-darwin13.1.0
--host=x86_64-apple-darwin13.1.0 --target=h8300-rtems4.11 --verbose
--disable-nls --without-included-gettext --disable-win32-registry
--disable-werror --enable-sim --without-zlib --with-expat --with-python
--prefix=/Users/chris/development/rtems/4.11
--bindir=/Users/chris/development/rtems/4.11/bin
--exec-prefix=/Users/chris/development/rtems/4.11
--includedir=/Users/chris/development/rtems/4.11/include
--libdir=/Users/chris/development/rtems/4.11/lib
--mandir=/Users/chris/development/rtems/4.11/share/man
--infodir=/Users/chris/development/rtems/4.11/share/info
I attach a patch which works on Mavrick and FreeBSD. I am not sure it is 100%
as some of the logic used in the way the inline, extern and extern inline are
handled left me confused so I just cleaned up the code.
--
You are receiving this mail because:
You are on the CC list for the bug.