• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: How are we supposed to build Libc?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How are we supposed to build Libc?

  • Subject: Re: How are we supposed to build Libc?
  • From: Daniel Peebles <email@hidden>
  • Date: Wed, 12 Oct 2016 19:39:54 -0400
Did you make any progress here?

It would be nice if the Apple projects were easily buildable outside the company but that doesn't appear to be a big priority. As a result, Sam Marshall put together a very useful "private OSX SDK" with headers she pulled from all over the opensource.apple.com releases. Some of the headers were even reverse-engineered as I recall, because sometimes Apple just leaves out some crucial pieces that prevent building the software outside the company.


On Fri, Sep 30, 2016 at 11:43 AM, Stéphane Sudre <email@hidden> wrote:

On 30 sept. 2016, at 17:16, Jeremy Huddleston Sequoia wrote:

> Given the output below, it looks like you're building it against the DevSDK (the SDK installed to / when you install the Xcode Command Line Tools package) because there is no -isysroot command line argument.  At minimum, you should be building it against an SDK that matches the OS that it came with.
>
> There's nothing to "run" so Build & Run doesn't really make sense.  I suggest you start from the command line like:
>
> xcodebuild -sdk macosx -target libsystem_c.dylib
>

Noted.

> You may run into issues due to internal headers being included (sys/_pthread/_pthread_types.h isn't such a case, it's in /usr/include).  If that's the case, you'll want to fix that up yourself either by grabbing the internal headers out of other OSS packages or disabling that functionality in Libc.

Will try on a 10.11.5 system as on 10.12, the command line call results in 1,267 errors at build.

Thanks.


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden
  • Prev by Date: Debugger permissions in macOS 10.12
  • Previous by thread: Debugger permissions in macOS 10.12
  • Index(es):
    • Date
    • Thread