On Jul 17, Dima Pasechnik wrote:
A standard way to "fix" this for projects like fplll would be to add
AM_MAINTAINER_MODE macro to configure.ac, regenerate ./configure
and then run configure with --disable-maintainer-mode

But I'll have to do this for every pkgs that will be installed? that'll take a while. But if this is really a matter of having /home mounted over nsf, this should be something that comes up often I suppose.
R

On Fri, Jul 17, 2020 at 9:15 PM Dima Pasechnik <dimp...@gmail.com> wrote:

Do you build on a network file system?
Do they have a "scratch" partition you can use, which is on a local disk?

What you see has to do with "skew clocks" on the fileserver vs the CPU you use.



On Fri, 17 Jul 2020, 21:00 'Reimundo Heluani' via sage-devel, 
<sage-devel@googlegroups.com> wrote:

Hello, I asked shell access to a larger computer at my institution (192
threads and a couple terabytes of RAM). This is not a computer that I have
root access. I am trying to build sage from git and I hit a configure error on
every package with the message

"newly created file is older than distributed files!"

The snippet that fails is:

# Do 'set' in a subshell so we don't clobber the current shell's
# arguments.  Must try -L first in case configure is actually a
# symlink; some systems play weird games with the mod time of symlinks
# (eg FreeBSD returns the mod time of the symlink's containing
# directory).
if (
    am_has_slept=no
    for am_try in 1 2; do
      echo "timestamp, slept: $am_has_slept" > conftest.file
      set X `ls -Lt "$srcdir/configure" conftest.file 2> /dev/null`
      if test "$*" = "X"; then
         # -L didn't work.
         set X `ls -t "$srcdir/configure" conftest.file`
      fi
      if test "$*" != "X $srcdir/configure conftest.file" \
         && test "$*" != "X conftest.file $srcdir/configure"; then

         # If neither matched, then we have a broken ls.  This can happen
         # if, for instance, CONFIG_SHELL is bash and it inherits a
         # broken ls alias from the environment.  This has actually
         # happened.  Such a system could not be considered "sane".
         as_fn_error $? "ls -t appears to fail.  Make sure there is not a broken
   alias in your environment" "$LINENO" 5
      fi
      if test "$2" = conftest.file || test $am_try -eq 2; then
        break
      fi
      # Just in case.
      sleep 1
      am_has_slept=yes
    done
    test "$2" = conftest.file
    )
then
    # Ok.
    :
else
    as_fn_error $? "newly created file is older than distributed files!
Check your system clock" "$LINENO" 5
fi

But I am not familiar with the build system. I am attaching one of the config
logs that fails and the main configure.log. I'll appreciate any help.

Best,

R.

--
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/20200717200023.GB589209%40vertex.

--
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAAWYfq1TaAzp15DrUjd7cy%3DB1hk1e04grFVpZFCY6DpRH215Vg%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/20200717204336.GA594266%40vertex.

Attachment: signature.asc
Description: PGP signature

Reply via email to