configure: error: newly created file is older than distributed files!

2,314 views
Skip to first unread message

chris lindensmith

unread,
Mar 10, 2016, 3:52:02 AM3/10/16
to Phusion Passenger Discussions
I'm installing 5.0.26 on a FreeBSD system.  I'm installing for apache, so I run passenger-install-apache2-module. It goes through compiling a bunch of files and then it gets to checking the kit and I get the following error (including a few lines before and after):

checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... configure: error: newly created file is older than distributed files!
Check your system clock
rake aborted!
Command failed with status (1): [cd buildout/libuv/ && sh /usr/local/www/d_...]

Tasks: TOP => apache2 => buildout/support-binaries/PassengerAgent => buildout/libuv/.libs/libuv.a => buildout/libuv/Makefile
(See full trace by running task with --trace)

--------------------------------------------

It looks like something went wrong

I've gone through the full directory structure and haven't found any files that have dates in the future. There don't seem to be any issues with system time-- it matches the hardware time.  Any suggestions on what's causing this and/or how to prevent it?

Daniel Knoppel

unread,
Mar 10, 2016, 6:26:04 AM3/10/16
to Phusion Passenger Discussions
I wouldn't immediately suspect anything other than what the message says, the system clock. Is it actually synced to real time?

Your output suggest the error is coming from the libuv configure script: /src/cxx_supportlib/vendor-copy/libuv/configure. I think it checks dates against itself, so touch-ing that file might make it work regardless of your clock sync.

- Daniel

chris lindensmith

unread,
Mar 10, 2016, 10:14:04 AM3/10/16
to Phusion Passenger Discussions


On Thursday, March 10, 2016 at 3:26:04 AM UTC-8, Daniel Knoppel wrote:
I wouldn't immediately suspect anything other than what the message says, the system clock. Is it actually synced to real time?

Your output suggest the error is coming from the libuv configure script: /src/cxx_supportlib/vendor-copy/libuv/configure. I think it checks dates against itself, so touch-ing that file might make it work regardless of your clock sync.

I just tried that and got the same error.  Also tried after touching the other files in that directory that get updated during the build (Makefile.in, aclocal.m4), same error.


Daniel Knoppel

unread,
Mar 10, 2016, 10:50:56 AM3/10/16
to Phusion Passenger Discussions
Hmmm.. well we did upgrade our libuv dependency from 1.5.0 to 1.8.0, for the 5.0.26 release and I see now that the (autogenerated) configure file is still from 1.5.0..

I don't know if it is related, but we'll need to have a closer look at that.

- Daniel

chris lindensmith

unread,
Mar 11, 2016, 12:07:29 AM3/11/16
to Phusion Passenger Discussions
I tried going as far back ad 5.0.18 and got the same error.

Then I went back to 4.0.60 and it installed ok, now I'm trying to get it to launch spree properly again-- it's giving me a directory instead of launching.

(all this because my hosting switched abruptly from apache 2.2 to 2.4)

Daniel Knoppel

unread,
Mar 11, 2016, 6:12:48 AM3/11/16
to Phusion Passenger Discussions
What provider are you on? Perhaps they changed more than just Apache..

I just tried a Passenger 5.0.26 install on a fresh FreeBSD 10.2 + Apache 2.4 using a Digitalocean droplet, and everything went alright there (installed Ruby/rvm with their tutorial and then Passenger as a gem before doing passenger-install-apache2-module).

- Daniel
Reply all
Reply to author
Forward
0 new messages