X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:message-id:from:reply-to:to:subject :references:in-reply-to:content-type; q=dns; s=default; b=u9oilB HZMsAM3dp1uS1mXgXPxTOyTCo5uw52rB6HIxYv+DEPADKsnzNZfXdogdWwebCiMD z1lemDS+gcvq6S6K9PNGST6SB7k7B409t3YNyq4vy56KuACvqhtjyBg5SJFSnWBX tglAR6RWzdR4WBO2mn3w9ZEMMVvkklHoa2y6s= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:message-id:from:reply-to:to:subject :references:in-reply-to:content-type; s=default; bh=eq+7l2LeC2fl LLr8ftVQ+qHWfyI=; b=r2YyyqTLJtgtcbS1tLgT/iZiDaIVESMutMn2H1Tk5EiE n3aRTqJuKgCUtoSnQEj6Y5u2bG+CgORYomm6qS7qE+FfBlJN+XRcrrhMnteySS4A DY05Pf26eDsVHfxU7JuAbnrdJJYypZ9MW7dgxIMlORjvIzZLlkitRrOYQPS10cY= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.1 required=5.0 tests=AWL,BAYES_00,KAM_NUMSUBJECT,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.1 spammy=mirror, tarballs, sk:cygwinp, sk:newlib X-HELO: lb2-smtp-cloud8.xs4all.net Date: Sat, 06 Jul 2019 10:24:20 +0200 Message-ID: <8040fde0c0402fc3361515edbdd26d01@smtp-cloud8.xs4all.net> From: Houder Reply-To: cygwin AT cygwin DOT com To: cygwin AT cygwin DOT com Subject: Re: cygwin can not be compiled with gcc 8.3.0 References: <3a8155076bbb80ecf8a7a8d3076a331f AT smtp-cloud8 DOT xs4all DOT net> In-Reply-to: Content-Type: text/plain; charset=UTF-8; format=fixed User-Agent: mua.awk 0.99 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