On 18.07.2018 14:58, Jeffrey Walton wrote: > On Wed, Jul 18, 2018 at 7:14 AM, Tim Rühsen <tim.rueh...@gmx.de> wrote: >> Maybe it's an bash/sh incompatibility. Anyways - what does 'make >> install' do !? It basically copies the 'wget' executable into a >> directory (e.g. /usr/local/bin/) that is listed in your PATH env variable. >> >> You can do that by hand. If you want the updated man file, copy wget.1 >> into your man1 directory (e.g. /usr/local/share/man/man1/). > > I see what was happening. After unpacking this patch was applied: > > sed -e 's|$(LTLIBICONV)|$(LIBICONV)|g' fuzz/Makefile.am > > fuzz/Makefile.am.fixed > mv fuzz/Makefile.am.fixed fuzz/Makefile.am > > But it lacked this: > > touch -t 197001010000 fuzz/Makefile.am > > So Autotools was trying to regenerate all of its shit. Autotools sucks > so bad I cringe when I have to work with it. What a miserable set of > programs.
This really isn't a fault of autotools :-) You simply didn't have the things installed that you needed for amending Makefile.am and rebuilding. So what Darshit says would be an option: build a tarball from the latest source (or with your changes) on *any* development machine, copy the tarball over to the destination machine and simply './configure && make && sudo make install'. No autotools needed ! Another option would be that we make up a new release 1.19.6. And another one: Don't touch Makefile.am - instead amend Makefile. Regards, Tim
signature.asc
Description: OpenPGP digital signature