On Fri, Apr 19, 2019 at 09:59:39AM -0700, we recorded a bogon-computron collision of the <[email protected]> flavor, containing: > I tweaked these scripts but haven't check them in yet. Found another > problem though: In build/scripts/ none of the scripts are marked executable > now.
That's because the Makefile.am only sets those as executable in the install hook at the time you do "make install". It worked in the olden days because the scripts were already present unmodified (not generated from .in files) and were already executable in the source tree. Now that they're being generated from .in files (that are still executable) and dumped into the build tree, nobody's setting the uninstalled files to executable, and configure doesn't preserve the permissions of the .ins when it creates the real ones. > I'll check in my tweaks to the scripts in a sec, but won't include the > executable stuff. Tom? Looking into it now. > On Fri, Apr 19, 2019 at 9:25 AM Curt Mills <[email protected]> wrote: > > > Thanks Tom Russo! Also Jason Godfrey for approving the pull request. > > > > I still see "x = `dirname $0` in four of the scripts that end up in > > build/scripts/ > > > > Also see "$dirname=dirname($0);" but haven't investigated whether $dirname > > gets used in those later in the scripts, so that may or may not be > > something that needs tweaking. > > > > -- > > Curt, WE7U http://we7u.wetnet.net > > http://www.sarguydigital.com > > > > > -- > Curt, WE7U http://we7u.wetnet.net http://www.sarguydigital.com > _______________________________________________ > Xastir-dev mailing list > [email protected] > http://xastir.org/mailman/listinfo/xastir-dev -- Tom Russo KM5VY Tijeras, NM echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m] _______________________________________________ Xastir-dev mailing list [email protected] http://xastir.org/mailman/listinfo/xastir-dev
