ERROR: No module named 'geoviewer'

Installation
1

I have installed flair in a Mac High Sierra and Geoviewer following the instructions Official flair site. I have installed flair-3.0. flair-viewer-3.0 and Fluka in three independent folders. Fluka is running OK, however when I run flair the following error messages appear:

Warning: Geometry Viewer not found

e> ERROR: No module named ‘geoviewer’
Fontconfig warning: ignoring UTF-8: not a valid region tag

I hope you can help me with this issue.

Best regards

2

Hi Julia,
have you compiled and installed the geoviewer library?

See the instruction in the section Compile from source in the page mentioned.

Cheers luigi

3

yes, I have compiled and installed Geoviewer from source following the instructions in the section Compile from source.
But maybe I haven’t understood the last instruction when it is said that

“replace PATH_FLAIR with the directory path where Flair was expanded.”

Could you give me some more details about that?

Best,

Julia

4

Hi Julia,
you need to replace the string PATH_FLAIR with the directory where you have expanded the flair tarfile.
For example, in my case, it would be
$ > make install DESTDIR=/Users/luillo/git-repo/flair/flair

Hope this is more clear now.
Cheers luigi

5

Thanks Luigi, I have followed the instructions and I have installed Geoviewer. At the end I have replaced the string PATH_FLAIR with the directory where I have expanded the flair tarfile.

I have the same message when I run flair:

Warning: Geometry Viewer not found

e> ERROR: No module named ‘geoviewer’
Fontconfig warning: ignoring UTF-8: not a valid region tag

When I compile flair with make -j 8, the following warning appears:

ld: warning: text-based stub file /System/Library/Frameworks//CoreFoundation.framework/CoreFoundation.tbd and library file /System/Library/Frameworks//CoreFoundation.framework/CoreFoundation are out of sync. Falling back to library file for linking.
ld: warning: text-based stub file /System/Library/Frameworks//CoreFoundation.framework/CoreFoundation.tbd and library file /System/Library/Frameworks//CoreFoundation.framework/CoreFoundation are out of sync. Falling back to library file for linking.

Maybe you know if it is related to the error.

Best,

Julia

6

Dear Julia,
you don’t need to compile flair but only geoviewer.

The error Geometry Viewer not found means that the command
make install DESTDIR=PATH_FLAIR
was not successful or that there was a problem in the geoviewer compilation.

Could you possibly check that geoviewer.so exists both in the geoviewer directory and in the flair directory?

Finally, the message ld: warning: text-based stub file ... is a warning, so it can be ignored.
I guess that it’s caused by an old version of the Command Line Tools installed on you Mac.
You may try to reinstall:

  1. sudo rm -rf /Library/Developer/CommandLineTools
  2. xcode-select --install

Let me know if this helps you.
Cheers luigi

7

Dear Luigi,
The geoviewer.so exist both in the geoviewr directory and the flair directory. I have the same error again:

w> Warning: Geometry Viewer not found

e> ERROR: No module named ‘geoviewer’
Fontconfig warning: ignoring UTF-8: not a valid region tag

I don´t obtain any errors when I compile Geoviewr with make.
Any other ideas?

Best,

Julia

8

Dear @julia.campa,

Can you change the line 224 of the rules.mk file located in the geoviewer module folder from
# LDFLAGS = -dynamiclib
to
SOFLAGS = -dynamiclib
and recompile again?
After this change, you should enter the folder where the geoviewer was expanded and type:
make clean
make
and afterwards, make install DESTDIR=PATH_FLAIR changing the PATH_FLAIR with the directory name where flair was expanded.

Let me know,
Thanos

9

Thanks Thanos, I have followed your steps but the error is the same.

best,

Julia

10

Hi Julia,
can you provide the output of this command inside the flair directory?
file geoviewer.so
Thanks, luigi

11

Hi Luigi,
the output is:

bash-3.2$ file geoviewer.so
geoviewer.so: Mach-O 64-bit executable x86_64

Thanks

12

Hi Julia,

so the solution is the one described by @manousos.
Please follow carefully the proposed steps. Something’s gone wrong.

Let us know if you manage to fix the problem.

Sorry for the inconvenience (the fix will be available in the next Flair release).
Thanks, luigi