public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: Go or Rust Packages?
Date: Sat, 05 Feb 2022 22:25:32 +0100	[thread overview]
Message-ID: <87pmo1xayb.fsf@Rainer.invalid> (raw)
In-Reply-To: <87ee4i9v3a.fsf@Otto.invalid> (ASSI's message of "Fri, 04 Feb 2022 22:32:09 +0100")

ASSI writes:
> Go might be salvageable if the go frontend to go is usable, I haven't
> had time to look at that.

I've went ahead and tried to activate go in gcc and it doesn't even get
past the very beginning of confdigure:

--8<---------------cut here---------------start------------->8---
configure: WARNING: go not supported for this target
configure: error: 
The following requested languages could not be built: go
--8<---------------cut here---------------end--------------->8---

Pulling out this and another stop successfully configures and actually
builds a gccgo executable sometime later.  If any of this actually works
remains to be seen.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

DIY Stuff:
http://Synth.Stromeko.net/DIY.html

  reply	other threads:[~2022-02-05 21:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-01 21:22 Orphaning fzf Adam Dinwoodie
2022-02-02  9:44 ` Corinna Vinschen
2022-02-04  5:27   ` Go or Rust Packages? Brian Inglis
2022-02-04  6:57     ` Marco Atzeri
2022-02-04  9:23       ` Jan Nijtmans
2022-02-04 21:17         ` Marco Atzeri
2022-02-04 21:32       ` ASSI
2022-02-05 21:25         ` Achim Gratz [this message]
2022-02-06 11:09           ` Achim Gratz
2022-02-04  8:14     ` Mark Geisert
2022-02-04  9:12       ` Corinna Vinschen

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=87pmo1xayb.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=cygwin-apps@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).