From: Michael Weiser <michael@weiser.dinsnail.net>
To: gentoo-alt@lists.gentoo.org
Subject: Re: [gentoo-alt] Update clang failed (El Captain)
Date: Sun, 11 Sep 2016 02:05:49 +0200 [thread overview]
Message-ID: <20160911000549.jhleo5nn5ru5cea7@weiser.dinsnail.net> (raw)
In-Reply-To: <20160904150656.GA1112@gentoo.org>
Hi Fabian,
On Sun, Sep 04, 2016 at 05:06:56PM +0200, Fabian Groffen wrote:
> I've patched the function to return / in case xcodebuild returns nothing
> useful, such that we fall back to /usr/include, which makes the whole
> thing compile for me.
Well, I'd like to stress again that having Command Line Tools selected
as the currently selected Xcode does not seem to be supported by the
llvm cmake build system in Apple mode. As far as it's concerned someone
building llvm needs to have a proper Xcode selected using xcode-select
-s so it can find the SDKs within it.
Is it actually possible to have only Command Line Tools installed
(without Xcode) and get stuff to compile? I'm quite sure it was not in
the olden days (<= 10.6).
Also, I don't understand why there's a separate instance of the Command
Line Tools somewhere in /Library and how it happens to be the default
"Xcode" for some/most people. And also2, I don't understand why
xcode-select even accepts it as a parameter for -s. This is all very
weird.
Anyway, I thought of your solution as well while paddling along the
Peene. :) But on second thought I was wondering if we shouldn't patch
any SDK selection and osx-min-version/OSX_DEPLOYMENT_TARGET for the host
system (!) out of llvm/clang for prefix altogether. Prefix is always
meant for the host system, right? Without any of this selection stuff,
the compiler will fall back to the default include paths like
/usr/include anyways and we eliminate a whole lot of possible grief in
the future. IIRC I did this for 3.4.2 for exactly that reason but that
got lost on the move to cmake some time around 3.7, I think.
The only place I can think of where we'd need SDKs in the context of
prefix is if we wanted to provide a fully cross-capable Apple-like
toolchain for iOS and WatchOS and stuff like that. While binutils-apple
should be able to provide that I guess no-one's ever even tested or
played with it in that direction. And again, we'd need a proper Xcode
installed and selected to find and use the proper SDKs for that. Full
circle...
--
Thanks, Micha
Ich mag Kaba!
next prev parent reply other threads:[~2016-09-11 1:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-02 14:49 [gentoo-alt] Update clang failed (El Captain) Han H.
2016-09-02 15:44 ` Michael Weiser
2016-09-02 19:31 ` Han H.
2016-09-02 20:25 ` Michael Weiser
2016-09-04 15:06 ` Fabian Groffen
2016-09-06 7:55 ` Fabian Groffen
2016-09-06 7:56 ` Matt Michalowski
2016-09-11 0:05 ` Michael Weiser [this message]
2016-09-11 8:09 ` Fabian Groffen
2016-09-22 13:05 ` Michael Weiser
2016-12-23 10:57 ` Fabian Groffen
-- strict thread matches above, loose matches on Subject: below --
2016-09-06 21:37 Han H.
2016-09-06 21:37 ` Han H.
2016-09-07 7:36 ` Fabian Groffen
2016-09-08 19:36 ` Han H.
2016-09-03 23:36 Han H.
2016-08-24 16:40 Han H.
2016-08-29 12:35 ` Michael Weiser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160911000549.jhleo5nn5ru5cea7@weiser.dinsnail.net \
--to=michael@weiser.dinsnail.net \
--cc=gentoo-alt@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox