public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Chances for llvm / clang update?
Date: Thu, 22 Apr 2021 13:11:24 +0200	[thread overview]
Message-ID: <513e44a6-50da-1851-f2db-9c3b1900805b@gmail.com> (raw)
In-Reply-To: <002e01d73751$e5066840$af1338c0$@uni-bremen.de>

On 22.04.2021 10:31, Andreas Heckel via Cygwin wrote:
> Hi,
> 
> Is there a chance for an "official" update of clang / llvm. Currently I see v8 here on Cygwin while llvm is now at v12.
> 
> I had tried to build v12 in Cygwin by simply running along the instructions on the llvm page. But I failed at a number of options / packages in the past and only got clang and a few tools like clang-format to run under Cygwin. I apologise, but I really have no clue about building anything properly for Cygwin (yet).
> 
> Cheers,
> Andreas
> 

Hi Andreas,

have you started looking to the current cygwin source package and 
patches for hints and guidance ?

Unfortunately the package is without maintainer, and volunteers to take 
over are lacking.

https://cygwin.com/packages/summary/clang.html

Motivation/Need is a good starting point for becoming a maintainer,
feel free to post here your issues in trying to compile it;
maybe we can help you

Marco

  parent reply	other threads:[~2021-04-22 11:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-22  8:31 Andreas Heckel
2021-04-22  9:47 ` Andrey Repin
2021-04-22 11:11 ` Marco Atzeri [this message]
2021-04-22 12:00   ` Andreas Heckel
2021-04-22 15:08 ` Brian Inglis
2021-04-22 15:45   ` Brian Inglis
2021-04-22 17:14     ` Andreas Heckel

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=513e44a6-50da-1851-f2db-9c3b1900805b@gmail.com \
    --to=marco.atzeri@gmail.com \
    --cc=cygwin@cygwin.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).