Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SR-449] swift-corelibs-libdispatch doesn't build on El Capitan #756

Open
drewcrawford opened this issue Jan 3, 2016 · 3 comments
Open

Comments

@drewcrawford
Copy link
Contributor

Previous ID SR-449
Radar None
Original Reporter @drewcrawford
Type Bug
Environment

OSX 10.11.2 (15C50)

Additional Detail from JIRA
Votes 0
Component/s libdispatch
Labels Bug
Assignee None
Priority Medium

md5: c2d3e7f105ad4e500d99318787216438

Issue Description:

$ brew install libtool automake autoconf
$./autogen.sh
$ ./configure
$ make

/bin/sh ../libtool  --tag=CC   --mode=compile clang -DHAVE_CONFIG_H -I. -I../config  -I.. -I.. -I../private -I../os  -Wall -fvisibility=hidden -momit-leaf-frame-pointer    -fblocks -g -O2 -c -o allocator.lo allocator.c
libtool: compile:  clang -DHAVE_CONFIG_H -I. -I../config -I.. -I.. -I../private -I../os -Wall -fvisibility=hidden -momit-leaf-frame-pointer -fblocks -g -O2 -c allocator.c  -fno-common -DPIC -o .libs/allocator.o
In file included from allocator.c:21:
In file included from ./internal.h:138:
../private/voucher_activity_private.h:493:10: fatal error: 'os/lock_private.h' file not found
#include <os/lock_private.h>
         ^
1 error generated.
make[2]: *** [allocator.lo] Error 1
make[1]: *** [all] Error 2
make: *** [all-recursive] Error 1
@swift-ci
Copy link

Comment by Chris Bailey (JIRA)

I'm not sure if it helps, but this was (briefly) discussed on the mailing list as a known issue in early Dec:

https://lists.swift.org/pipermail/swift-corelibs-dev/Week-of-Mon-20151207/000123.html

So I don't think your missing anything - currently the swift-corelibs-libdispatch project can't be built on El Capitan because of the missing dependency.

@drewcrawford
Copy link
Contributor Author

Wow that... is a long time for libdispatch to be broken on the one platform where it is actually supported!

Thanks though, I guess I will not try to work on it yet...

@Dante-Broggi
Copy link

Is this resolved, or no longer valid? If either, this should be closed.

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
@shahmishal shahmishal transferred this issue from apple/swift May 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants