On Mon, Jul 31, 2006 at 03:11:11PM -0700, Dan Nicholson wrote: > Greg pointed out to me that this has been reported upstream. Here's > the link in case his mail doesn't get through. > > http://lists.gnu.org/archive/html/bug-bash/2006-05/msg00018.html > Ooh goody, we can blame the bug somebody raised against glibc on bash, instead of blaming it on our build system. Nah, I wouldn't be so crass, it's our build system which exposes the problem. But thanks for the reference, I will add it to the glibc bug once we agree/test something for the book
> Looks like this could be the simple fix, but I'm not on a system to test. > > $ sed -i '[EMAIL PROTECTED] \(/dev/fd/.\)@-e \1@' configure > As it stands, not acceptable - we can't assume sed supports -i until we boot or chroot (unlike LFS). That's a minor reservation. I'm building on ppc64 at the moment to see if the bash_cv_dev_fd=standard fix does indeed fix the problem with c++-types.out (don't hold your breath, I'll be in bed before both sets of glibc tests have finished, even with the hours I keep ;) I'll look at this sed tomorrow. If both approaches work, I don't know if it is better to add another override to config.cache, or to fix the too-specific test in configure ? Ken -- das eine Mal als Tragödie, das andere Mal als Farce _______________________________________________ Clfs-dev mailing list [email protected] http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-dev
