It doesn't help that I'm not a C programmer
I've tried various build scripts:
Here are the errors using the source and build script from slackware-9.1:
First there seems to be problems with the patches:
Quote:
bash-2.05b/y.tab.c
bash-2.05b/y.tab.h
bash-2.05b/parser-built
Hmm...Ignoring potentially dangerous file name ../bash-2.05b/lib/readline/bind.c
Looks like a new-style context diff to me...
The text leading up to this was:
--------------------------
| BASH PATCH REPORT
| =================
|
|Bash-Release: 2.05b
|Patch-ID: bash205b-001
|
|Bug-Reported-by: taviso@sdf.lonestar.org
|Bug-Reference-ID: <200208021107.g72B723d021352@darkstar.example.net>
|Bug-Reference-URL: http://mail.gnu.org/pipermail/bug-ba...st/004980.html
|
|Bug-Description:
|
|Bash goes into an infinite loop and eventually crashes with a SIGSEGV
|when some keys on the numeric keypad are pressed, possibly in combination
|with the shift key.
|
|Patch:
|
|*** ../bash-2.05b/lib/readline/bind.c Thu Jan 24 11:15:52 2002
|--- lib/readline/bind.c Wed Jul 31 09:11:18 2002
--------------------------
patching file lib/readline/bind.c
Using Plan A...
Hunk #1 succeeded at 312.
done
Hmm...Ignoring potentially dangerous file name ../bash-2.05b/lib/readline/readline.c
Looks like a new-style context diff to me...
The text leading up to this was:
--------------------------
| BASH PATCH REPORT
| =================
|
|Bash-Release: 2.05b
|Patch-ID: bash205b-002
|
|Bug-Reported-by: rwhron@earthlink.net
|Bug-Reference-ID: <20020724000454.GA15210@rushmore> (bug-bash)
|Bug-Reference-URL: http://mail.gnu.org/pipermail/bug-ba...ly/004856.html
|
|Bug-Description:
|
|Repeating an edit in vi-mode with `.' does not work.
|
|Patch:
|
|*** ../bash-2.05b/lib/readline/readline.c Wed Mar 13 17:10:46 2002
|--- lib/readline/readline.c Tue Jul 30 17:46:44 2002
--------------------------
patching file lib/readline/readline.c
Using Plan A...
Hunk #1 succeeded at 685.
Hmm... Ignoring the trailing garbage.
done
Hmm...Ignoring potentially dangerous file name ../bash-2.05b/bashline.c
Looks like a new-style context diff to me...
The text leading up to this was:
--------------------------
| BASH PATCH REPORT
| =================
|
|Bash-Release: 2.05b
|Patch-ID: bash205b-003
|
|Bug-Reported-by: jan.q.bruun-andersen@posten.se
|Bug-Reference-ID: <BE156C6450189B4ABAF7381F0AD4724A0165674F@002exmbs002.ad.posten.se>
|Bug-Reference-URL: http://mail.gnu.org/pipermail/bug-ba...ly/004789.html
|
|Bug-Description:
|
|In certain cases, Bash appends a space instead of a slash to a directory
|name relative to the current directory when performing command name
|completion. This affects partial completion of intermediate directory
|names.
|
|Patch:
|
|*** ../bash-2.05b/bashline.c Tue May 7 15:52:42 2002
|--- bashline.c Sat Aug 3 11:40:16 2002
--------------------------
patching file bashline.c
Using Plan A...
Hunk #1 succeeded at 1045.
Hunk #2 succeeded at 1056.
Hunk #3 succeeded at 1065.
done
Hmm...Ignoring potentially dangerous file name ../bash-2.05b/subst.c
Looks like a new-style context diff to me...
The text leading up to this was:
--------------------------
| BASH PATCH REPORT
| =================
|
|Bash-Release: 2.05b
|Patch-ID: bash205b-004
|
|Bug-Reported-by: c.f.a.johnson@rogers.com
|Bug-Reference-ID: <aji8sb$1aa9bi$2@ID-136730.news.dfncis.de>
|Bug-Reference-URL: http://mail.gnu.org/pipermail/bug-ba...st/005074.html
|
|Bug-Description:
|
|A bug in the bash variable expansion code causes leading blanks in a
|variable's value to be ignored when computing its length.
|
|Patch:
|
|*** ../bash-2.05b/subst.c Mon Jun 24 07:59:45 2002
|--- subst.c Sat Aug 17 17:28:46 2002
--------------------------
patching file subst.c
Using Plan A...
Hunk #1 succeeded at 1639.
Hmm... Ignoring the trailing garbage.
done
Hmm...Ignoring potentially dangerous file name ../bash-2.05b/lib/readline/mbutil.c
Looks like a new-style context diff to me...
The text leading up to this was:
--------------------------
| BASH PATCH REPORT
| =================
|
|Bash-Release: 2.05b
|Patch-ID: bash205b-005
|
|Bug-Reported-by: Jim Meyering <jim@meyering.net>
|Bug-Reference-ID: <87bs6v8iib.fsf@pixie.eng.ascend.com>
|Bug-Reference-URL: http://mail.gnu.org/archive/html/bug.../msg00047.html
|
|Bug-Description:
|
|When in a locale with multibyte characters, the readline display updater
|will occasionally cause a segmentation fault when attempting to compute
|the length of the first multibyte character on the line.
|
|Patch:
|
|*** ../bash-2.05b/lib/readline/mbutil.c Tue Jun 4 11:54:29 2002
|--- lib/readline/mbutil.c Mon Aug 5 11:20:39 2002
--------------------------
patching file lib/readline/mbutil.c
Using Plan A...
Hunk #1 succeeded at 206.
Hunk #2 succeeded at 214.
Hunk #3 succeeded at 228.
Hunk #4 succeeded at 282.
done
Hmm...Ignoring potentially dangerous file name ../bash-2.05b/lib/readline/display.c
Looks like a new-style context diff to me...
The text leading up to this was:
--------------------------
| BASH PATCH REPORT
| =================
|
|Bash-Release: 2.05b
|Patch-ID: bash205b-006
|
|Bug-Reported-by: clowenst@ucsd.edu
|Bug-Reference-ID: <156388ec.0212021151.51a48df1@posting.google.com>
|Bug-Reference-URL:
|
|Bug-Description:
|
|When running in a locale with multibyte characters, the readline display
|updater will use carriage returns when drawing the line, overwriting any
|partial output already on the screen and not terminated by a newline.
|
|Patch:
|
|*** ../bash-2.05b/lib/readline/display.c Tue Jun 4 10:54:47 2002
|--- lib/readline/display.c Fri Sep 13 16:22:57 2002
--------------------------
patching file lib/readline/display.c
Using Plan A...
Hunk #1 succeeded at 71.
Hunk #2 succeeded at 1349.
Hunk #3 succeeded at 1511.
Hunk #4 succeeded at 1602.
Hunk #5 succeeded at 2121.
Using Plan A...
Hunk #1 succeeded at 206.
Hunk #2 succeeded at 214.
Hunk #3 succeeded at 228.
Hunk #4 succeeded at 282.
done
Hmm...Ignoring potentially dangerous file name ../bash-2.05b/lib/readline/display.c
Looks like a new-style context diff to me...
The text leading up to this was:
--------------------------
| BASH PATCH REPORT
| =================
|
|Bash-Release: 2.05b
|Patch-ID: bash205b-006
|
|Bug-Reported-by: clowenst@ucsd.edu
|Bug-Reference-ID: <156388ec.0212021151.51a48df1@posting.google.com>
|Bug-Reference-URL:
|
|Bug-Description:
|
|When running in a locale with multibyte characters, the readline display
|updater will use carriage returns when drawing the line, overwriting any
|partial output already on the screen and not terminated by a newline.
|
|Patch:
|
|*** ../bash-2.05b/lib/readline/display.c Tue Jun 4 10:54:47 2002
|--- lib/readline/display.c Fri Sep 13 16:22:57 2002
--------------------------
patching file lib/readline/display.c
Using Plan A...
Hunk #1 succeeded at 71.
Hunk #2 succeeded at 1349.
Hunk #3 succeeded at 1511.
Hunk #4 succeeded at 1602.
Hunk #5 succeeded at 2121.
Hunk #6 succeeded at 2197.
done
Hmm...Ignoring potentially dangerous file name ../bash-2.05b/lib/readline/vi_mode.c
Looks like a new-style context diff to me...
The text leading up to this was:
--------------------------
| BASH PATCH REPORT
| =================
|
|Bash-Release: 2.05b
|Patch-ID: bash205b-007
|
|Bug-Reported-by: dman@dman.ddts.net
|Bug-Reference-ID: <15893.26358.129589.503364@gargle.gargle.HOWL>
|Bug-Reference-URL: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=175127
|
|Bug-Description:
|
|Using the vi editing mode's case-changing commands in a locale with
|multibyte characters will cause garbage characters to be inserted into
|the editing buffer.
|
|Patch:
|
|*** ../bash-2.05b/lib/readline/vi_mode.c Thu May 23 13:27:58 2002
|--- lib/readline/vi_mode.c Tue Feb 4 15:11:07 2003
--------------------------
patching file lib/readline/vi_mode.c
Using Plan A...
Hunk #1 succeeded at 681.
Hunk #2 succeeded at 705.
done
configure: WARNING: you should use --build, --host, --target
checking build system type... x86_64-slackware-linux-gnu
checking host system type... x86_64-slackware-linux-gnu
Beginning configuration for bash-2.05b-release for x86_64-slackware-linux-gnu
|
It goes on to the compile and then gets these errors:
Quote:
ar cr libtilde.a tilde.o
test -n "ranlib" && ranlib libtilde.a
make[1]: Leaving directory `/tmp/bash-2.05b/lib/tilde'
make[1]: Entering directory `/tmp/bash-2.05b/lib/malloc'
x86_64-slackware-linux-gcc -I. -I../.. -I../.. -I../../include -I../../lib -DHAVE_CONFIG_H -DSHELL -O2 -fPIC -DRCHECK -Dbotch=programming_error -c malloc.c
malloc.c: In function ‘internal_free’:
malloc.c:881:1: error: label at end of compound statement
make[1]: *** [malloc.o] Error 1
make[1]: Leaving directory `/tmp/bash-2.05b/lib/malloc'
make: *** [lib/malloc/libmalloc.a] Error 1
make[1]: Entering directory `/tmp/bash-2.05b/lib/malloc'
x86_64-slackware-linux-gcc -I. -I../.. -I../.. -I../../include -I../../lib -DHAVE_CONFIG_H -DSHELL -O2 -fPIC -DRCHECK -Dbotch=programming_error -c malloc.c
malloc.c: In function ‘internal_free’:
malloc.c:881:1: error: label at end of compound statement
make[1]: *** [malloc.o] Error 1
make[1]: Leaving directory `/tmp/bash-2.05b/lib/malloc'
make: *** [lib/malloc/libmalloc.a] Error 1
mv: cannot stat ‘/tmp/package-bash/usr/bin/bash’: No such file or directory
|
BTW - despite the fatal errors, this buildscript then carries on and builds a package without the bash program in it, so installing the package without checking the log, which is what I did, left me without any bash - luckily I had ash and dash installed.