Hugh Sasse <[EMAIL PROTECTED]> writes:
> As I've been re-examining "The Practice of Programming" (Kernighan and Pike)
> I'd like to ask: is there a reason why you wouldn't replace memcpy
> with memmove, so if these ever overlap it still works?
A newly allocated block of memory cannot overlap wi
On Tue, 9 Oct 2007, Ian Campbell wrote:
> Fix:
>
> The fix is really to pre-seed config.cache so that it knows that the uclibc
> version of getcwd() does the right thing but the fix for the problem in
> lib/sh/getcwd.c is the patch below from my colleague Christian Limpach.
>
> Index: bash-3.2/l
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler:
/bind/obj/repos/dist-buildroot.hg/build_x86_64/staging_dir/usr/bin/x86_64-linux-uclibc-gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MA
