From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Rich Felker <dalias@libc.org>
Cc: musl@lists.openwall.com
Subject: Re: Re: python-libconfig failing to build with musl
Date: Wed, 1 Mar 2017 09:03:10 +0100 [thread overview]
Message-ID: <20170301090310.38bc0b46@free-electrons.com> (raw)
In-Reply-To: <20170301022543.GD1520@brightrain.aerifal.cx>
Hello,
On Tue, 28 Feb 2017 21:25:43 -0500, Rich Felker wrote:
> > It's intentional that FILE is an incomplete type. Do you know what
> > they're trying to do by trying to use it as if it were a complete
> > type? This is a bug that needs a patch, preferably one suitable for
> > upstream.
>
> On further investigation, it looks like there's something weird that
> boost is doing that's causing it to get expanded in a template that
> uses FILE rather than FILE*. Not clear why but this is probably a bug
> in boost. Maybe someone who understands C++ better could advise.
Yeah, I also tried to have a look, but C++ and Boost are too unfamiliar
to me, and I had to give up.
> BTW, any idea what happened to your mail to the list? It seems to have
> gotten lost.
My e-mails for some reason don't make it to the mailing list. I am
registered on the list as I'm receiving all the traffic, and I'm using
the same From: address as the one used for my mailing list
subscription. My previous e-mail to the list (about SSP on x86) also
didn't make it to the list.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-03-01 8:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170228221233.30654a92@free-electrons.com>
2017-02-28 21:49 ` Rich Felker
2017-03-01 2:25 ` Rich Felker
2017-03-01 8:03 ` Thomas Petazzoni [this message]
2017-03-02 14:45 ` Rich Felker
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=20170301090310.38bc0b46@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=dalias@libc.org \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).