From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 38016 invoked by alias); 4 Mar 2019 18:09:39 -0000 Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm Precedence: bulk Sender: cygwin-apps-owner@cygwin.com List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps@cygwin.com Received: (qmail 37999 invoked by uid 89); 4 Mar 2019 18:09:38 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=BAYES_00,FREEMAIL_FROM,FROM_LOCAL_NOVOWEL,HK_RANDOM_ENVFROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no version=3.3.2 spammy=Canada, canada, granted, tape X-HELO: mail-qt1-f172.google.com Received: from mail-qt1-f172.google.com (HELO mail-qt1-f172.google.com) (209.85.160.172) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 04 Mar 2019 18:09:36 +0000 Received: by mail-qt1-f172.google.com with SMTP id j36so6121448qta.7 for ; Mon, 04 Mar 2019 10:09:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=bwZKXaMxUopEOqlp1+cu4JfY0jWModWk1Uww/9rBZ64=; b=GyiBHQQYV7Ap7DpBY9EnHm5xEe6e6pu8IbNhmQmKeQEDeRTi0q3+G7qZqkJ31X6K4C 7buMMI0KQpTBIHw/xAVfQE9e+G+R7AnhHXvhO3OJ+VIhrdKXJ9yWf8/LIIUU6ayeTvOM QQV+cimQ9HV2L6OjiQ5yV/8P71cdc8eZ5vc8IRgly1RwoWYUbLhxv7kIIFtCKqrH1QMB 5DHarJw0o3NBBYKtf7nhvnbtX3HWwGjV8x1C4s3/qJmTTEtoADY+U6Ap9P+Vyx0CPOVL jmiIkVK6ezuqv64FDcSmvT5RtwChxRToY8iBmQM3+KklRVKtopQgdbJTG+XpNEF6nS54 xhjw== MIME-Version: 1.0 References: In-Reply-To: From: Doug Henderson Date: Mon, 04 Mar 2019 18:09:00 -0000 Message-ID: Subject: Re: rebuilding python pip from source To: Cygwin Apps Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2019-03/txt/msg00002.txt.bz2 On Mon, 4 Mar 2019 at 09:39, Yaakov Selkowitz <> wrote: > > On Mon, 2019-03-04 at 04:57 -0700, Doug Henderson wrote: > > I am trying to rebuild the python37-pip package from source. > > Checking source in setup gives me /usr/src/python-pip-19.0.2-1.src/ > > When I try to build the package I get an error: > > > > $ cygport python-pip.cygport all > > *** ERROR: python27-pip is required to build this package > > > > Initially I got errors saying python36-pip, etc. were required, so I > > installed the binary and source packages for them, but there is no > > python27-pip or python2-pip package available to install. > > There is: https://cygwin.com/packages/x86_64/python27-pip/ I have that package installed. I want to be able to compile it from source, as a small step towards my ultimate goal. > > Ultimately I intend to completely rebuild from source both Python 2.7 and 3.7 > > and all the other packages named "^python.*". > > To what end? Because that is a right granted to me by the open source license under which some source code is released. Perhaps not explicitly by the Python and cygwin licences, but as an implied ability. What is the point of having a source package but to be able to rebuild the binary package. For me, it is more a learning process than anything else. I understand that you are the maintainer of the main Python packages, as well as many other related packages. Thank you for your contributions. I must keep you very busy, so automating the process using cygport makes a lot of sense. There are other python related packages maintained by others, or orphaned. Starting with pip seemed a good idea. Previously, before python3 was available on cygwin, I rebuilt python2 from source, and also attempted to port python3. I don't think I used cygport back then. Back in the early 80's I received gcc, emacs, X11, sun-rpc, etc. on 9 track tape, and built them on the wide variety of Unix workstations and servers in our office. And over the years I built Python every where I had a C compiler but no Python. Building software from a source distribution is not a problem for me. Currently I maintain the cygwin expat package. I suspect that the Python build process requires some manual steps in addition to perhaps running cygport in small step, or even editing the.cygport file between those steps, that are not obvious from examining the source package. I suspect there is a recipe that you use every time you build a new Python release. I hope you can share that with me. I am thinking about porting some other packages to cygwin, and Python represents a complex system of packages that appears to make good use of cygport. Along the way, I need a better understanding of cygport, and how to wrap a provided build system within it. Thanks, Doug -- Doug Henderson, Calgary, Alberta, Canada - from gmail.com