Can you give me the full /proc/cpuinf for one core on each of the two?
This doesn't make sense and doesn't match my v4 info.
And what OS are you running on them? incl kernel version.
On 08/25/2017 12:46 AM, Andreas Hilboll wrote:
> Hi Kenneth,
>
> thanks for your answer!
>
>> By default,
Hi Kenneth,
thanks for your answer!
> By default, EasyBuild uses -xHost when building with the Intel compilers
> to optimize for the processor architecture of the system you are
> building on.
Yes, that's what I thought. However, I'm a bit confused, because both
CPUs are from the Xeon E-5
Hi Andreas,
On 24/08/2017 20:13, Andreas Hilboll wrote:
Hi Easybuilders,
when I build the Python-3.6.1-intel-2017a.eb easyconfig on the compute
nodes of our cluster instead of the login node, I can only start the
generated python executable on the compute nodes:
[hilboll@login1 ~]$
Hi Easybuilders,
when I build the Python-3.6.1-intel-2017a.eb easyconfig on the compute
nodes of our cluster instead of the login node, I can only start the
generated python executable on the compute nodes:
[hilboll@login1 ~]$ module load Python
[hilboll@login1 ~]$ python
Please
Hello,Thank you for contacting me.Regarding the reason for using GCCcore-4.9.3, I was verifying the introduction of a single application.Now that I needed GCCcore-4.9.3 for introducing PETSc-3.7.3-foss-2016a-Python-2.7.11, I came up with this problem.It seems necessary for GCC core -4.9.3 build
Hi,
We are trying to deploy qt5 in various foss toolchains and are experiencing
issues with the xkb library.
The users report errors like (X11 20160819 in foss 2016b):
xkbcommon: ERROR: failed to add default include path
Dear Yoshihito,
It seems like either this version of GCC or the version of binutils that
is being used to build it (binutils 2.25) is too old for your recent
operating system (or the binutils it includes...).
Is there a reason why you specifically need that fairly old version of GCC?
Hi all,
I found this thread from about two years ago:
www.mail-archive.com/easybuild@lists.ugent.be/msg01795.html
Have things changed since? Would newer glibc still present a pain from
easybuild point of view?
New glibc goodies that got me to think in this direction are thread cache and
Hi,
in the end I (as I work with Maxime) found a solution that seems to work
but needs some more testing:
* instead of setting PYTHONPATH, eb-generated modules set EBPYTHONPATH
* then in the default site-packages directory (or in a location pointed to
by a single-entry PYTHONPATH) we have a file
9 matches
Mail list logo