[Users] Problem installation Einstein Toolkit

Roland Haas rhaas at illinois.edu
Thu Jul 25 10:54:29 CDT 2024


Hello Elena,

> I am Elena Goria and I want to use the Einstein Toolkit.

Weclome to the toolkit!

> I am writing to you because of a problem encountered in installing
> the Einstein Toolkit. 

The errors that you are seeing (incompatible pointers) is something
that showed up with very recent version of gcc (gcc 14 I think).

This is supposed to be fixed in the most recent release of the Einstein
Toolkit ET_2024_05 "Lev Landau".

Which version are you using? If it is an older version you may want to
try the newest release.

Alternatively you (and also if it fails in the current release) you can
add the option

-Wno-incompatible-pointer-types

to you CFLAGS option list variable.

The option list file used depends on the cluster / workstation you are
compiling on. They all exist in the directory
simfactory/mdb/optionlists

If you are compiling on your workstation or an unknown cluster and let
the Einstein Toolkit try to auto-detect things (which may well not
fully succeed on a cluster since it is geared towards typical laptops /
workstations) it uses the file `generic.cfg` or something like
`generic-14.cfg` or `generic-mp-14.cfg` *after* (and only after) the
`simfactory/bin/setup-silent` step.

Based on the path (/Users/<username>) is this a macOS system?

The most robust way to edit this is then to:

* delete the directory `configs` and all its content so that you are
  guaranteed to compile from scratch
* edit the option list (likely
  `simfactory/mdb/optionlists/generic.cfg` or `generic-14.cfg`) and
  find the line that starts with CFLAGS. Add
  -Wno-incompatible-pointer-types at the end of that line (with a space
  in front of it)

compile again using the `build` command.

Some instructions are also provided in 

https://github.com/einsteintoolkit/jupyter-et/blob/master/tutorial-server/notebooks/CactusTutorial.ipynb

in the prerequisites section. Unfortunately that section has not yet
been fully updated for the most recent gcc version.

Yours,
Roland

-- 
My email is as private as my paper mail. I therefore support encrypting
and signing email messages. Get my PGP key from http://pgp.mit.edu .
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.einsteintoolkit.org/pipermail/users/attachments/20240725/71a381db/attachment.sig>


More information about the Users mailing list