On 12/7/16 11:46 PM, Mike Frysinger wrote:
> On 07 Dec 2016 19:09, Chet Ramey wrote:
>> On 12/5/16 11:01 PM, Mike Frysinger wrote:
>>> using ^ as an anchor doesn't seem that much better than %
>>
>> Ultimately, autoconf is the right way to do this.
>
> sure, you could add bashbug to AC_OUTPUT and
On 07 Dec 2016 19:09, Chet Ramey wrote:
> On 12/5/16 11:01 PM, Mike Frysinger wrote:
> > using ^ as an anchor doesn't seem that much better than %
>
> Ultimately, autoconf is the right way to do this.
sure, you could add bashbug to AC_OUTPUT and adapt all the vars to
be AC_SUBST. i assume you'll
On 12/5/16 11:01 PM, Mike Frysinger wrote:
> using ^ as an anchor doesn't seem that much better than %
Ultimately, autoconf is the right way to do this.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CW
> using ^ as an anchor doesn't seem that much better than %
>
> autoconf uses & and |, but they tend to do it for vars where it's
> unlikely those will show up (like path vars)
>
> how about something like:
> @s=$$(printf '\001'); \
> sed -e "s$$s!MACHINE!$$s$(Machine)$$s" ...
Good i
On 04 Dec 2016 22:53, Vladimir Marek wrote:
> Studio compiler may use things like '-xregs=no%frameptr' for example.
>
> Thank you
> --
> Vlad
> # Our compiler flags contain percent sign which get mixed up with percent sign
> # seprators used by sed.
>
> # Submitted to bug-bash@gnu.org
>
Studio compiler may use things like '-xregs=no%frameptr' for example.
Thank you
--
Vlad
# Our compiler flags contain percent sign which get mixed up with percent sign
# seprators used by sed.
# Submitted to bug-bash@gnu.org
--- Makefile.in 2014-01-25 13:27:30.0 -0800
+++ Makefil
