[swift-corelibs-dev] Duplicate definition of va_list on Arm
william at housedillon.com
Fri Aug 19 22:41:19 CDT 2016
True enough. In that case, would be acceptable to match by architecture and skip the import on arm?
> On Aug 19, 2016, at 5:56 PM, Pierre Habouzit <pierre at habouzit.net> wrote:
> the include was added to dispatch specifically to allow dispatch_io to build on intel so your patch I think would break Intel.
> I think the general problem is likely that glibc is not module friendly today.
>> On Aug 19, 2016, at 11:53 AM, William Dillon via swift-corelibs-dev <swift-corelibs-dev at swift.org <mailto:swift-corelibs-dev at swift.org>> wrote:
>> Hi all,
>> In corelibs-foundation project we've been using a patch based on https://github.com/apple/swift-corelibs-foundation/pull/399/files <https://github.com/apple/swift-corelibs-foundation/pull/399/files> for quite some time (summary: remove #include <stdio.h>). The PR hasn't gotten any where for various reasons. Currently, I've gotten libdispatch working on arm, but it requires a fix that's essentially identical. It is part of a PR available here: https://github.com/apple/swift-corelibs-libdispatch/pull/155 <https://github.com/apple/swift-corelibs-libdispatch/pull/155>
>> I'd like to get this moving forward in both cases, and I'd like to bring it to the list. What exactly is stdio.h bringing in? I realize the comment identifies __off_t, but at least on arm that's being provided elsewhere. Furthermore, __off_t is defined in several places.
>> Are there any suggestions for what a satisfactory solution would be to address the duplicate definition of va_list on arm that does not negatively impact other platforms?
>> - Will
>> swift-corelibs-dev mailing list
>> swift-corelibs-dev at swift.org <mailto:swift-corelibs-dev at swift.org>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-corelibs-dev