FEAPpv - instalation issue

[Adam]

Hi,

I.m a new FEAPpv user (Windows 10, Cygwin & intel compiler already installed) and I have difficulty with compiling the makefile.in.

Of course, I choose the intel version, after installing it. But I guess still makefile.in files is not prepared correctly :/
Folder localization: D:\rozne\FEAPpv\feappv-5.1.1c

makefile & error logs in attachments

[Prof. S. Govindjee]

I think the problem is that you are not using the makefile correctly.

First just call it makefile.in not makefile.bat.

Second to compile the code, at the command prompt just issue the command

Code: [Select]

make install

[Adam]

Hi,

if makefile has the file extension ".bat" it is possible to run the script (message in the previous attachment). Otherwise for ".in" command "makefile.in install" open script in notepad only.

As I see console is able to run this file, but the input I guess has some mistakes inside.

Maybe you have some poka-yoke install-guidline for windows? :/

[Prof. S. Govindjee]

A makefile is not a script.  Leave it as makefile.in, the build system is expecting that.  If you do not do that, then FEAPpv will never install for you 

I'm assuming here that you are building within cygwin not performing a regular windows build.

See the build videos on youtube for further guidance.

[Adam]

Hi,

I proceed the instruction by this video for cygwin: https://www.youtube.com/watch?v=_ohQ__rqq3Y

Unfortunately, I'm still not sure if makefile.in is prepared correctly:
- my intel C-compiller colalication:  C:\Program Files (x86)\Intel\oneAPI
- makefile.in file in attachement (please take a look)

After command in cygwin "make archive" sth like this occure:

Code: [Select]

adamk@DESKTOP-CHGAMV8 /cygdrive/d/rozne/FEAPpv/feappv-5.1.1c
$ make archive
(cd elements; make archive)
make[1]: Entering directory '/cygdrive/d/rozne/FEAPpv/feappv-5.1.1c/elements'
(cd frame; make archive)
make[2]: Entering directory '/cygdrive/d/rozne/FEAPpv/feappv-5.1.1c/elements/frame'
makefile:1: .../makefile.in: No such file or directory
make[2]: *** No rule to make target '.../makefile.in'.  Stop.
make[2]: Leaving directory '/cygdrive/d/rozne/FEAPpv/feappv-5.1.1c/elements/frame'
make[1]: *** [makefile:4: archive] Error 2
make[1]: Leaving directory '/cygdrive/d/rozne/FEAPpv/feappv-5.1.1c/elements'
make: *** [makefile:13: archive] Error 2


[Prof. R.L. Taylor]

You need to set a real path not "..."

[Adam]

Hi,

after adding "export ...." I've received such answer from cygwin terminal:

Code: [Select]

adamk@DESKTOP-CHGAMV8 /cygdrive/d/rozne/FEAPpv/feappv-5.1.1c
$ make archive
(cd elements; make archive)
make[1]: Entering directory '/cygdrive/d/rozne/FEAPpv/feappv-5.1.1c/elements'
(cd frame; make archive)
make[2]: Entering directory '/cygdrive/d/rozne/FEAPpv/feappv-5.1.1c/elements/frame'
make[3]: Entering directory '/cygdrive/d/rozne/FEAPpv/feappv-5.1.1c/elements/frame'
make[3]: *** No rule to make target 'D:rozneFEAPpvfeappv-5.1.1c/Feappv_i.a'.  Stop.
make[3]: Leaving directory '/cygdrive/d/rozne/FEAPpv/feappv-5.1.1c/elements/frame'
make[2]: *** [makefile:16: archive] Error 1
make[2]: Leaving directory '/cygdrive/d/rozne/FEAPpv/feappv-5.1.1c/elements/frame'
make[1]: *** [makefile:4: archive] Error 2
make[1]: Leaving directory '/cygdrive/d/rozne/FEAPpv/feappv-5.1.1c/elements'
make: *** [makefile:13: archive] Error 2
current makefile.in & makefile in attachment

EDIT: I've found at previous mentioned youtube guidline comment section, that error "no rule to make target" mean that there's sth wrong with compillet etc O.o
EDIT2: I've try with both (gcc fortran & intel compiller version of makefile.in) files and receive the same error on Cygwin

[Prof. S. Govindjee]

Adam,
  (1) I suggest reading a short tutorial on the unix OS that will help with some of your misunderstandings and make cygwin more useful for you.

  (2) (a) Edit makefile.in and comment out the export statement, as it originally was.
       (b) Open the cygwin terminal window.  In the terminal window, at the command prompt, try executing

Code: [Select]

export FEAPPVHOME5_1=/cygdrive/d/rozne/FEAPpv/feappv-5.1.1c this is the instruction in the video near the 22 second mark.  Note that if your cygwin terminal is not a bash shell you may need to use setenv instead of export.  You can check with the command printenv | grep SHELL.

  (3) Now at the command prompt, while in /cygdrive/d/rozne/FEAPpv/feappv-5.1.1c, execute make install at the command prompt

CYGWIN, I believe, uses its own file system and paths, which slightly differ from the Window paths.  I am curious as to if the intel compiler will work when called from inside CYGWIN.  In the past I think I have only used CYGWIN with the gcc compiler.  Your other option for a unix like environment is to use the WSL system that is built into Windows 10.  I use that with Ubuntu; there are other distributions available too from the Windows store (for free).

[Adam]

Hi,

acc. to your sugestion:
- after checking command printenv, I've received the below info (I guess Cygwin is a bash shell?).

Code: [Select]

[...]
SHELL=/bin/bash
[...]
and after checking only "export" command works,
- after changing to makefile.in for gcc and used of different export localization (suggested by you) command "make" is alive!

But with few errors. For full transcript please take a look in attachment, below short clipping:

->

Code: [Select]

make[3]: Entering directory '/cygdrive/d/rozne/FEAPpv/feappv-5.1.1c/elements/material'
Building material.o
rvemat.f:2:25:
    2 |       subroutine rvemat(d,f,detf,ta,hn,hn1,nh, sig,dd,isw)
      |                         1
Warning: Unused dummy argument ‘d’ at (1) [-Wunused-dummy-argument](the same for another arguments like 'dd', 'deft', 'numnp', 'filmnp' ... and for others localization: materials, solid3d, thermal, program)

->

Code: [Select]

make[2]: Entering directory '/cygdrive/d/rozne/FEAPpv/feappv-5.1.1c/program'
Building acheck.o
acosd.f:2:6:
    2 |       function acosd(x)
      |      1
Warning: ‘acosd’ declared at (1) is also the name of an intrinsic.  It can only be called via an explicit interface or if declared EXTERNAL. [-Wintrinsic-shadow]
[...]
psolve.f:53:72:
   53 |             tdiff = tary(1)
      |                                                                        ^
Warning: ‘tary’ may be used uninitialized [-Wmaybe-uninitialized]
psolve.f:43:40:
   43 |       real (kind=4) :: etime, tt,tary(2)
      |                                        ^
note: ‘tary’ declared here
(the same for another functions like 'asind(x)')

->

Code: [Select]

make[2]: Entering directory '/cygdrive/d/rozne/FEAPpv/feappv-5.1.1c/plot'
[...]
Building vecp.o
vem_compp.f:2:34:
    2 |       subroutine vem_compp(k, iplt, nel, iu)
      |                                  1
Warning: Unused dummy argument ‘iplt’ at (1) [-Wunused-dummy-argument](the same for another arguments like 'iu', ...)

-> Fatal error

Code: [Select]

make[2]: Entering directory '/cygdrive/d/rozne/FEAPpv/feappv-5.1.1c/unix'
[...]
Building tplot.o
x11u.c:64:10: fatal error: X11/Xlib.h: No such file or directory
   64 | #include <X11/Xlib.h>
      |          ^~~~~~~~~~~~
compilation terminated.
make[2]: *** [makefile:42: /cygdrive/d/rozne/FEAPpv/feappv-5.1.1c/Feappv_g.a(x11u.o)] Error 1
make[2]: Leaving directory '/cygdrive/d/rozne/FEAPpv/feappv-5.1.1c/unix'
a - clpan.o
[...]
a - tplot.o
--->/cygdrive/d/rozne/FEAPpv/feappv-5.1.1c/unix objects now up-to-date<---
make[1]: *** [makefile:16: archive] Error 1
make[1]: Leaving directory '/cygdrive/d/rozne/FEAPpv/feappv-5.1.1c/unix'
make: *** [makefile:19: archive] Error 2
I guess the last fatal error is the crucial one at this stage.

Additionally, I want to say sorry for my "not-even-basic "knowledge of Cygwin and thank you both for your help.

[Prof. S. Govindjee]

You can ignore the warnings.  The error however is crucial.  You need to load the X11 window system into your version of cygwin.  You will also need to have an xserver running on the windows side.  We normally use Xming.  It is important to load the 75 and 100 dpi fonts when setting up the server and the X11 libraries.  Have a look at the instructions posted for using WSL+Ubuntu on this forum.

[Adam]

I'm happy to say that FEAPpv works and the output file from the solver pass the "test problem"!
Thank you Prof. S. Govindjee!