install feap on a VM

[Shuai Wang]

Hello every one,
I try to install feap on a Virtual Machine, but encountered a problem.
The installation is successful with make.  However, each time I run make, the make command always compiles  every single .f file in feap.  Usually, make will only update the changed source file.Could anyone give me a clue what happened?
Platform：windows10 + hyper-V + Ubuntu20 + feap84 + gfortran

correct make
https://ibb.co/DfzkkdN
wrong make
https://ibb.co/P5xJtTV

Best

[Prof. S. Govindjee]

I see the same problem on my Win10+Ubuntu 20.04LTS .
It looks like make is broken in this version of Ubuntu.

I do notice that the make file in $FEAPHOMEX_Y/main does behave in the expected way.
The make files in the other folders are the problem.  It seems that Ubuntu make does not know
how to check dates on object file located in archives.  I will have to look into this more.

[Prof. S. Govindjee]

Figured it out.

The problem is that

Code: [Select]

ar rvinserts files into the archive with the incorrect date (Dec 13 1969)!  To fix the problem, please edit $FEAPHOMEX_Y/makefile.in and change the line near the bottom to

Code: [Select]

AR = ar rvUSo add the U on the tags for the archive command.  This will get the date correct in the archive when using Win10+Ubuntu 20.04LTS.

Now run make to fix all the dates.  Your next run of make should work as expected.

The reason this rarely comes up is due to the fact that the default behavior of binutils is to use the correct date.  It seems that binutils in this version of Ubuntu has been configured with the --enable-deterministic-archives tag, which then messes up the dates in the archives.

[Shuai Wang]

thank you for your reply.
Problem solved!

[JStorm]

Notice for later users reading this thread: The behaviour in binutils of Ubuntu has changed since GCC version 6, i.e. since Ubuntu 18.04. LTS.
Also Ubuntu 16.04. LTS is affected when a newer compiler is installed then the default version GCC 5.