I should note, I do not build a ton of software by hand, so I
struggle, and try to learn as best as I can. If I am not clear, let
me know, if I need to read or research more, let me know.

On May 28, 2009, at 11:50 PM, Timo Sirainen wrote:

On May 29, 2009, at 2:39 AM, Scott Haneda wrote:

...

checking whether build environment is sane... configure: error: ls - t appears to fail. Make sure there is not a broken alias in your environment

Well, that's the first I've heard of this. Have you tried compiling
any other program that has a configure script built by autoconf?
Seems like all of them would be broken and maybe a better list would
be some autoconf-related mailing list.

Primarily, I have used MacPorts often, so that is where 90% of the
built apps are. In the majority of those cases, it is just calling ./ configure and doing some record keeping.

On this machine, I have built outside of Macports, mrtg, which needed
iirc, some GD stuff. In my efforts to get ASSP working, ~10 perl
modules, not using CPAN, but using ./configure.

• This was a total wild effort here, but I commented out the lines
  that did the date check and the ls -t check and got much further, but
  ended up bailing out on a could not find DC config file. This was my
  error, I did not download the DC sources to this machine.

After doing the right thing and downloading the DC sources... dovecot-1.2.rc4 $./configure checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... configure: error: ls -t
appears to fail. Make sure there is not a broken alias in your environment configure: error: newly created file is older than distributed files! Check your system clock

...

configure: error: newly created file is older than distributed files! Check your system clock

Here is the config log http://dl.getdropbox.com/u/340087/Drops/05.28.09/config-4d3972ab-233922.log

Some tests: $date Thu May 28 23:37:13 PDT 2009

Do you have any NFS or other remote filesystems enabled?

No, just a lowly MacBook on wifi at the moment. I have several other
servers in production I am going to give this a quick go on just to be
sure it is not this particular machine.

Scott * If you contact me off list replace talklists@ with scott@ *

On May 29, 2009, at 12:06 AM, Timo Sirainen wrote:

On May 29, 2009, at 3:01 AM, Scott Haneda wrote:

...

No, just a lowly MacBook on wifi at the moment. I have several
other servers in production I am going to give this a quick go on
just to be sure it is not this particular machine.

I'm pretty sure the problem is your specific machine, given that
I've successfully compiled Dovecot many times in my own MacBook.
Although I could look into what exactly causes this problem in a few
days.

Very nice to know that you work on a MacBook, as I move closer and
closer to getting all my users migrated to DC on Mac OS X. Thank you
for the offer to look at it.

I am guessing configure scripts are auto gen'd? That being the case,
any issues I am having need to be addressed by the developers of
'autoconf' ?

I stepped through the configure script a line at a time to see if I
could pin it down. I have in my bashrc export CLICOLOR=1 export CLICOLOR_FORCE=1

Commenting out the first fixes it. This seems poorly documented, as
the man page for ls does not tell me much about how this will
interfere with the output values for ls at all.

Any suggestions on how to keep my colors and still build, as well as
why this only just bit me now? I have built far too many things for
this to crop up only now, and also have had that color setting on all
my machines since beginnings of 10.5 and maybe 10.4 at some point.

Do you have any idea on where I take this issue to correctly address
is for a proper fix either in the way I define colors, or in how
configure scripts are made?

Thank you for your help, I am off to build this out and run some tests.

Scott * If you contact me off list replace talklists@ with scott@ *