From: <Jan.Sommer@dlr.de>
To: <ebotcazou@adacore.com>, <soja-lists@aries.uberspace.de>
Cc: <gcc@gcc.gnu.org>
Subject: RE: __sync_-builtins cause undefined references on some sparc targets
Date: Fri, 03 Mar 2017 12:07:00 -0000 [thread overview]
Message-ID: <DE6CFD2ED4BCD440A2DE18E253A8FDF45A3FFC@DLREXMBX01.intra.dlr.de> (raw)
In-Reply-To: <1808636.TyOe3qnzdO@polaris>
> -----Original Message-----
> From: gcc-owner@gcc.gnu.org [mailto:gcc-owner@gcc.gnu.org] On Behalf Of
> Eric Botcazou
> Sent: Monday, February 27, 2017 10:30 PM
> To: Jan Sommer
> Cc: gcc@gcc.gnu.org; devel@rtems.org
> Subject: Re: __sync_-builtins cause undefined references on some sparc targets
>
> > Is there an easy way to remove the libbacktrace dependency?
> > Might something like that work?:
> > https://patchwork.ozlabs.org/patch/553017/
>
> Yes, even better, simply arrange for the __sync and __atomic support tests of
> libbacktrace to fail on your target, possibly by using the same trick as HPUX.
Ok. I set libbacktrace_cv_sys_sync=no for my target and the undefined referenced disappeared.
However I am not sure I understand what that means now.
Is libbacktrace excluded from the build, or is it build but broken?
Cheers,
Jan
>
> --
> Eric Botcazou
next prev parent reply other threads:[~2017-03-03 12:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 15:55 Jan.Sommer
2017-02-27 21:08 ` Eric Botcazou
2017-02-27 21:14 ` Jan Sommer
2017-02-27 21:29 ` Eric Botcazou
2017-03-03 12:07 ` Jan.Sommer [this message]
2017-03-03 12:23 ` Eric Botcazou
2017-03-03 12:35 ` Sebastian Huber
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=DE6CFD2ED4BCD440A2DE18E253A8FDF45A3FFC@DLREXMBX01.intra.dlr.de \
--to=jan.sommer@dlr.de \
--cc=ebotcazou@adacore.com \
--cc=gcc@gcc.gnu.org \
--cc=soja-lists@aries.uberspace.de \
/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).