Dear Satish,
On 19/06/2017 08:29, Satish Sherikar wrote:
Dear Kenneth,
I think there is bug in shared filesystem like gpfs filesystem.
When I use buiddir "/dev/shm" as suggested by you,It ran successfully.
Great, thanks for confirming!
(please keep the list in CC when replying to messages, so solutions to
problems are known publicly)
regards,
Kenneth
Here is the log.
iitmlogin5:/gpfs1/home/ibm $ export EASYBUILD_BUILDPATH=/dev/shm
iitmlogin5:/gpfs1/home/ibm $ eb GCCcore-4.9.3.eb $ROBOT
== temporary log file in case of crash /tmp/eb-my585V/easybuild-uZaKHx.log
== resolving dependencies ...
== processing EasyBuild easyconfig
/gpfs1/home/ibm/.local/easybuild/software/EasyBuild/3.2.1/lib/python2.6/site-packages/easybuild_easyconfigs-3.2.1-py2.6.egg/easybuild/easyconfigs/g/GCCcore/GCCcore-4.9.3.eb
== building and installing GCCcore/4.9.3. <http://4.9.3.>..
== fetching files...
== creating build dir, resetting environment...
== unpacking...
== patching...
== preparing...
== configuring...
== building...
== testing...
== installing...
== taking care of extensions...
== postprocessing...
== sanity checking...
== cleaning up...
== creating module...
== permissions...
== packaging...
== COMPLETED: Installation ended successfully
== Results of the build can be found in the log file(s)
/gpfs1/home/ibm/.local/easybuild/software/GCCcore/4.9.3/easybuild/easybuild-GCCcore-4.9.3-20170619.115813.log
== Build succeeded for 1 out of 1
== Temporary log file(s) /tmp/eb-my585V/easybuild-uZaKHx.log* have
been removed.
== Temporary directory /tmp/eb-my585V has been removed.
Thank you Very much!!
Regards,
Satish Sherikar
On Fri, Jun 16, 2017 at 1:14 PM, Kenneth Hoste <[email protected]
<mailto:[email protected]>> wrote:
Dear Satish,
On 16/06/2017 06:49, Satish Sherikar wrote:
Dear Kenneth,
We are using "gpfs" file system we don't have any local
filesystem to install the modules.
Kindly let me know why it is giving an error on this filesystem.
To be honest, I'm not 100% sure why using a shared filesystem like
GPFS for the build directory, but it's some kind of a
timing/syncing issue (or a bug in GPFS)...
To be clear: the build directory is where the software is being
compiled by EasyBuild, it's not where the software is being
installed to.
If you have a local disk in the system where you are running
EasyBuild, you should configure EasyBuild to use that for the
build directories,
for example using "eb --buildpath /tmp/$USER" or "export
EASYBUILD_BUILDPATH=/tmp/$USER; eb ...".
If you don't have a local disk, you can use /dev/shm (which can
also significantly speed up the building).
By default, EasyBuild abuses $HOME/.local/easybuild for the build
directories, install directories, etc.
Using your home directory may not be a good configuration on your
system though, so you should reconfigure EasyBuild to use
different locations.
The documentation I linked to explains that in detail, but do let
us know if you have any further questions.
regards,
Kenneth
Regards,
Satish Sherikar
On Thu, Jun 15, 2017 at 9:23 PM, Kenneth Hoste
<[email protected] <mailto:[email protected]>> wrote:
Dear Satish,
On which OS are you seeing this?
From the config.log:
ld.gold: error:
/gpfs1/home/ibm/.local/easybuild/build/GCCcore/4.9.3/dummy-/gcc-4.9.3/obj/./gcc/libgcc_s.so:1:1:
invalid character
That looks like the same problem as was reported in
https://github.com/hpcugent/easybuild-easyconfigs/issues/4191
<https://github.com/hpcugent/easybuild-easyconfigs/issues/4191>,
i.e. having the build directory on a shared filesystem may be
the problem here...
Try configuring EasyBuild to use a local directory as build
directory, see
http://easybuild.readthedocs.io/en/latest/Configuration.html#build-path-buildpath
<http://easybuild.readthedocs.io/en/latest/Configuration.html#build-path-buildpath>.
regards,
Kenneth
On 15/06/2017 14:02, Satish Sherikar wrote:
Hi,
I have getting an error while installing GCCcore-4.9.3.
iitmlogin5:/gpfs1/home/ibm $ eb GCCcore-4.9.3.eb $ROBOT --debug
== temporary log file in case of crash
/tmp/eb-5tpUER/easybuild-y7Xa9p.log
== resolving dependencies ...
== processing EasyBuild easyconfig
/gpfs1/home/ibm/.local/easybuild/software/EasyBuild/3.2.1/lib/python2.6/site-packages/easybuild_easyconfigs-3.2.1-py2.6.egg/easybuild/easyconfigs/g/GCCcore/GCCcore-4.9.3.eb
== building and installing GCCcore/4.9.3. <http://4.9.3.>..
== fetching files...
== creating build dir, resetting environment...
== unpacking...
== patching...
== preparing...
== configuring...
== building...
== FAILED: Installation ended unsuccessfully (build
directory:
/gpfs1/home/ibm/.local/easybuild/build/GCCcore/4.9.3/dummy-):
build failed (first 300 chars): cmd " make -j 32 bootstrap
" exited with exitcode 2 and output:
echo stage3 > stage_final
make[1]: Entering directory
`/gpfs1/home/ibm/.local/easybuild/build/GCCcore/4.9.3/dummy-/gcc-4.9.3/obj'
make[2]: Entering directory
`/gpfs1/home/ibm/.local/easybuild/build/GCCcore/4.9.3/dummy-/gcc-4.9.3/obj'
m
== Results of the build can be found in the log file(s)
/tmp/eb-5tpUER/easybuild-GCCcore-4.9.3-20170615.172520.vXhbr.log
ERROR: Build of
/gpfs1/home/ibm/.local/easybuild/software/EasyBuild/3.2.1/lib/python2.6/site-packages/easybuild_easyconfigs-3.2.1-py2.6.egg/easybuild/easyconfigs/g/GCCcore/GCCcore-4.9.3.eb
failed (err: 'build failed (first 300 chars): cmd " make -j
32 bootstrap " exited with exitcode 2 and output:\necho
stage3 > stage_final\nmake[1]: Entering directory
`/gpfs1/home/ibm/.local/easybuild/build/GCCcore/4.9.3/dummy-/gcc-4.9.3/obj\'\nmake[2]:
Entering directory
`/gpfs1/home/ibm/.local/easybuild/build/GCCcore/4.9.3/dummy-/gcc-4.9.3/obj\'\nm')
Regards,
Satish Sherikar
