From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp-out-so.shaw.ca (smtp-out-so.shaw.ca [64.59.136.138]) by sourceware.org (Postfix) with ESMTPS id 3C11E38930EF for ; Sun, 11 Apr 2021 18:47:56 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 3C11E38930EF Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=SystematicSw.ab.ca Authentication-Results: sourceware.org; spf=none smtp.mailfrom=brian.inglis@systematicsw.ab.ca Received: from [192.168.1.104] ([68.147.0.90]) by shaw.ca with ESMTP id Vf7ilTijwnRGtVf7jl98qe; Sun, 11 Apr 2021 12:47:55 -0600 X-Authority-Analysis: v=2.4 cv=cagXElPM c=1 sm=1 tr=0 ts=6073445b a=T+ovY1NZ+FAi/xYICV7Bgg==:117 a=T+ovY1NZ+FAi/xYICV7Bgg==:17 a=IkcTkHD0fZMA:10 a=PYOqKKcWAAAA:20 a=uYT-Tk0qkVT609LjNaIA:9 a=QEXdDO2ut3YA:10 Reply-To: cygwin-apps@cygwin.com To: cygwin-apps@cygwin.com References: <1e2133e8-d234-508f-5cc2-221ae8a3487c@dronecode.org.uk> From: Brian Inglis Organization: Systematic Software Subject: Re: [ITA] fortune-mod - please review Message-ID: Date: Sun, 11 Apr 2021 12:47:54 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.9.0 MIME-Version: 1.0 In-Reply-To: <1e2133e8-d234-508f-5cc2-221ae8a3487c@dronecode.org.uk> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-CA Content-Transfer-Encoding: 8bit X-CMAE-Envelope: MS4xfMOrnhaK8nMLBH68uEMuyFE+8R8Va8s3iIh7c2DaZgpV4FJkYxTGaM+3qBOfd5QfMz8EFELsIURKkcGEJN43lcI/FSZyhkDbSxuxIha9XldAC4u5KfsJ djuTw6amBqxqmlhdW6jk9uLp11WVy4R86iFX5xR4WfRODv4W0aK6xGKb833OpZt3VKLeh4J7B2NJ45GZRZzVrZKYU9fMdLCkVdk= X-Spam-Status: No, score=0.3 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, RCVD_IN_BARRACUDACENTRAL, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin-apps@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Cygwin package maintainer discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Apr 2021 18:47:57 -0000 On 2021-04-11 09:16, Jon Turney wrote: > On 09/04/2021 17:49, Brian Inglis wrote: >> Please review: >> - build now uses cmake >> - build requires unpackaged cpan module, installing with cpan in .cygport >> - x86 will not build with ninja, only if deinstalled >> - x86 applies but also regenerates source patches > Can you be a bit more explicit what the issues are on x86? Duh, yeah, realized that after hitting send! I'm unsure here because I've never before used cmake and ninja, which step is that's causing termination, and why when x86_64 succeeds? And I have rerun after wiping the build directory to ensure there's no cruft. >> See Google Drive for review files: >> https://drive.google.com/drive/folders/15500wdTKygcwVNB7-0XN9P6kd9pvByxJ > > For future reference, giving a link to the cygport, rather than having to dig it > out of the source package would ease review. Sorry, forgot that, it's been a while since I last copied dists to the web: time for another cyg-pkg-maint... script! >> DEPEND="cmake ninja perl" >> BUILD_REQUIRES="$DEPEND" > > build requires also seem to include Perl-Path-Tiny. Remembered and added that, removed ninja, and reran. Rerunning now I get perl-Path-Tiny not found although installed, and remember I got a complaint from setup_x86 about perl module version conflicts since then. I just ran cpan Path:Tiny which also updated Unicode::UTF8, Test::MockRandom, and Test::FailWarnings. Now the debug build succeeds as does the normal build. It looks like something about perl-Path-Tiny and/or prereqs was messed up here, but is no longer. So sorry for wasting time. >> cpan App::XML::DocBook::Builder > > This is less than ideal, as this means this gets executed as a side effect any > time the cygport is sourced (e.g. if you run 'cygport fortune-mod.cygport info'). > > If you really can't get this packaged, maybe it should be in the src_compile > instead? > > Apart from that, looks good. Yes, now I am past any ninja issues, will look at where I can put it in prep, compile, cmake, or ninja compile functions. Will recheck back as using cmake, ninja, cpan, and having source patch regeneration issues are new areas for me. I think patch regeneration may be due to the process modifying the sources directly, so I may be able to drop most patches. -- 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. [Data in binary units and prefixes, physical quantities in SI.]