From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: cygwin can not be compiled with gcc 8.3.0
Date: Fri, 05 Jul 2019 18:48:00 -0000 [thread overview]
Message-ID: <151eaa1a-28ba-1fdc-b043-9b8d5febf8a6@gmail.com> (raw)
In-Reply-To: <CALK-3mKKB3ZcRczoPaGym97mgNe8pskEEW2B3nuPVou5RqNvcg@mail.gmail.com>
Am 05.07.2019 um 19:03 schrieb Biswapriyo Nath:
>> .. uhm, sort of ... [1] is deprecated
>
> If it is deprecated then why the FAQ is not fixed yet?
>
>> cygwin is built using cygport ...
>
> Is there any docs about it? I don't find the cygwin.cygport file in source
> tree. Also I don't use source tarballs, git is my first choice. Also the
> configure script or Makefile didn't warn me that I've not that cygport
> package/script.
>
it is included in the source package, as reported on
https://cygwin.com/packages/x86/cygwin-src/cygwin-3.0.7-1-src
cygwin-src: The UNIX emulation engine (source)
2019-04-30 18:07 0 cygwin-3.0.7-1.src/
2019-04-30 18:07 3090 cygwin-3.0.7-1.src/cygwin.cygport
2019-04-30 18:07 13425098
cygwin-3.0.7-1.src/newlib-cygwin-3.0.7.tar.bz2
---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2019-07-05 18:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 7:46 Biswapriyo Nath
2019-07-05 8:21 ` Houder
2019-07-05 8:39 ` Houder
2019-07-05 17:03 ` Biswapriyo Nath
2019-07-05 18:48 ` Marco Atzeri [this message]
2019-07-05 20:46 ` Biswapriyo Nath
2019-07-06 4:04 ` Sam Edge
2019-07-06 4:00 ` Sam Edge
2019-07-06 8:24 ` Houder
2019-07-06 14:29 ` Brian Inglis
2019-07-17 15:13 ` Ken Brown
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=151eaa1a-28ba-1fdc-b043-9b8d5febf8a6@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).