From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Subject: Re: Re: python-libconfig failing to build with musl
Date: Tue, 28 Feb 2017 21:25:43 -0500 [thread overview]
Message-ID: <20170301022543.GD1520@brightrain.aerifal.cx> (raw)
In-Reply-To: <20170228214931.GC1520@brightrain.aerifal.cx>
On Tue, Feb 28, 2017 at 04:49:31PM -0500, Rich Felker wrote:
> On Tue, Feb 28, 2017 at 10:12:33PM +0100, Thomas Petazzoni wrote:
> > Hello,
> >
> > The python-libconfig doesn't build with the musl C library, with some
> > very weird error coming all the way from Boost Python:
> >
> > error: invalid use of incomplete type 'struct _IO_FILE'
> >
> > See:
> >
> > http://autobuild.buildroot.net/results/f0f/f0f6cdc8c38c024772615d5e677b0f4ad63ef7ec/build-end.log
> >
> > for the complete build log of python-libconfig.
> >
> > If you want a way to easily reproduce, let me know, I can provide the
> > 4/5 commands that can allow you to reproduce it with Buildroot.
>
> 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.
BTW, any idea what happened to your mail to the list? It seems to have
gotten lost.
Rich
next prev parent reply other threads:[~2017-03-01 2:25 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 [this message]
2017-03-01 8:03 ` Thomas Petazzoni
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=20170301022543.GD1520@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.com \
--cc=thomas.petazzoni@free-electrons.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).