From: Houder <houder@xs4all.nl>
To: cygwin@cygwin.com
Subject: Re: cygwin can not be compiled with gcc 8.3.0
Date: Fri, 05 Jul 2019 08:21:00 -0000 [thread overview]
Message-ID: <3a8155076bbb80ecf8a7a8d3076a331f@smtp-cloud8.xs4all.net> (raw)
In-Reply-To: <CALK-3mKzG-1zhMQE5yV1fZyp_hWp1cRyOBQM4Tfqyins8KEfRA@mail.gmail.com>
On Fri, 5 Jul 2019 13:15:46, Biswapriyo Nath wrote:
[snip]
> Am I doing anything wrong? I have installed all the required
.. uhm, sort of ... [1] is deprecated
cygwin is built using cygport ...
- install the cygport package (subsequently invoke "man cygport" from bash)
- using cygport to build cygwin requires the cygwin.cygport file in the Cygwin
source tarball (will not use gcc 8.3.0)
- extract the source tarball, then ...
Reminder (zie man cygport)
cygport <options> cygwin.cygport prep create working directory, unpack sources and apply patches
cygport <options> cygwin.cygport compile run all compiliation steps (including configure)
cygport <options> cygwin.cygport install installinto a DESTDIR, and run post-installation steps
cygport <options> cygwin.cygport package create binary and source package
cygport <options> cygwin.cygport finish delete working directory
Regards,
Henri
> packges[1]. It will be better if cygwin code is fixed for gcc 8.3.0
> instead of downgrading gcc version.
>
> [1]: https://cygwin.com/faq.html#faq.programming.building-cygwin
--
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 8:21 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 [this message]
2019-07-05 8:39 ` Houder
2019-07-05 17:03 ` Biswapriyo Nath
2019-07-05 18:48 ` Marco Atzeri
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=3a8155076bbb80ecf8a7a8d3076a331f@smtp-cloud8.xs4all.net \
--to=houder@xs4all.nl \
--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).