Hi,
many thanks for that hint, this may indeed be the issue. I will request access to the local disk and try it again. Best, Florian Btw: @John: I was running make again but there were no files in the future. On Monday, March 18, 2019 at 10:12:09 PM UTC, Dima Pasechnik wrote: > > On Mon, Mar 18, 2019 at 10:05 PM John H Palmieri <jhpalm...@gmail.com > <javascript:>> wrote: > > > > What are the modification dates and times for the files in the directory > > > > > /apps/srv01/pmt/pmtfh/sage/sage-8.6/local/var/tmp/sage/build/yasm-1.3.0.p0 > > > > Maybe you should run 'make' again, which will regenerate this directory, > and then check the times on the files. Are any of them in the future? > > there could also be funny things happening if /apps/srv01/pmt/pmtfh/ > resides on > an NFS or other network filesystem rather than on a local disk. > Please do all the builds on a local disk... > > > > > > > > > On Monday, March 18, 2019 at 2:38:43 PM UTC-7, Dima Pasechnik wrote: > >> > >> You may also ask your sysadmins to install yasm (it's an assembler for > x86_64) > >> (cf e.g. > https://centos.pkgs.org/7/epel-x86_64/yasm-1.2.0-4.el7.x86_64.rpm.html) > >> > >> On Mon, Mar 18, 2019 at 9:18 PM Dima Pasechnik <dim...@gmail.com> > wrote: > >> > > >> > On Mon, Mar 18, 2019 at 9:10 PM 'Florian Hanisch' via sage-support > >> > <sage-s...@googlegroups.com> wrote: > >> > > > >> > > Thanks, my system clock matches the local time quite accurately > (including the year), I just checked it again. I can / could not make any > sense of this comment in the log that you quoted. > >> > > >> > This is a quite standard test in configure files generated by GNU > autotools. > >> > > >> > I don't find much relevant on this on the net, except perhaps > >> > > https://serverfault.com/questions/136186/what-steps-can-you-take-to-ensure-sane-build-environments-when-compiling-softwar > > >> > > >> > Do you by any chance have "ls" aliased to something ? > >> > > >> > > >> > > > >> > > > >> > > On Monday, March 18, 2019 at 8:56:31 PM UTC, Dima Pasechnik wrote: > >> > >> > >> > >> In the log you see > >> > >> > >> > >> checking whether build environment is sane... configure: error: > newly > >> > >> created file is older than distributed files! > >> > >> Check your system clock > >> > >> > >> > >> So it seems that your system clock is off by a considerable > interval > >> > >> (probably, years!) > >> > >> This might be a problem... > >> > >> > >> > >> Does the output of "date" in the terminal match the wall clock in > any way? > >> > >> > >> > >> > >> > >> On Mon, Mar 18, 2019 at 8:37 PM 'Florian Hanisch' via sage-support > >> > >> <sage-s...@googlegroups.com> wrote: > >> > >> > > >> > >> > Dear all, > >> > >> > > >> > >> > this might be a question for the developers groups. But before > joining the dev-group just to be able to post one question, I decided to > ask here first. > >> > >> > > >> > >> > I am trying to compile sage 8.6 on Centos 7 (intel core i5, 8GB > Ram) but the process stops with the following message > >> > >> > > >> > >> > > Error building Sage. > >> > >> > > > >> > >> > > The following package(s) may have failed to build (not > necessarily > >> > >> > > during this run of 'make all-start'): > >> > >> > > > >> > >> > > * package: yasm-1.3.0.p0 > >> > >> > > log file: > /apps/srv01/pmt/pmtfh/sage/sage-8.6/logs/pkgs/yasm-1.3.0.p0.log > >> > >> > > build directory: > /apps/srv01/pmt/pmtfh/sage/sage-8.6/local/var/tmp/sage/build/yasm-1.3.0.p0 > >> > >> > > >> > >> > I attached the log-file mentioned above to my post. I know that > the package perl-ExtUtils-MakeMaker is not installed on my computer > >> > >> > (unfortunately, I am not root on the computer I am using). Is > this a possible reason for the problem ? Or do I have to look for a > "deeper" problem ? > >> > >> > > >> > >> > Thanks, > >> > >> > > >> > >> > Florian > >> > >> > > >> > >> > P.S. If this question should be posted at sage-devel, plaese let > me know, I will subscribe and post then. > >> > >> > > >> > >> > -- > >> > >> > You received this message because you are subscribed to the > Google Groups "sage-support" group. > >> > >> > To unsubscribe from this group and stop receiving emails from > it, send an email to sage-support...@googlegroups.com. > >> > >> > To post to this group, send email to sage-s...@googlegroups.com. > > >> > >> > Visit this group at https://groups.google.com/group/sage-support. > > >> > >> > For more options, visit https://groups.google.com/d/optout. > >> > > > >> > > -- > >> > > You received this message because you are subscribed to the Google > Groups "sage-support" group. > >> > > To unsubscribe from this group and stop receiving emails from it, > send an email to sage-support...@googlegroups.com. > >> > > To post to this group, send email to sage-s...@googlegroups.com. > >> > > Visit this group at https://groups.google.com/group/sage-support. > >> > > For more options, visit https://groups.google.com/d/optout. > > > > -- > > You received this message because you are subscribed to the Google > Groups "sage-support" group. > > To unsubscribe from this group and stop receiving emails from it, send > an email to sage-support...@googlegroups.com <javascript:>. > > To post to this group, send email to sage-s...@googlegroups.com > <javascript:>. > > Visit this group at https://groups.google.com/group/sage-support. > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at https://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
