[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 22 Jun 2016 15:41:50 -0400
From: Rich Felker <dalias@...c.org>
To: musl@...ts.openwall.com
Subject: Re: Issues when building libcxx libcxxabi with MUSL
On Wed, Jun 22, 2016 at 09:38:17PM +0200, Julien Ramseier wrote:
> Hi Zhao,
>
> Not sure how you did build llvm-libcxx, but the only issue I encountered myself is
> the use of PTHREAD_MUTEX_INITIALIZER in libcxx include/__mutex_base.
> musl uses volatile types in its pthread_mutex_t struct and C++11 does not allow them
> with constexpr member initializers. This rule has been relaxed in C++14.
Note that the code using them is still formally/conceptually buggy.
POSIX does not permit using these initializers as values. They can
only be used as initializers for objects with static storage duration.
A "mutex value" makes no sense; mutexes are objects not values.
Rich
> > Le 22 juin 2016 à 21:24, Zhao, Weiming <weimingz@...eaurora.org> a écrit :
> >
> > Hi,
> >
> > I tried to build libcxx/libcxxabi using MUSL. Compiler is clang.
> >
> > The build issues I got:
> >
> > 1) In libcxx, it complains that some pthread structure is not completely initialized.
> >
> > 2) Some types like max_align_t are already defined in clang's include.
> >
> > 3) libcxx can't find it's own math.h
> >
> > A patch is attached. Please review if the changes are correct.
> >
> >
> > Thank,
> >
> > Weiming
> >
> >
> >
> >
> > --
> > Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
> >
> > <build_libcxx.patch>
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
