Mail Archives: djgpp/1998/02/12/04:53:48
On Wed, 11 Feb 1998, Peter Palotas wrote:
> I have a problem with BASH. Very often when I try to run configure scripts
> from within BASH it crashes (SIGSEGV), however it works fine if I run it
> from the DOS command prompt like "bash configur".
There is no significant differences in Bash operation between batch
and interactive modes. Although I mostly run Bash in batch mode, it
does work for me to run configure scripts interactively as well.
So please provide necessary details. The crash traceback is required
whenever you report a crash. Version information about Bash is also
necessary (``latest version'' is not enough, as there are two ported
versions on SimTel: v1.14.7 and v2.x; I use the former). And of
course you need to tell which configure script (from what package) did
you run and how did you run it.
Other related information that could be useful:
- does Bash crash every time you run that script, or only
sometimes?
- are you sure all programs invoked by Bash (like `sed', `grep',
`mv' etc.) are DJGPP ports?
- do you have enough free space on the disk where the TMPDIR
variable points? (This is especially important if it points
to a RAM disk.)
> I'm running DOS 6.22, i.e. no long filenames, I thought maybe that could
> have something to do with it, otherwise I don't know.
I doubt that this would be the reason. I run configure scripts with
Bash routinely on plain DOS, and it never crashed for me (unless there
was a very good reason ;-).
Of course, configure scripts cannot usually run on DOS (or on Windows
95, for that matter) without some editing. That is why I asked which
script(s) did you run. But Bash shouldn't crash even if you didn't
edit the script, it will just fail in several places.
- Raw text -