> -----Original Message----- > From: Sam Halliday [mailto:fommil@xxxxxxxxx] > Sent: Wednesday, January 26, 2005 2:43 PM > To: squid-users@xxxxxxxxxxxxxxx > Subject: [squid-users] configure: error: ls -t appears to fail > > > hi there, > > i have always had an issue with compiling squid on GNU/Linux... every time i > run ./configure i get the title of this email as the output of "checking if > build environment is sane". > > my system IS sane. as far as i can tell, this is an issue with older versions > of autoconf generating an insane sanity check which somehow breaks with the > more recent versions of ls. > > may i please request that squid uses a more up to date version of autoconf to > generate the configure script for the next release? (i just tried on today's > RC2 and this still happens). you are currently using 2.13 which is quite a few > years old. > > i would just run autoconf myself (i have 2.57), but recently i've been getting > the error: do not use LIBOBJS directly, use AC_LIBOBJ. and i have no idea how > to fix it. > > no-one is gonna disagree that GNU autotools suck... and unfortunately this is > another one of those cases where they are a real pain in the backside. > > cheers, > Sam When you mention recent versions of ls, what version are you specifically working with? I've compiled squid 2.5STABLE7 on a box with ls version 4.1 (on a Cobalt Qube based on RedHat 6.2), version 4.5.3 (on RedHat 9) and version 5.2.1 (on Fedora Core 3) all without the issue that you mention. Coreutils (http://ftp.gnu.org/pub/gnu/coreutils/) is currently at version 5.2.1, so I imagine that this indicates the current version of ls. This obviously doesn't help your situation in and of itself, but it might lead you to look to another area for the cause of this error message. *shrug* Chris
