On Tue, Nov 18, 2008 at 07:09:19PM +0000, Dan wrote: [...] > Questions: > 1) Does my guide (see below) for applying the patches make sense? I > couldn't see any other way to make this work without creating the symbolic > links and using the -p0 option as recommended by Chet. The steps in the > guide work on both Fedora 9 and Asus Eee PC Xandros, i.e. patch does not > give any errors or warnings on either. [...]
I'm not sure why you need to do all that. Here, I do: ~/install/BASH$ ls bash-3.2.tar.gz bash32* bash32-001 bash32-008 bash32-015 bash32-022 bash32-029 bash32-036 bash32-002 bash32-009 bash32-016 bash32-023 bash32-030 bash32-037 bash32-003 bash32-010 bash32-017 bash32-024 bash32-031 bash32-038 bash32-004 bash32-011 bash32-018 bash32-025 bash32-032 bash32-039 bash32-005 bash32-012 bash32-019 bash32-026 bash32-033 bash-3.2.tar.gz bash32-006 bash32-013 bash32-020 bash32-027 bash32-034 bash32-007 bash32-014 bash32-021 bash32-028 bash32-035 ~/install/BASH$ tar xf bash-3.2.tar.gz ~/install/BASH$ cd bash-3.2 ~/install/BASH/bash-3.2$ cat ../bash32* | patch -p0 patching file parse.y patching file patchlevel.h [...] Maybe you've got too old a version of the "patch" utility. Here, patch --version gives me: patch 2.5.9 Copyright (C) 1988 Larry Wall Copyright (C) 2003 Free Software Foundation, Inc. [...] > /Users/chet/src/bash/src/parse.y: In function ?decode_prompt_string?: > /Users/chet/src/bash/src/parse.y:4333: error: too few arguments to function > ?expand_prompt_string? > make: *** [y.tab.o] Error 1 > > So the question is has my patch "procedure" broken the source code? [...] Yes, it looks like there has been a problem while applying bash32-037 -- Stéphane
