[FLASH-USERS] Error When Running LaserSlab On FLASH 4.6.1

[Jared Guzman]

Klaus, Aaron,

I am able to successfully run make in the object directory, as well as
execute flash. It turns out my Makefile had *tabs* where those compiler
definitions were taking place when they should've been spaces...

Thank you both for your help in this issue, it is greatly appreciated.

Have a good weekend!

Jared

On Fri, Jan 8, 2021 at 4:08 PM Jared Guzman <jag21791 at vt.edu> wrote:

> Klaus,
>
> Thank you for the response, I will try to set it up in a Docker and see
> how it goes. Ill try the make command with the proper flags as well, to see
> if i can get something running this week.
>
> Best,
>
> Jared
>
> On Fri, Jan 8, 2021 at 2:52 PM Klaus Weide <klaus at flash.uchicago.edu>
> wrote:
>
>> On Fri, 8 Jan 2021, Jared Guzman wrote:
>>
>> > So running that line within my object directory creates the command,
>> > however, new commands are now sought by the system, such as the one
>> > attached. If i run the line you sent, replacing 'Burn_interface.F90'
>> with
>> > the missing command, then a new error pops up, repeating the same text
>> just
>> > missing a different one each time (i.e. create Burn_interface, but
>> > ut_sysMemData.mod is missing, create ut_sysMemData.mod
>> > but gr_pmFlashHookData.o is missing, creating that but
>> IncompNS_interface.o
>> > is missing, etc.)
>> >
>> > There seem to be numerous commands missing, is there a way I can find
>> out
>> > all the files that havent been built by Make?
>>
>> Jared,
>>
>> You are using the word "command" in a strange way that makes it a bit
>> difficult to understand what you mean. Perhaps you mean "file".
>>
>> What you have described confirms, or at least is consistent with, the
>> assumption that your compiler works, and that it is only the build
>> process
>> using make that does not behave properly.
>>
>> If you have access to another machine or environment where the build
>> process works properly, you could compare that environment to yours and
>> hopefully narrow down what causes the difference.
>>
>> If you don't have access to another machine or environment, perhaps you
>> can build within a Docker container, as described in the User's Guide.
>>
>>
>> Here is another thing you can try. This is not a proper solution, but may
>> help work around your problem (or not).  Instead of just
>>
>>  make
>>
>> use a command like
>>
>>  make FFLAGS='-c -g -r8 -i4 -real_size 64' CFLAGS='-c -I
>> /opt/apps/intel15_3/openmpi3_0/phdf5/1.8.16/include -DH5_USE_16_API'
>>
>> You may have to modify those flags and maybe add some others.
>>
>> Klaus
>>
> --
> *Jared Guzman*
> *B.S. Physics 2019*
> *M.S. Aerospace Engineering 2022*
> *Virginia Tech*
> *540-419-6027 | jag21791 at vt.edu <jag21791 at vt.edu>*
>


-- 
*Jared Guzman*
*B.S. Physics 2019*
*M.S. Aerospace Engineering 2022*
*Virginia Tech*
*540-419-6027 | jag21791 at vt.edu <jag21791 at vt.edu>*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://flash.rochester.edu/pipermail/flash-users/attachments/20210108/236efac7/attachment.htm>