From owner-freebsd-questions@freebsd.org Wed Aug 19 02:17:58 2020 Return-Path: Delivered-To: freebsd-questions@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4B59A3AE9D2 for ; Wed, 19 Aug 2020 02:17:58 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.187]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4BWWdv4NRvz41pQ for ; Wed, 19 Aug 2020 02:17:55 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([178.12.45.27]) by mrelayeu.kundenserver.de (mreue010 [212.227.15.167]) with ESMTPA (Nemesis) id 1MT9zD-1kEdiD2MXf-00UaOO; Wed, 19 Aug 2020 04:17:50 +0200 Date: Wed, 19 Aug 2020 04:17:50 +0200 From: Polytropon To: louis.forums@xs4all.nl Cc: "louis.forums@xs4all.nl" , Subject: Re: How to build a package from local source keeping all the original used (gnu autotools) build options !?? Message-Id: <20200819041750.5784a1f9.freebsd@edvax.de> In-Reply-To: <000701d67598$0c8aa560$259ff020$@xs4all.nl> References: <000001d67566$e2acd5a0$a80680e0$@xs4all.nl> <000701d67598$0c8aa560$259ff020$@xs4all.nl> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Provags-ID: V03:K1:Ce3AJKEsDAxZp92CnKGZW1qc6kXisaYBECy9IwKKdmI9YkcAOrR ZhMOxU6/OyD/sTCl4LRX7RsyIpxYVuLxxImhgf8zMjs0rcT5dnwwqEyit+ypfq1JB6Kw9dJ /Th7NYxaUBBzQJNGKkd5RD8KvCWds0jL/IQxeEGlhXIFUZoDnfEKn4hPwbX5ltXPI9+5dQG FpPNt72bsko907iBNoKkg== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:cT9iOXnZrWQ=:Hzq3fF/EI6Hxyt8dDVAVEd C+D+h+6+8CeVLW1tLOdsFMRBCiMo967h+1GrhepD4mZCdXKjedRSO4PE5CeNgMY0p3lz5MK4b KFkBhvgml8SxBl7iCE6XsQ50iENgmTh1FzKz7AeWrU9eUBPpUL+YuyFivFS2pGy8thLkfgsEp usBGcRaYUBC1IJdJJLK9dPytTGBE3HvuOLKvHCnjoAbGIG62M/fUch2WNqfdcVUaBGywlHgcw HdjDSgstfKbLLin06vcwjiOgwGp1xLs0LbUzhQtBWXxT2MJUVnHnCcqWNbKQCCyFpGncO4qKl eQReD3knr1SrocajgFD8AnTHpeqch0nCnNYLsbSxtL8L4BYlpFSrvd/UTR1nGC9KvJK4ajpeg eRqKh9ylnYQrnKC4gDJcL6fl0xolrVxjcQy26yx68ua1bTM/P38Sl8HMScCEotMY3LSv3BReo z9SG0DYujtVi1MaUs85Qvh5uISDnwKKpFFM41SE0OGGuuy+UMJDbDWXCFY23VGAmTQIRtms32 qKhUSDOgLGeL6B8XBi1Bogc3/A2fIp0m1wdgdawfPDTMElAi2eWyuEq6vU8pnzIa4If3FCLIM PrtqKch3VjvtkVDFjZEdKKJVHXhdGPiahAmdsZXyiYZXAG3ezl873AlAfRdgD9VJoDnfirEg9 gqPgbKFvexmtQwarbuD9G+yDgQ1ReSyFN0w4a1Lxf95hFbDT+1LIXVzdjvYIBTSSc3umSGB7C YEE7vbr/JYR1O8ZRxG1l4tBgNPkhgNGeueftACNYuM2o7c5W/49wnXH2Gse5jVvlzx+6uZgKl jOGfnAM8FRG5iQ6wnwYfwpJwmLpXW+6o+cpUxRtUNdi2edNwzHWOqI4KL55PJVIOTcVlHIN X-Rspamd-Queue-Id: 4BWWdv4NRvz41pQ X-Spamd-Bar: +++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of freebsd@edvax.de has no SPF policy when checking 212.227.126.187) smtp.mailfrom=freebsd@edvax.de X-Spamd-Result: default: False [3.60 / 15.00]; HAS_REPLYTO(0.00)[freebsd@edvax.de]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; HAS_ORG_HEADER(0.00)[]; SUBJECT_HAS_EXCLAIM(0.00)[]; FREEMAIL_TO(0.00)[xs4all.nl]; FROM_EQ_ENVFROM(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:8560, ipnet:212.227.0.0/16, country:DE]; MIME_TRACE(0.00)[0:+]; RECEIVED_SPAMHAUS_PBL(0.00)[178.12.45.27:received]; ARC_NA(0.00)[]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_SPAM_SHORT(0.20)[0.202]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[edvax.de]; AUTH_NA(1.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MID_CONTAINS_FROM(1.00)[]; RCVD_IN_DNSWL_NONE(0.00)[212.227.126.187:from]; R_SPF_NA(0.00)[no SPF record]; RWL_MAILSPIKE_POSSIBLE(0.00)[212.227.126.187:from]; FREEMAIL_CC(0.00)[xs4all.nl,freebsd.org]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-questions] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Aug 2020 02:17:58 -0000 On Tue, 18 Aug 2020 21:44:54 +0200, louis.forums@xs4all.nl wrote: > Hello, > > � Something is wrong with your mailer - it damaged commands so they become incorrect - oh, never mind, "Microsoft Outlook", let's see if I can fix that a bit. ;-) > After downloading a project from GitHub and making some changes, > I can build and install that project using the GNU autotools > > cd /var/git/ > > ./autogen.sh > > ./configure – option-A=/abc �– option-B=/def � � �etc (*required* options) ^ That is probably a case of "smart substitution" where you want to have "--", but got "– ", and I have no idea what "�" could have been in your original input (it appears in many places). > make > > make install > > make dist > > � > > However than I need to make a distribution package for that project > > cp /var/git// � cd /usr/ports/ > > cd /usr/ports// At this point, all make commands will use the options set for the port - which have not been set yet, i. e., the default port options will apply (as you have noticed in the result). The reason is that you built source outside (!) of the ports tree, and you set those options outside of the tree with means that are not part of the "ports options framework". > make makesum > > make stage > > make stage-qa > > make package > > That however does not work in the right way. As I said, it works in the _intended_ way. What you would need to do is to obtain the sources you need, usually by getting the most recent version of the ports tree (using svn), and then use "make config" so the ports framework can store the options. If you need sources that are _different_ from those provided by the ports collection, you could try to copy the source tree obtained by git into the work/ subdirectory of the port. > The problem is that “Port” is building the sources *again* > (in �cd /usr/ports//work// > > And more severe …. It is building the package without and > *required* options ……. (the same as defined for the original build!) That is exactly how it is supposed to work. :-) > So my question: “is how to build an package having the same > build settings as in the original autotools build” > (using same generated makefile, config etc.) It might sound strange, but you're trying a "non-supported thing", which doesn't mean it couldn't work. As I mentioned, try to use the generated source tree, copied into the ports tree, from within (!) the ports tree, by revisiting the "make config" screen to make sure all options are met as intended. > Perhaps !!?? the whole rebuild process by the port-tools is > not required at all (just my feeling(!) The rebuild will only be performed if an existing package does not meet the requirements of the options set (option mismatch) or if the version is different (version mismatch). In any other cases, existing built and/or installed packages will be kept. So the ports framework has no idea of which options have been applied to the files now available in distfiles/, that's why it needs to rebuild the (unsuited, because default option) packages as they do not exist yet. The best idea here probably is to use "ports only" as a means to build stuff to avoid both version mismatch and options mismatch. > If port could!!?? only do all the packaging stuff for the > already build files! ☹ 😊 > � That is probably possible. Have you looked into poudriere? For a "one-time action", using the regular ports tree might be okay, but if you're going to do updating and rebuilding more than once, maybe dedicating a poudriere installation with your custom options would be more convenient on the long run. I hope I did understand your intentions correctly. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...