From: Matt Michalowski <nextdayflight@gmail.com>
To: gentoo-alt@lists.gentoo.org
Subject: Re: [gentoo-alt] Update clang failed (El Captain)
Date: Tue, 6 Sep 2016 17:56:26 +1000 [thread overview]
Message-ID: <CAFs8pHYnBhLdvGjVS_thm6h0qJ3_bSuR=PnzYzM0JqAf=pu3_A@mail.gmail.com> (raw)
In-Reply-To: <20160906075512.GA10667@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2068 bytes --]
I had the same problem. Your fixes have worked for me.
Thanks Fabian.
Matt.
On 6 September 2016 at 17:55, Fabian Groffen <grobian@gentoo.org> wrote:
> Han,
>
> Does it work for you now with my fixes?
>
> Thanks,
>
> Fabian
>
>
> On 04-09-2016 17:06:56 +0200, Fabian Groffen wrote:
> > Han, Michael,
> >
> > I've got the exact same scenario on my El Capitan. With the help of
> > Michael's pointers, I managed to track down what goes wrong.
> >
> > Michael pointed out there is a call to some function that will return an
> > empty string for systems where xcodebuild barfs, and the later code
> > checks if the variable is set. Obviously it is (to an empty string),
> > with a result of "-isysroot".
> >
> > 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.
> >
> > Fabian
> >
> > On 02-09-2016 19:31:02 +0000, Han H. wrote:
> > > Hi Michael,
> > >
> > > Yes /usr/include is there. I am not able to install mac packages so an
> > > update must not be run by me.
> > >
> > > $ xcodebuild -version -sdk macosx
> > > xcode-select: error: tool 'xcodebuild' requires Xcode, but active
> developer
> > > directory '/Library/Developer/CommandLineTools' is a command line
> tools
> > > instance
> > >
> > > I saw in the check
> > >
> > > -- Finding valid architectures for osx...
> > > -- OSX supported arches: i386;x86_64;x86_64h
> > > -- Finding valid architectures for 10.4...
> > > -- OSX 10.4 supported arches: i386;x86_64;x86_64h
> > > -- Compiler-RT supported architectures: i386;x86_64;x86_64h
> > >
> > > does that mean it detects my system is 10.4?
> > >
> > > I also tried 3.8.1-r2 but same thing happens. llvm-3.9.0_rc3 requires
> more
> > > upgrade (cmake...) and not sure if uncomplete upgrade (if cmake
> updates and
> > > llvm remains 3.7.1) will cause a broken toolchain.
> > >
> > > Thanks,
> > > Han
> > >
> >
> > --
> > Fabian Groffen
> > Gentoo on a different level
>
>
>
> --
> Fabian Groffen
> Gentoo on a different level
>
[-- Attachment #2: Type: text/html, Size: 2917 bytes --]
next prev parent reply other threads:[~2016-09-06 7:56 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 [this message]
2016-09-11 0:05 ` Michael Weiser
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='CAFs8pHYnBhLdvGjVS_thm6h0qJ3_bSuR=PnzYzM0JqAf=pu3_A@mail.gmail.com' \
--to=nextdayflight@gmail.com \
--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