Re: Strange Make Error

[Maren Purves via Tech-talk <tech-talk@aps.anl.gov>]

Agree, this is neither EPICS nor C related.

"date" on both machines should tell you which one is way off (but
won't change the timestamps on files). If you have admin privileges,
set the time on the one that  is off, and then try "touch" on all the
files that appear to have the wrong time to get the timestamp right.
And yes, you may have to work through that  one by one, it's tedious.

Maren (doing more sys-admin than EPICS these days)

On Mon, Jul 21, 2025 at 6:07 AM Johnson, Andrew N. via Tech-talk
<tech-talk@aps.anl.gov> wrote:
>
> I agree that this has nothing to do with the EPICS code.
>
> Another possibility is that the machine that you used to extract or checkout the EPICS code has its clock far in advance of the machine where you’re doing the build. The GNUmake program that we use to build EPICS does need all of your machine clocks to be closely synchronized, you can’t rely on manually setting the clocks if you’re going to use more than one system to extract and do the builds.
>
> - Andrew
>
> --
>
> Complexity comes for free, Simplicity you have to work for.
>
>
>
> On 7/21/25, 11:02 AM, "Tech-talk" <tech-talk-bounces@aps.anl.gov> wrote:
>
> Hej Federico,
> As far as I can see :this has nothing to do with C
>
> The time of your local machine compared to the time where
> /home/xlabsrv11/ is mounted are really out of sync.
> Either the clock of your local machine is wrong.
> Or the server hosting the file system has the wrong clock.
> Or both.
>
> What happens, if you enter
> date
> on your machine ?
>
>
> On 2025-07-21 17:24, Federico Galdenzi via Tech-talk wrote:
> > Dear Simon,
> >
> > Thanks for the reply. I'm not very familiar with C but i'm trying to
> > fill the gaps. However the building fails because the warning gets
> > triggered continously and the building doesnt' go further. It just keeps
> > printing the warning.
> >
> > Il 2025-07-21 16:33 Simon Rose ha scritto:
> >> Hi Federico -
> >>
> >> Make uses the timestamp on files to detect if a file needs to be
> >> updated. It seems that one of your files thinks it was created about 6
> >> years from now.
> >>
> >> I've seen this come up in a few odd ways, possibly due to thinks like
> >> mounted filesystems on hosts that have different time settings, or
> >> improper NTP syncing.
> >>
> >> That said, that shouldn't actually cause the build to fail; that's
> >> just a warning that something is a bit off with the latest
> >> modification time of that file. It can be ignored, although it's
> >> probably worth looking at why your file and systems times do not match
> >> each other.
> >>
> >> Cheers,
> >>
> >> Simon
> >>
> >> On 2025-07-21, 16:17, "Tech-talk on behalf of Federico Galdenzi via
> >> Tech-talk" <tech-talk-bounces@aps.anl.gov <mailto:tech-talk-
> >> bounces@aps.anl.gov> on behalf of tech-talk@aps.anl.gov <mailto:tech-
> >> talk@aps.anl.gov>> wrote:
> >>
> >>
> >> Dear Community,
> >>
> >>
> >> I'm trying to learn EPICS and i started following a pretty simple
> >> example from Maurizio Monti, stream device exercises. I wanted to create
> >> a simple EPICS application that controls VPS. However, after setting up
> >> everything, I get into this error.
> >>
> >>
> >> make[3]: Attenzione: il file
> >> "/home/xlabsrv11/epics/configure/RULES_COMMON" ha un orario di modifica
> >> 209019432 nel futuro
> >> Creating dbd file hvps_example.dbd
> >> perl -CSD /home/xlabsrv11/epics/bin/linux-x86_64/dbdExpand.pl -I. -I..
> >> -I../O.Common -I../../../dbd
> >> -I/home/xlabsrv11/epics/synApps_6_3/support/asyn-R4-44-2/dbd
> >> -I/home/xlabsrv11/epics/synApps_6_3/support/StreamDevice-2-8-24/dbd
> >> -I/home/xlabsrv11/epics/dbd -o hvps_example.dbd base.dbd
> >> ^Cmake[2]: *** [/home/xlabsrv11/epics/configure/RULES_ARCHS:58:
> >> install.linux-x86_64] Interruzione
> >> make[1]: *** [/home/xlabsrv11/epics/configure/RULES_DIRS:85:
> >> src.install] Interruzione
> >> make: *** [/home/xlabsrv11/epics/configure/RULES_DIRS:85:
> >> hvps_exampleApp.install] Interruzione
> >>
> >>
> >> The "make[3]: warning" translates to " the file ../../.. has a different
> >> modification time 209019432 in the future".
> >>
> >>
> >> Can you help me?
> >>
> >>
> >> ps: as a side note, i'd like to know if you can suggest me some
> >> resources for learning epics. I'm kinda lost sometimes.
> >
>