Re: I can`t complete ./configure command
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Ivan Maximov on 3/2/2007 3:05 AM: > I have an HP Integrety superdome with HP-UX 11iv2, but i can1t > complete command ./configure (see error in attachment). What I can > do? Do you realize you just slammed the list with a 5 megabyte screenshot, when a copy-and-paste of the text contents from your terminal would have been only a few kilobytes? Please be more considerate in the future, particularly for people who get their mail over dialup. Your screenshot doesn't show any fatal errors, just that gcc is not installed on your HP. Did configure run to completion? If not, what is your real problem? - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF8A/z84KuGfSFAYARAqXrAKCzk81KP5CraB5aZhCpMivBORNC4ACeNaqq xoSPBdNv7f72sppDR/JfA4A= =DkDY -END PGP SIGNATURE- ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
Re: parameter expansion malinterpretation
[EMAIL PROTECTED] wrote: > Bash Version: 3.2 > Patch Level: 9 > Release Status: release > > Description: > When introducing negative values in a parameter or variable > substitution dealing with substrings it does not interpret as a negative > number, I think it interprets like a default value substitution You are correct -- but that is not a bug. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer Live Strong. No day but today. Chet Ramey, ITS, CWRU[EMAIL PROTECTED]http://cnswww.cns.cwru.edu/~chet/ ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
Re: Bash-3.2 Official Patch 10
Tim Waugh wrote:
> There still doesn't seem to be a way to write expressions that work in
> 3.2 and in 3.1. For example, below is an expression that works fine in
> 3.1. How do I re-write it so that it (a) continues to work with
> bash-3.1, and (b) also works with bash-3.2?
>
> { cat "$file" ; echo ; } | while read line; do
> if [[ ! "$line" =~ '^[[:space:]]*(\#.*)?$' ]]; then
> /sbin/ip rule del $line
> fi
>done
>
> In particular, when the whole thing is de-quoted bash-3.1 seems to
> require the parentheses to be escaped, while bash-3.2 seems to require
> that they are *not* escaped.
The easiest thing to do is probably to assign the regular
expression to a variable. You may need to conditionally assign it
based on the value of $BASH_VERSION, but probably not.
This would have worked before and after any patches or changes to
bash-3.2.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
Live Strong. No day but today.
Chet Ramey, ITS, CWRU[EMAIL PROTECTED]http://cnswww.cns.cwru.edu/~chet/
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash
Re: parameter expansion malinterpretation
[EMAIL PROTECTED] wrote:
> [EMAIL PROTECTED] ~ $ hello="hello"; echo ${hello:-1}
Read entry E12 in the bash FAQ.
paul
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash
Bash 3.2: defect in jobs.c
Missing macro wrappers for a few uses of status from struct PROCESS.
Some compilers dislike this.
diff -r -c bash-3.2.orig/jobs.c bash-3.2/jobs.c
*** bash-3.2.orig/jobs.cSat Jul 29 16:40:48 2006
--- bash-3.2/jobs.c Thu Mar 8 09:48:16 2007
***
*** 2225,2231
p = jobs[job]->pipe;
do
{
! if (p->status != EXECUTION_SUCCESS) fail = p->status;
p = p->next;
}
while (p != jobs[job]->pipe);
--- 2225,2231
p = jobs[job]->pipe;
do
{
! if (WSTATUS(p->status) != EXECUTION_SUCCESS) fail =
WSTATUS(p->status);
p = p->next;
}
while (p != jobs[job]->pipe);
***
*** 2234,2240
for (p = jobs[job]->pipe; p->next != jobs[job]->pipe; p = p->next)
;
! return (p->status);
}
/* Return the exit status of job JOB. This is the exit status of the last
--- 2234,2240
for (p = jobs[job]->pipe; p->next != jobs[job]->pipe; p = p->next)
;
! return (WSTATUS(p->status));
}
/* Return the exit status of job JOB. This is the exit status of the last
***
*** 2367,2373
if (r == -1 && errno == ECHILD)
{
child->running = PS_DONE;
! child->status = 0;/* XXX -- can't find true status */
js.c_living = 0; /* no living child processes */
if (job != NO_JOB)
{
--- 2367,2373
if (r == -1 && errno == ECHILD)
{
child->running = PS_DONE;
! WSTATUS(child->status) = 0; /* XXX -- can't find true status */
js.c_living = 0; /* no living child processes */
if (job != NO_JOB)
{
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash
Bash 3.2: defect in lib/readline/rltty.c
Missing macro line continuation in middle of declaration. diff -r -c bash-3.2.orig/lib/readline/rltty.c bash-3.2/lib/readline/rltty.c *** bash-3.2.orig/lib/readline/rltty.c Mon Dec 26 17:21:50 2005 --- bash-3.2/lib/readline/rltty.c Thu Mar 8 10:23:43 2007 *** *** 862,868 } #define RESET_SPECIAL(c) \ ! if (c != -1 && kmap[(unsigned char)c].type == ISFUNC) kmap[(unsigned char)c].function = rl_insert; static void --- 862,868 } #define RESET_SPECIAL(c) \ ! if (c != -1 && kmap[(unsigned char)c].type == ISFUNC) \ kmap[(unsigned char)c].function = rl_insert; static void ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
Bash uses 100% CPU time (when started by "su")
Configuration Information: Machine: i686 OS: linux-gnu Compiler: i686-pc-linux-gnu-gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash' -DSHELL -DHAVE_CONFIG_H -I. -I. -I./include -I./lib -march=athlon-xp -O2 -fomit-frame-pointer -pipe uname output: Linux schlumpfine 2.6.19-gentoo-r5 #3 PREEMPT Sun Feb 11 11:26:54 CET 2007 i686 AMD Athlon(tm) XP 2600+ AuthenticAMD GNU/Linux Machine Type: i686-pc-linux-gnu Bash Version: 3.1 Patch Level: 17 Release Status: release Description: When using bash and then starting a second bash by using "su", the bash started by "su" will use 100% CPU time if it is in reverse-i-search mode and the first bash process is killed with SIGHUP (using "kill" or e. g. by closing the xterm window). This also happens with Bash 3.2_p9 and Readline 5.2_p1. I'm using su from shadow version 4.0.18.1. Repeat-By: 1) log in to a console or open an xterm/konsole/... 2) echo $$ (keep this in mind as PID#1) 3) su $USER 4) echo $$ (keep this in mind as PID#2) 5) Hit Ctrl+R (bash is in reverse-i-search mode now) 6) On a different console type: kill -HUP 7) The bash with PID#2 now runs endlessly with 100% CPU usage 8) kill -9 ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
