* cygwin can not be compiled with gcc 8.3.0 @ 2019-07-05 7:46 Biswapriyo Nath 2019-07-05 8:21 ` Houder 2019-07-17 15:13 ` Ken Brown 0 siblings, 2 replies; 11+ messages in thread From: Biswapriyo Nath @ 2019-07-05 7:46 UTC (permalink / raw) To: cygwin make command shows: ``` In file included from /d/newlib-cygwin/winsup/cygwin/aio.cc:10: /d/newlib-cygwin/winsup/cygwin/path.h: In member function 'path_conv& path_conv::eq_worker(const path_conv&, const char*)': /d/newlib-cygwin/winsup/cygwin/path.h:316:33: error: 'void* memcpy(void*, const void*, size_t)' writing to an object of type 'class path_conv' with no trivial copy-assignment; use copy-assignment or copy-initialization instead [-Werror=class-memaccess] memcpy (this, &pc, sizeof pc); ^ /d/newlib-cygwin/winsup/cygwin/path.h:133:7: note: 'class path_conv' declared here class path_conv ^~~~~~~~~ cc1plus: all warnings being treated as errors make[3]: *** [/d/newlib-cygwin/winsup/cygwin/../Makefile.common:41: aio.o] Error 1 ``` Am I doing anything wrong? I have installed all the required 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 ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: cygwin can not be compiled with gcc 8.3.0 2019-07-05 7:46 cygwin can not be compiled with gcc 8.3.0 Biswapriyo Nath @ 2019-07-05 8:21 ` Houder 2019-07-05 8:39 ` Houder 2019-07-05 17:03 ` Biswapriyo Nath 2019-07-17 15:13 ` Ken Brown 1 sibling, 2 replies; 11+ messages in thread From: Houder @ 2019-07-05 8:21 UTC (permalink / raw) To: cygwin 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 ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: cygwin can not be compiled with gcc 8.3.0 2019-07-05 8:21 ` Houder @ 2019-07-05 8:39 ` Houder 2019-07-05 17:03 ` Biswapriyo Nath 1 sibling, 0 replies; 11+ messages in thread From: Houder @ 2019-07-05 8:39 UTC (permalink / raw) To: cygwin On Fri, 05 Jul 2019 10:21:49, Houder wrote: [snip] > 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) Sorry. I should have written: gcc is invoked with different options when using cygport, among them: -std=gnu++98 ... > - 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 -- 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 ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: cygwin can not be compiled with gcc 8.3.0 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 ` (2 more replies) 1 sibling, 3 replies; 11+ messages in thread From: Biswapriyo Nath @ 2019-07-05 17:03 UTC (permalink / raw) To: cygwin > .. 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. -- 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 ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: cygwin can not be compiled with gcc 8.3.0 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:00 ` Sam Edge 2019-07-06 8:24 ` Houder 2 siblings, 1 reply; 11+ messages in thread From: Marco Atzeri @ 2019-07-05 18:48 UTC (permalink / raw) To: cygwin 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 ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: cygwin can not be compiled with gcc 8.3.0 2019-07-05 18:48 ` Marco Atzeri @ 2019-07-05 20:46 ` Biswapriyo Nath 2019-07-06 4:04 ` Sam Edge 0 siblings, 1 reply; 11+ messages in thread From: Biswapriyo Nath @ 2019-07-05 20:46 UTC (permalink / raw) To: cygwin Now I'm sure that the issue in cygwin source code. I've installed all the components. Also find same issue[1] provided a year ago. Cygwin needs some papering[2] for gcc 8.3.0. [1]: https://github.com/Tencent/rapidjson/issues/1246 [2]: https://github.com/mintty/mintty/commit/f7df4adf1775638b2aa75defb01822c0c21d6bcd -- 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 ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: cygwin can not be compiled with gcc 8.3.0 2019-07-05 20:46 ` Biswapriyo Nath @ 2019-07-06 4:04 ` Sam Edge 0 siblings, 0 replies; 11+ messages in thread From: Sam Edge @ 2019-07-06 4:04 UTC (permalink / raw) To: cygwin On 05/07/2019 21:46, Biswapriyo Nath wrote: > Now I'm sure that the issue in cygwin source code. I've installed all the > components. Also find same issue[1] provided a year ago. Cygwin needs some > papering[2] for gcc 8.3.0. > Hi again. I don't want to sound mean (https://cygwin.com/acronyms/#WJM) but ... Since you're the one who wants to build Cygwin using gcc 8.3.0, then why don't you create appropriate patches and submit them for consideration? https://cygwin.com/acronyms/#PTC and all that. Regards. -- 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 ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: cygwin can not be compiled with gcc 8.3.0 2019-07-05 17:03 ` Biswapriyo Nath 2019-07-05 18:48 ` Marco Atzeri @ 2019-07-06 4:00 ` Sam Edge 2019-07-06 8:24 ` Houder 2 siblings, 0 replies; 11+ messages in thread From: Sam Edge @ 2019-07-06 4:00 UTC (permalink / raw) To: cygwin On 05/07/2019 18:03, Biswapriyo Nath wrote: > > If it is deprecated then why the FAQ is not fixed yet? > As is normal, I'll think you'll find https://cygwin.com/acronyms/#PTC. -- 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 ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: cygwin can not be compiled with gcc 8.3.0 2019-07-05 17:03 ` Biswapriyo Nath 2019-07-05 18:48 ` Marco Atzeri 2019-07-06 4:00 ` Sam Edge @ 2019-07-06 8:24 ` Houder 2019-07-06 14:29 ` Brian Inglis 2 siblings, 1 reply; 11+ messages in thread From: Houder @ 2019-07-06 8:24 UTC (permalink / raw) To: cygwin On Fri, 5 Jul 2019 22:33:20, Biswapriyo Nath wrote: [snip] > > 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. Documents about using cygport? Well, sort of ... - https://cygwin.com/packages.html - https://cygwin.com/packaging-contributors-guide.html - - https://cygwinports.github.io/cygport/cygport.1.html - https://github.com/cygwinports/cygport/blob/master/README - https://cygwinports.github.io/cygport/toc_index.html Using (Cygwin) git as starting point? - https://cygwin.com/git/gitweb.cgi?p=newlib-cygwin.git - git is 'bleeding edge' (unstable by definition) cygwin.cygport file? - No, not present in git ... (not present in the git for newlib-cygwin) - a cygwin source tarball (to be found on any Cygwin mirror) is composed of a tarball, which represents git at a 'specific moment' in time plus the cygwin.cygport file - specific moment? Look for the 'cygwin-3_x_y' tags in git ... mirrors: https://cygwin.com/mirrors.html cygport build/ cygport package - the cygport build system is basically a wrapper around autoconf etc. (and build systems like cmake) - i.e. configure, make (Makefile) do not know about cygport Regards, Henri -- 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 ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: cygwin can not be compiled with gcc 8.3.0 2019-07-06 8:24 ` Houder @ 2019-07-06 14:29 ` Brian Inglis 0 siblings, 0 replies; 11+ messages in thread From: Brian Inglis @ 2019-07-06 14:29 UTC (permalink / raw) To: cygwin On 2019-07-06 02:24, Houder wrote: > On Fri, 5 Jul 2019 22:33:20, Biswapriyo Nath wrote: >>> 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. > Documents about using cygport? Well, sort of ... > - https://cygwin.com/packages.html > - https://cygwin.com/packaging-contributors-guide.html > - https://cygwinports.github.io/cygport/cygport.1.html > - https://github.com/cygwinports/cygport/blob/master/README > - https://cygwinports.github.io/cygport/toc_index.html > Using (Cygwin) git as starting point? > - https://cygwin.com/git/gitweb.cgi?p=newlib-cygwin.git > - git is 'bleeding edge' (unstable by definition) > cygwin.cygport file? > - No, not present in git ... (not present in the git for newlib-cygwin) > - a cygwin source tarball (to be found on any Cygwin mirror) is composed > of a tarball, which represents git at a 'specific moment' in time plus > the cygwin.cygport file > - specific moment? Look for the 'cygwin-3_x_y' tags in git ... > mirrors: https://cygwin.com/mirrors.html > cygport build/ cygport package > - the cygport build system is basically a wrapper around autoconf etc. > (and build systems like cmake) > - i.e. configure, make (Makefile) do not know about cygport Files like ....cygport and ....hint are for packaging and appear only in packaged sources not git repos. Install cygport package and dependencies then: $ cygstart /usr/share/doc/cygport/html/manual/index.html or https://cygwinports.github.io/cygport/ There are also source snapshots after Cygwin or newlib patches: https://cygwin.com/snapshots/ e.g. https://cygwin.com/snapshots/x86_64/cygwin-20190628-src.tar.xz Using cygport makes it relatively trivial to build upstream packages, from standard upstream mirrors or repos; using standard autotools, or configure and make; cross building libraries for Mingw; addon modules for girepository, lua, ocaml, perl, php, python2, python3, R, ruby, tcl, tex, vala; GUI libraries for widget sets like qt and wx; or desktop window manager environments like GNOME, KDE, LXDE, MATE, XFCE. Whereas cygport automates a lot of the standard upstream source download, build and package requirements, and Cygwin package repo upload, on the packager maintainer client; calm automates a lot of the standard uploaded Cygwin package repo checks, and maintenance of setup.ini entries, on the package repo primary server. Many source package builds also generate ...-debuginfo packages as well as binary packages for both architectures, so there are three packages added to each of the arch repos. Library packages may also generate separate ...-devel packages for each arch to support developer APIs, as well as the cyg....dlls in the binary packages. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. -- 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 ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: cygwin can not be compiled with gcc 8.3.0 2019-07-05 7:46 cygwin can not be compiled with gcc 8.3.0 Biswapriyo Nath 2019-07-05 8:21 ` Houder @ 2019-07-17 15:13 ` Ken Brown 1 sibling, 0 replies; 11+ messages in thread From: Ken Brown @ 2019-07-17 15:13 UTC (permalink / raw) To: cygwin; +Cc: Biswapriyo Nath [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain; charset="utf-8", Size: 400 bytes --] On 7/5/2019 3:45 AM, Biswapriyo Nath wrote: > It will be better if cygwin code is fixed for gcc 8.3.0 > instead of downgrading gcc version. This is now fixed. Ken \0ТÒÐÐ¥\a&ö&ÆVÒ\a&W\x06÷'G3¢\x02\x02\x02\x02\x02\x02\x06GG\x03¢òö7wvâæ6öÒ÷\a&ö&ÆV×2æFÖÀФd\x15\x13¢\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x06GG\x03¢òö7wvâæ6öÒöf\x17\x12ðФFö7VÖVçF\x17Föã¢\x02\x02\x02\x02\x02\x02\x02\x02\x06GG\x03¢òö7wvâæ6öÒöFö72æFÖÀÐ¥Vç7V'67&&R\x06æfó¢\x02\x02\x02\x02\x02\x06GG\x03¢òö7wvâæ6öÒöÖÂò7Vç7V'67&&R×6×\x06ÆPÐ Ð ^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2019-07-17 15:13 UTC | newest] Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2019-07-05 7:46 cygwin can not be compiled with gcc 8.3.0 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 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
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).