This might be caused by conditional checks, possibly in the autotools arena, which are not correctly identifying the darwin system as capable of shared libraries. Increased generation of shared (dylib) libraries.ĥ) I've noticed that many of the libraries generated are static (.a) rather than shared (.so or. build for logical cpus, then limit the number of concurrent jobs to somewhere between the number of physical and logical cpus. There is probably a different way to deal with this matter i.e. I since have set up my build to use physical cores, thereby again in my case limiting the number of jobs run in astout.export to 4 concurrent jobs which results in a more reasonable multi-tasking environment. The intel i7 processor on my MacBookPro is single cpu, quad core, with hyperthreading technology (two threads per core) therefore providing up to 8 threads (aka logical cores)Ĥ) When running the astout.export tests with the code compiled using the number of logical cores (8 in my case), my machine was all but unusable since the logic in the job queuing allowed 8 jobs to run simultaneously, essentially sucking up most/all of the system resources. I eliminated many of the changes associated with changing the recursive rm command lowercase r to uppercase both darwin and linux accept lowercase r for recursive rm so these changes were not necessary.ġ) Build the HOMARD tool to integrate so those samples referring to HOMARD will successfully run (currently all the files in astout.export which refer to HOMARD fail with ERROR when testing)Ģ) Coordinate effort to include gmsh binary for Mac OS X x86_64 thereby coming one step closer to a single source distributionģ) Decide how best to accommodate the specification of number of cores vs number of threads allowable. I was able to identify what prevented grace from including PNG support and also now have xmgrace included in the grace build There was no notable difference in the output based on the 38 sample files included in the astout.export test suite.ĥ packages modified (aster, astk, grace,, metis-edf, scotch plus files in main distribution root directory)Īstout.export using liste_short (38 files) I have applied the patches to my CentOS 6.3 systems (one on a standalone HP laptop and one as a VirtualBox virtual machine on my MacBook). Reference TdS's wiki article describing his approach to successfully building code-aster for Mac OS X Lion Code-Aster on OS X Wiki Page I wish to thank the developers of code-aster for incorporating several of the patches provided by Thomas DE SOZA in the upgrade from version 11.1 to 11.2. Those of you who became familiar with my original patch will notice this patch is much smaller and, I believe, less invasive. I am hopeful the patches I've developed will be accepted by the code-aster development team for inclusion in future releases, thereby enabling Mac OS X users to use the update capability and all but eliminating the need for specific Mac OS X patches with future releases. Note: the modifications are similar for both versions 10.7 and 11.2. I have developed what I believe to be a reasonable approach to a single source code distribution for build on the primary supported Linux and also on Mac OS X. This is a followup to my recent post Mac OS X Lion patch for ver 11.2 providing more seamless support Mac OS X Lion.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |