http://www.catnook.com/patches/rsync-popt-1.6.4.patch
has a patch which upgrades the popt included with rsync to the latest version,
1.6.4. The configure script had to be regenerated (with autoconf 2.53) because
popt.c wants HAVE_FLOAT_H. As an aside, I have heard people complain about
this version of autoconf generating scripts that break when run under bash (as
/bin/sh).
Comments?
--
Jos Backus _/ _/_/_/ Santa Clara, CA
_/ _/ _/
_/ _/_/_/
_/ _/ _/ _/
jos@catnook.com _/_/ _/_/_/ require 'std/disclaimer'
I'm wondering if we shouldn't just remove popt from the rsync source and just rely on the user to install the popt package on their system prior to compiling rsync. Configure already uses the installed popt in preference to the included popt, so it wouldn't be hard to change this to not have a popt fallback. ..wayne..
On Thu, 11 Jul 2002, Jos Backus wrote:> http://www.catnook.com/patches/rsync-popt-1.6.4.patchI went ahead and tested this and then checked it in (since we might as well include the newest popt if we're going to include popt with rsync).> The configure script had to be regenerated (with autoconf 2.53) > because popt.c wants HAVE_FLOAT_H. As an aside, I have heard people > complain about this version of autoconf generating scripts that break > when run under bash (as /bin/sh).If this is a concern, I could easily check in a configure/config.h.in that was generated with autoconf 2.52d. Let me know if there are problems (I didn't have any on my Mandrake Linux 8.2 system). ..wayne..