Atom topic feed | site map | contact | login | Protection des données personnelles | Powered by FluxBB | réalisation artaban
You are not logged in.
Hello, today I tried to install current unstable code_aster on a linux ppc64le system (ubuntu 20.04, gfortran, python 3.9.5, med 4.1.0 etc).
waf build
finishes successfully. However,
waf install
fails as follows:
...
- install /opt/aster/share/locale/aster/en-US/LC_MESSAGES/aster_messages.mo (from build/std/release/i18n/en-US/aster_messages.mo) [53/1885]
- install /opt/aster/share/locale/aster/ja-JP/LC_MESSAGES/aster_messages.mo (from build/std/release/i18n/ja-JP/aster_messages.mo)
- install /opt/aster/share/locale/aster/ro-RO/LC_MESSAGES/aster_messages.mo (from build/std/release/i18n/ro-RO/aster_messages.mo)
Waf: Leaving directory `/home/may/aster/codeaster/src/build/std/release'
+ build the elements catalog elem.1 using installed aster (from cata_ele.ojb)
stdout:
╔════════════════════════════════════════════════════════════════════════════════════════════════╗
║ <F> <JEVEUX_1> ║
║ ║
║ La limite mémoire demandée de 4294967296 octets est supérieure ║
║ au maximum adressable sur cette plate-forme (-1 octets). ║
║ ║
║ Conseil : ║
║ Diminuez la mémoire totale demandée pour le calcul. ║
║ ║
║ ║
║ Cette erreur est fatale. Le code s'arrête. ║
╚════════════════════════════════════════════════════════════════════════════════════════════════╝
How can I investigate this issue? The configuration log on this system is attached.
Last edited by maychiew (2021-12-17 00:02:23)
Offline
Today I found one problem. The platform name is:
$ uname -p
ppc64le
but the waf file wscript (line 348) contains:
if self.env.DEST_CPU.endswith('64'):
os_name += '64'
self.define('ASTER_HAVE_64_BITS', 1)
because "ppc64le" contains, but does not end with "64", the platform is misconfigured as a 32-bit platform.
Can wscript:348 be changed to, for example:
if self.env.DEST_CPU.find('64'):
Can people in the community make changes to code_aster?
Last edited by maychiew (2021-12-14 20:54:51)
Offline
This has been solved. The problem was the configuration not understanding it is a 64-bit platform, and editing the run_aster and catalo scripts to use a larger memory limit (e.g. 32GB) so the catalog can be built. Then the install completed successfully and aster seems to work.
Offline
Here is a patch (on head of default branch) that:
- detect ppc64le as a 64bits platform,
- add option --disable-proc-status not to control VmSize during execution to be passed at configure step.
Should be integrated soon in development branch.
For a quick fix, you can undefined ASTER_ENABLE_PROC_STATUS in generated build/*/*/asterc_config.h files.
MC
Code_Aster release : last unstable on Ubuntu 16.04 64 bits - GNU Compilers
Please do not forget to tag your first post as *SOLVED* when it is!
Offline