From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] system bash replacement
Date: Mon, 11 Sep 2017 10:28:19 +0200 [thread overview]
Message-ID: <20170911082819.johu2ttb5j2mmoky@pengutronix.de> (raw)
In-Reply-To: <1504947574.21495.381.camel@erwinrol.com>
Hi,
On Sat, Sep 09, 2017 at 10:59:34AM +0200, Erwin Rol wrote:
> I have several (older) CentOS 6.X (and even 5.X :-/ ) systems that have
> bash 4.1.2 which is to old for newer ptxdist releases.
>
> Ptxdist checks for several tools and places links in its $PTXDIR/bin/
> dir. Tools include cp, ls, awk, and bash. The ptxdist $PTXDIR/bin/ dir
> is placed in PATH so those links in $PTXDIR/bin/ are found first.
>
> But! all ptxdist scripts have "#!/bin/bash" in them, so that bash link
> in $PTXDIR/bin/ is never used.
>
> I have some success by replacing "#!/bin/bash" with "#!/usr/bin/env
> bash" but before I go ahead with that I would like to hear if someone
> already tried that and failed (or succeeded).
>
> BTW the same for the python link, scripts with #!/bin/python will not
> use it.
I've never tried this, but I had some ideas:
1. We already set SHELL=$(PTXDIST_TOPDIR)/bin/bash in
rules/other/Toplevel.make so that handles some of it.
2. PTXdist itself is a problem. I had some ideas about re-executing ptxdist
if the shell is different from $(PTXDIST_TOPDIR)/bin/bash.
That should help for PTXdist. Most files are not directly executed so the
shebang is just cosmetics.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2017-09-11 8:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-09 8:59 Erwin Rol
2017-09-11 8:28 ` Michael Olbrich [this message]
2017-09-11 8:59 ` Erwin Rol
2017-09-13 14:57 ` Michael Olbrich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170911082819.johu2ttb5j2mmoky@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox