public inbox for gentoo-alt@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Weiser <michael@weiser.dinsnail.net>
To: gentoo-alt@lists.gentoo.org
Subject: Re: [gentoo-alt] Update clang failed (El Captain)
Date: Thu, 22 Sep 2016 15:05:24 +0200	[thread overview]
Message-ID: <20160922130524.zk46mlmkavo2ls4t@weiser.dinsnail.net> (raw)
In-Reply-To: <20160911080944.GB759@gentoo.org>

Hello Fabian,

On Sun, Sep 11, 2016 at 10:09:44AM +0200, Fabian Groffen wrote:

> I think I understand your points:
> - I don't understand why systems get messed up xcode-wise either, but
>   I'm sure not everyone has root access to fix it
> - My current workaround works currently, indeed, dunno about the future

Agreed.

> - Doing more patchwork is discouraged by llvm maintainer(s?),
>   didn't like my above patch, and in fact told me to leave the llvm
>   ebuilds alone because the patches are not acceptable/accepted by
>   upstream, if you got ideas for this...

Under these conditions I don't have any great ideas either. Obviously,
the right way to do it[tm] is to find someone willing to become llvm
upstream contributor/maintainer with a standing to get our patches in.
I've tried something similar on a much lower level on several occasions
and can say that it's a major undertaking that will gobble that someone
up. So I'm not volunteering.

> - The libcxx{abi,-headers} situation needs love too, since we have
>   different ebuilds for Prefix

I haven't forgotten about the "switch to cmake"-part of Bug #538364 but seem
to have trouble motivating myself to touch it since the current scheme
works reasonably well. :-/
-- 
Regards,
Michael


  reply	other threads:[~2016-09-22 14:01 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
2016-09-11  8:09         ` Fabian Groffen
2016-09-22 13:05           ` Michael Weiser [this message]
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=20160922130524.zk46mlmkavo2ls4t@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