From: Iain Sandoe <idsandoe@googlemail.com>
To: Tom de Vries <tdevries@suse.de>
Cc: Gerald Pfeifer <gerald@pfeifer.com>,
Ian Lance Taylor <ian@airs.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Subject: Re: [PATCH 4/4][libbacktrace] Add tests for unused formats
Date: Thu, 03 Jan 2019 11:49:00 -0000 [thread overview]
Message-ID: <4CFB7022-8306-429F-BFAC-17AEC3B84F1D@googlemail.com> (raw)
In-Reply-To: <FAF1C151-F2E7-4E77-A59B-E68780C9CE7C@googlemail.com>
> On 2 Jan 2019, at 13:26, Iain Sandoe <idsandoe@googlemail.com> wrote:
>
>
>> On 2 Jan 2019, at 13:20, Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE> wrote:
>>
>> Gerald Pfeifer <gerald@pfeifer.com> writes:
>>
>>>
<snip>
>>>
>>> I believe that in addition to FreeBSD this probably also fails on
>>> Solaris and Darwin.
>>
>> I cannot test Darwin right now,
>
> I have builds running on a number of versions, will take a look
> - is it missing a “macho_xx.c” implementation, anyway ?
(on darwin17 / macOS 10.13)
make check-target-libbacktrace
fails for me at trunk r267505 with:
/src-local/gcc-trunk/libbacktrace/elf.c:144:2: error: #error "Unknown BACKTRACE_ELF_SIZE"
144 | #error "Unknown BACKTRACE_ELF_SIZE"
| ^~~~~
So, it looks like there’s some configury-fixing/implementation work needed for Darwin.
Iain
next prev parent reply other threads:[~2019-01-03 11:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-23 20:56 Tom de Vries
2018-11-28 12:33 ` Tom de Vries
2018-11-29 18:28 ` Ian Lance Taylor via gcc-patches
2018-11-30 9:06 ` Tom de Vries
2018-11-30 14:46 ` Ian Lance Taylor via gcc-patches
2018-12-29 13:13 ` Gerald Pfeifer
2018-12-29 20:44 ` Gerald Pfeifer
2018-12-30 9:06 ` Tom de Vries
2018-12-30 16:07 ` Gerald Pfeifer
2019-01-02 13:20 ` Rainer Orth
2019-01-02 13:26 ` Iain Sandoe
2019-01-03 11:49 ` Iain Sandoe [this message]
2019-01-03 23:10 ` Ian Lance Taylor via gcc-patches
2019-01-07 19:30 ` Iain Sandoe
2019-01-03 12:49 ` Tom de Vries
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=4CFB7022-8306-429F-BFAC-17AEC3B84F1D@googlemail.com \
--to=idsandoe@googlemail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=ian@airs.com \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
--cc=tdevries@suse.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).