Problem solved - it seems as though for some reason I included the
--enable-strict-posix-default option in the configure script I was
using, not realizing the ramifications. Mea culpa.
--
Charles D. (Chuck) Harding Voice: 925-423-8879
Senior Computer Technologist LC Operations Fa
> >> Description:
> >> no matter how I invoke bash, it will not run any of the startup
> >> scripts: /etc/profile, ~/.bash_profile, ~/.bashrc - this is either being
> >> started by /bin/login or in an xterm session
You could always run bash in the debugger and set a breakpoint at
run_star
On Wed, 11 Mar 2009, Pierre Gaston wrote:
On Tue, Mar 10, 2009 at 8:42 PM, root wrote:
Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: linux-gnu - Red Hat Enterprise Linux Client release 5.3 (Tikanga)
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DC
On Tue, Mar 10, 2009 at 8:42 PM, root wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: i686
> OS: linux-gnu - Red Hat Enterprise Linux Client release 5.3 (Tikanga)
> Compiler: gcc
> Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686'
> -DCONF_OSTYPE
Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: linux-gnu - Red Hat Enterprise Linux Client release 5.3 (Tikanga)
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu'
-DCONF_V
