Now they would have been set read only if they were on a CD wouldn't they? When i get home (i am not right now) i will have to just chmod -R 775 the whole lot of them, i suspect that is my problem
wait. since the files on the CD were .tar.bz2 files, when i inflated them, the contents would not have been read only, so this would have not made any difference. i know i have read/write/execute permissions for the partition these files are on (which is an ext2 one i made using slackware's normal 'mke2fs' with no special options)...
it does look as though it's something to do with the 'configure' script, but why i wonder are the errors related to permissions? well, when i get home i will check it out as i say.
to keep it all together, here's the url for the other thread i asked this in, in case it's helpful to anybody who finds this thread because they have similar issues:
the 'INSTALL' file for this program says:
The simplest way to compile Bash is:
1. `cd' to the directory containing the source code and type
`./configure' to configure Bash for your system. If you're using
`csh' on an old version of System V, you might need to type `sh
./configure' instead to prevent `csh' from trying to execute
Running `configure' takes some time. While running, it prints
messages telling which features it is checking for.
2. Type `make' to compile Bash and build the `bashbug' bug reporting
3. Optionally, type `make tests' to run the Bash test suite.
4. Type `make install' to install `bash' and `bashbug'. This will
also install the manual pages and Info file.
The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
those values to create a `Makefile' in each directory of the package
(the top directory, the `builtins', `doc', and `support' directories,
each directory under `lib', and several others). It also creates a
`config.h' file containing system-dependent definitions. Finally, it
creates a shell script named `config.status' that you can run in the
future to recreate the current configuration, a file `config.cache'
that saves the results of its tests to speed up reconfiguring, and a
file `config.log' containing compiler output (useful mainly for
debugging `configure'). If at some point `config.cache' contains
results you don't want to keep, you may remove or edit it.
Specifying the System Type
There may be some features `configure' can not figure out
automatically, but need to determine by the type of host Bash will run
on. Usually `configure' can figure that out, but if it prints a
message saying it can not guess the host type, give it the
`--host=TYPE' option. `TYPE' can either be a short name for the system
type, such as `sun4', or a canonical name with three fields:
`CPU-COMPANY-SYSTEM' (e.g., `i386-unknown-freebsd4.2').
See the file `support/config.sub' for the possible values of each field.
i feel a little silly i never saw this before, but i am still a little confused about why it can't guess the system type on its own, it's linux 2.4.20 on an i686 which is hardly an unusual system type one would imagine...