swiftlang / swiftlang/swift-corelibs-libdispatch

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

Open
#756 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug libdispatch
Dominant language
C
Stars
2.6k
Forks
496
Avg merge
2d 6h
Merged PRs (30d)
3

Description

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the failure on OS X 10.11.2 using autogen.sh, configure, and make. Start with allocator.c and follow the includes through internal.h to private/voucher_activity_private.h and the missing os/lock_private.h; done means the project builds successfully on El Capitan.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
build-system, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.