Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: mingw32
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash.exe' -DCONF_HOSTTYPE='i686'
-DCONF_OSTYPE='mingw32' -DCONF_MACHTYPE='i686-pc-mingw32'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/local/share/locale'
-DPACKA
Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: mingw32
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash.exe' -DCONF_HOSTTYPE='i686'
-DCONF_OSTYPE='mingw32' -DCONF_MACHTYPE='i686-pc-mingw32'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/local/share/locale'
-DPACKA
On 10/2/14, 4:46 AM, Владимир Белоусов wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: i686
> OS: mingw32
> Compiler: gcc
> Compilation CFLAGS: -DPROGRAM='bash.exe' -DCONF_HOSTTYPE='i686'
> -DCONF_OSTYPE='mingw32' -DCONF_MACHTYPE='i686-pc-mingw32'
> -DCONF_V
I am curious; why does Bash 4-3 patch 28 contain patches for y.tab.c.
Is this really what was intended.
-- John Wolfe Xinuos, Inc.
On 10/02/2014 07:33 AM, John Wolfe wrote:
> I am curious; why does Bash 4-3 patch 28 contain patches for y.tab.c.
> Is this really what was intended.
Yes, it is intended.
https://lists.gnu.org/archive/html/bug-bash/2014-09/msg00315.html
--
Eric Blake eblake redhat com+1-919-301-3266
Lib
Thanks for the clarification. I had not seen that e-mail and was
expecting the parse.y changes would result in y.tab.c being regenerated
in the build.I have since run across a system with an earlier
version of Bison that cannot handle the latest parse.y.
Thanks again.
-- John
On 10/2/2
On 9/30/14, 2:18 PM, Matthew Gessner wrote:
> I apologize, but I somehow sent this from gmail prematurely.
> I am having issues with patch working properly with the patches in
> bash-4.3-patches.
> Admittedly, I don't use patch very often, but having asked on freenode
> ##bash and others telling me
BASH PATCH REPORT
=
Bash-Release: 4.3
Patch-ID: bash43-029
Bug-Reported-by:Michal Zalewski
Bug-Reference-ID:
Bug-Reference-URL:
Bug-Description:
When bash is parsing a function definition that contains a
BASH PATCH REPORT
=
Bash-Release: 4.2
Patch-ID: bash42-052
Bug-Reported-by:Michal Zalewski
Bug-Reference-ID:
Bug-Reference-URL:
Bug-Description:
When bash is parsing a function definition that contains a
BASH PATCH REPORT
=
Bash-Release: 4.1
Patch-ID: bash41-016
Bug-Reported-by:Michal Zalewski
Bug-Reference-ID:
Bug-Reference-URL:
Bug-Description:
When bash is parsing a function definition that contains a
BASH PATCH REPORT
=
Bash-Release: 4.0
Patch-ID: bash40-043
Bug-Reported-by:Michal Zalewski
Bug-Reference-ID:
Bug-Reference-URL:
Bug-Description:
When bash is parsing a function definition that contains a
BASH PATCH REPORT
=
Bash-Release: 3.1
Patch-ID: bash31-022
Bug-Reported-by:Michal Zalewski
Bug-Reference-ID:
Bug-Reference-URL:
Bug-Description:
When bash is parsing a function definition that contains a here-doc
BASH PATCH REPORT
=
Bash-Release: 3.2
Patch-ID: bash32-056
Bug-Reported-by:Michal Zalewski
Bug-Reference-ID:
Bug-Reference-URL:
Bug-Description:
When bash is parsing a function definition that contains a here-doc
BASH PATCH REPORT
=
Bash-Release: 3.0
Patch-ID: bash30-021
Bug-Reported-by:Michal Zalewski
Bug-Reference-ID:
Bug-Reference-URL:
Bug-Description:
When bash is parsing a function definition that contains a here-doc
BASH PATCH REPORT
=
Bash-Release: 2.05b
Patch-ID: bash205b-012
Bug-Reported-by:Michal Zalewski
Bug-Reference-ID:
Bug-Reference-URL:
Bug-Description:
When bash is parsing a function definition that contains a here
Unlike other versions, bash-2.05b patch 11 is missing from
ftp.gnu.org. Will it be appear soon?
Thanks,
--
Sangyong
16 matches
Mail list logo