Learning Forum

[soloviev]

Hello,

 

I am having an issue compiling a UDF on a Linux HPC. The UDF worked on Windows. I already tried solutions from /forum/forums/topic/getting-an-error-while-interpreting-udf-in-hpc/

Unfortunately they did not work.

 

The error I am receiving is not in my own UDF file, but rather 'udf_names.o' which it is linking to when compiling in fluent automatically apparently. 

 

The exact errors follow:

# building library in lnamd64/3ddp_node
make[1]: Entering directory `/storage/FW_lens/libudf/lnamd64/3ddp_node'
# Generating udf_names.c because of makefile cylinder_plume_inccoriolis_viscosity_test.c
make[2]: Entering directory `/storage/FW_lens/libudf/lnamd64/3ddp_node'
make libudf.so "CFLAGS=-D_lnamd64 -D_GNU_SOURCE -fpic -shared -ansi -Wall -O -DPTR_RESTRICT=   " "LDFLAGS=-shared -lm"
make[3]: Entering directory `/storage/FW_lens/libudf/lnamd64/3ddp_node'
make[3]: *** No rule to make target `cylinder_plume_inccoriolis_viscocity_test.c', needed by `udf_names.o'.
make[3]: Target `libudf.so' not remade because of errors.

 

Thank you,

Alex

[Rob]

The interpreter errors are never overly helpful.  Can you try and compile on a dummy case on LINUX to see if that's more diagnostic.  I assume you've used dos2unix to strip out all the weird whitespace characters that Windows likes to add to text files? 

[soloviev]

I tried compiling the same file directly on Linux, but it immediately had errors as the Linux compiler didn't understand the fluent macros, or even the 'include "udf.h"'

 

I did use dos2unix before compiling. I also have tested that the Linux compiler works with regular code, and it does. 

 

Thanks,

Alex

[Rob]

Sounds like white space characters: can you open in a text editor and see what happens if you delete the carriage return & then hit enter from the first few lines?  

[soloviev]

Thanks for the suggestion. I believe I did what you asked. I deleted anything before the "include "udf.h" line and then hit enter for a few lines to move the text down. (I also tried with returning the text to the first line after doing so.)

When compiling directly from the Linux command line this is the error I received.

 

Thanks,

Alex

[soloviev]

Hello,

Is there any update to this issue?

 

Thanks,

Alex

[soloviev]

I noticed when compiling on the HPC from the windows client that fluent creates both the lnamd64 folder and the win64 folder within the libudf library, is this what should be happening?

 

Thanks,
Alex

[soloviev]

It seems that I cannot do this via the Fluent to HPC connection on a windows client. I finally resolved this but had to launch Fluent directly via the Linux machine.