public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Iain Sandoe <idsandoe@googlemail.com>
To: ASSI <Stromeko@nexgo.de>
Cc: GCC Development <gcc@gcc.gnu.org>
Subject: Re: gcc-12+: D / phobos runtime
Date: Tue, 12 Sep 2023 22:13:02 +0100	[thread overview]
Message-ID: <50E95C58-546F-4BD6-BF9B-3AE977D1F082@googlemail.com> (raw)
In-Reply-To: <yddbke7tbz0.fsf@CeBiTec.Uni-Bielefeld.DE>



> On 12 Sep 2023, at 20:42, Rainer Orth <ro@cebitec.uni-bielefeld.de> wrote:
> 
> ASSI <Stromeko@nexgo.de> writes:
> 
>> Richard Biener via Gcc writes:
>>> I think we should fix this build problems.  Is there a bugzilla with
>>> more details about the problem?
>> 
>> No, I don't have an account on that bugtracker.
>> 
>> It is possible that the build would perhaps work, but the configure
>> check for the presence of a D compiler requires not just the compiler,
>> but also a runtime and thus fails on Cygwin.
> 
> Just try to configure gcc with --enable-libphobos, which overrides the
> default of LIBPHOBOS_SUPPORTED.  In quite a number of cases, this just
> works, but hasn't yet been verified.  You won't know until you try,
> though.

also you can add —with-libphobos-druntime-only to the GCC-11 build, that
makes a compiler sufficient for bootstrapping 12+ and is much less demanding
on completeness of OS support.

Iain


  reply	other threads:[~2023-09-12 21:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-03 11:44 ASSI
2023-09-12  8:23 ` Richard Biener
2023-09-12 19:16   ` ASSI
2023-09-12 19:42     ` Rainer Orth
2023-09-12 21:13       ` Iain Sandoe [this message]
2023-09-13  5:59         ` ASSI
2023-09-13  5:56       ` ASSI
2023-09-13  9:25         ` Rainer Orth
2023-09-12 20:08     ` Richard Biener
2023-09-13  6:15       ` ASSI

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=50E95C58-546F-4BD6-BF9B-3AE977D1F082@googlemail.com \
    --to=idsandoe@googlemail.com \
    --cc=Stromeko@nexgo.de \
    --cc=gcc@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).