Re: GUB3: Infinite loop in patch stage for linux-x86::linux-headers

[Patrick McCarty]

On Mon, Jul 20, 2009 at 01:41:18PM -0700, Patrick McCarty wrote:
> On Mon, Jul 20, 2009 at 03:09:19PM +0200, Jan Nieuwenhuizen wrote:
> > On vr, 2009-07-17 at 21:50 -0700, Patrick McCarty wrote:
> > 
> > > I have no idea what's going on, but the build.log is attached.
> > 
> > Can you try executing the command that triggers this by hand,
> > possibly with some -x debugging to see what's going on, ie
> > do something like
> > 
> > 
> >     cd /home/pnorcks/git/gub/target/linux-x86/src/linux-headers-2.4.34
> >     yes yes | make ARCH=i386 oldconfig CONFIG_SHELL='/bin/bash -x'
> > 
> > I do not see this problem, but someone on #denemo (don't remember) has.
> > Do you have /dev/mtd*?
> 
> No, I don't have any items that start with "mtd" in /dev.
> 
> However, I believe I've come across a bug in Bash 4.0-024.  From the
> shell tracing I've done, this simple command sequence demonstrates the
> problem:
> 
>   bash-4.0$ cat test.sh
>   #!/bin/sh
>   echo Hello
> 
>   bash-4.0$ . test.sh
>   Hello
>   bash-4.0$ sh
>   sh-4.0$ . test.sh
>   sh: .: test.sh: file not found
> 
> 
> This is why I'm getting the error message near the top of my log:
> 
>   scripts/Configure: line 551: .: .config-is-not.12306: file not found

As a followup, this is a situation where Bash 4.0 is more
POSIX-compliant than Bash 3.2.

See the bug report I posted, and the followup:

  http://bugs.archlinux.org/task/15606

The attached patch fixes the problem.

Thanks,
Patrick

0001-Fix-a-compatibility-issue-with-Bash-4.0.patch
Description: Text document