eh, and is it usually happens, I now see Brad's response about a missing bc; nevermind, sry for the noise. (but the final point still holds: "bc" should be declared as a build-dep of Chapel)
On Thu, Mar 27, 2014 at 10:20 AM, Fotis Georgatos <[email protected]>wrote: > Hi Bibek, > > I think you may benefit at this point from an EasyBuild "build reciPY": > > https://github.com/hpcugent/easybuild-easyconfigs/tree/master/easybuild/easyconfigs/c/Chapel > > Here is a script I've put together that does the interesting steps for > you, for a v1.8 variant: > (untested: it downloads, patches, builds etc): > > ``` > #!/bin/bash --posix > > # init variables and show default modules environment > TMPDIR=/tmp/HPCBIOS.$$/ > MODULEPATH=$TMPDIR/modules/all:$MODULEPATH > module avail > module --version > > # download easybuild via the bootstrap method > curl -O > https://raw.github.com/hpcugent/easybuild-framework/develop/easybuild/scripts/bootstrap_eb.py > python bootstrap_eb.py $TMPDIR > > # run the show > module load EasyBuild > eb Chapel-1.8.0-goolf-1.4.10.eb -r # here is where the magic happens > ``` > > This is a recursive build that includes the compiler and co, so it takes a > while! > > If that build effort also fails, with the same error about Perl, > you now need to feed it with a user-built version of the later as a > (build-)dep. > One way to go about it, is to replace the following line in the easyconfig: > `toolchain = {'name': 'PRACE', 'version': '20130605-goolf-1.4.10'}` # > Reduce the PRACE easyconfig from the unneeded baggage, like Tcl/Tk, Java & > NetCDF. > > The "correct" future way to do it is, to know all the "builddependencies" > of Chapel > and add that list in the relevant python dictionary (good question comes > to mind: > has anyone here have already done the homework, while providing a > distro-ready package?) > With that info at hand, the Chapel easyconfig can be rationalized a bit. > (ldd only gives some of the run-deps, at post-mortem of the build > process...) > > enjoy, > F. > > > > > On Thu, Mar 27, 2014 at 4:49 AM, Bibek Ghimire <[email protected]>wrote: > >> Hey everyone, >> I have been trying to install chapel in my university(LSU) >> machine ( debian linux) which has multi nodes in it. I keep on getting >> >> perl: warning: Setting locale failed. >> >> perl: warning: Please check that your locale settings: >> >> LANGUAGE = (unset), >> >> LC_ALL = (unset), >> >> LC_CTYPE = "UTF-8", >> >> LANG = "en_US.UTF-8" >> >> are supported and installed on your system. >> >> perl: warning: Falling back to the standard locale ("C"). >> >> perl: warning: Setting locale failed. >> >> perl: warning: Please check that your locale settings: >> >> >> every time and end up getting error when I try to compile simple hello >> world. >> >> Full error below : >> >> >> http://paste.ofcode.org/Q6QthwY3dUfzZCWaSepawY >> >> >> >> >> >> >> ------------------------------------------------------------------------------ >> >> _______________________________________________ >> Chapel-users mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/chapel-users >> >> > > > -- > -- > echo "sysadmin know better bash than english"|sed s/min/mins/ \ > | sed 's/better bash/bash better/' # Yelling in a CERN forum > > -- -- echo "sysadmin know better bash than english"|sed s/min/mins/ \ | sed 's/better bash/bash better/' # Yelling in a CERN forum
------------------------------------------------------------------------------
_______________________________________________ Chapel-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/chapel-users
