public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "chrisj at rtems dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug sim/16827] New: Duplication symbol _sim_addr_range_hit_p in sim common on Mavrick
Date: Thu, 10 Apr 2014 05:12:00 -0000 [thread overview]
Message-ID: <bug-16827-4717@http.sourceware.org/bugzilla/> (raw)
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.
next reply other threads:[~2014-04-10 5:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 5:12 chrisj at rtems dot org [this message]
2015-03-29 21:54 ` [Bug sim/16827] " vapier at gentoo dot org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-16827-4717@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).