Trouble compiling _bubble.c

[Claire Bergin]

Hi all,

I am very new to basilisk and coding in general and I was trying to compile bubble.c from the basilisk site. When trying to compile the final _bubble.c file I am getting an error saying

 fatal error: gl/framebuffer.h: No such file or directory
 #include <gl/framebuffer.h>

I attach a screen shot showing what I have done and also that framebuffer.h is present in gl. Could you please advise me how to fix this issue? Any help would be really appreciated!

Thanks in advance,

Claire

[felixh...@hispeed.ch]

Hi Claire

did you set the environment variable $BASILISK and the path as described in the installation instructions? with this set, it should work. I use this command for compiling MPI-runs:

qcc -D_MPI=1 -source prog.c
mpicc -Wall -O2 -std=c99 _prog.c -o prog -I$BASILISK -L$BASILISK/gl -lglutils -lfb_osmesa -lOSMesa -lGLU -lm

or in one step:

CC99='mpicc -std=c99' qcc -Wall -O2 -D_MPI=1 example.c -o example -L$BASILISK/gl -lglutils -lfb_osmesa -lGLU -lOSMesa -lm

cheers, Felix

[Claire Bergin]

Hi,

I'm still having trouble with bubble.c. When I go to run it on the supercomputer I get the error

"error while loading shared libraries: libOSMesa.so.8: cannot open shared object file: No such file or directory"

in the log file associated with the run. I thought everything compiled correctly and have tried recompiling a few times would anyone be able to advise how to get rid of this issue? libOSMesa.so.8 does exist in my directories.

Many thanks in advance,

Claire

[Stephane Popinet]

Hi Claire,

You need to configure the libraries correctly on the supercomputer (e.g.
using 'module load', LD_LIBRARY_PATH etc..). This depends on how your
supercomputer is setup and has nothing to do with Basilisk. You should
ask the system administrators of your supercomputer.

cheers,

Stephane

> --
> You received this message because you are subscribed to the Google
> Groups "basilisk-fr" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to basilisk-fr...@googlegroups.com
> <mailto:basilisk-fr...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/basilisk-fr/c6dfd75a-b2af-4446-8f6c-0e8ca92aab5fn%40googlegroups.com
> <https://groups.google.com/d/msgid/basilisk-fr/c6dfd75a-b2af-4446-8f6c-0e8ca92aab5fn%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Stephane Zaleski]

Hi

  I just checked, libOSMesa is provided by the installation of OSMesa on your machine, not by Basilisk, indeed the administrators of your supercomputer should help you ensure it is properly located. 

  Best

Stéphane Zaleski

[Nelson Joubert]

Hi,

apart from using the default OSMesa installed on the supercomputer, you can install it from source on the supercomputer following this: http://www.basilisk.fr/sandbox/joubert/INSTALL_mesa_supercomputer

Cheers,

Nelson

[Stephane Zaleski]

Dear Claire

   A general tip is to follow netiquette as perhaps explained somewhere on the basilisk website. Thus you should never ask a question on a mailing list without researching it on google first. In this case, it is particularly egregious, because google leads me directly to a page of the basilisk website. Try it. You should find:

### Generating MP4 movies

Note that when running on Irene the [ffmpeg](https://www.ffmpeg.org/)
MP4 encoder is not available and the logfile will contain the warning:

~~~bash
open_image(): cannot find 'ppm2mp4' or 'ffmpeg'/'avconv'
  falling back to raw PPM outputs
~~~

The MP4 files defined above will be renamed `movie.mp4.ppm` and
`l2.mp4.ppm`. As the extension indicates, these (large) files are now
raw (uncompressed) PPM images. To convert them to compressed MP4, you
will need to copy them to a machine where ffmpeg (and Basilisk) are
installed (i.e. your local machine) and do:

~~~bash
ppm2mp4 movie.mp4 < movie.mp4.ppm
ppm2mp4 l2.mp4 < l2.mp4.ppm
~~~

Hope it helps

Best

Stéphane Zaleski