Re: [easybuild] Building foss-2019a fails in binutils-2.31.1.eb (Skylake node)

[Pablo Escobar Lopez]

On Tue, Feb 26, 2019 at 11:24 AM Kenneth Hoste 
wrote:

>
> One easy thing we could do is make the binutils easyblock check whether
> both 'gcc' and 'g++' are present, and emit a clear warning if they're
> missing?
> That would help significantly, since pinpointing the underlying problem
> is clearly not trivial.
>

+1




>
> Not sure we should make that a hard failure though, as there may be
> situation where not having gcc/g++ is actually fine (e.g. when 'cc' and
> 'c++' compilers are available, and can be used to compile binutils).
>
> One other option could be to detect that the build failed because g++ is
> not there (by recognizing the pattern in the configure output or in
> config.log).
>
> Same applies for GCC(core), where you also need a system C++ compiler
> with sufficiently recent versions...
>
>
> regards,
>
> Kenneth
>
> >
> >
> > /Ole
> >
> >> From: easybuild-requ...@lists.ugent.be
> >>  on behalf of Ole Holm Nielsen
> >> 
> >> Sent: Friday, February 22, 2019 09:11
> >> To: easybuild@lists.ugent.be
> >> Subject: Re: [easybuild] Building foss-2019a fails in
> >> binutils-2.31.1.eb (Skylake node)
> >>
> >> Hi Olivier,
> >>
> >> On 2/20/19 10:18 PM, Olivier Mattelaer wrote:
> >>> I actually face the same issue.
> >>>
> >>> The actual error message is this one:
> >>>
> >>> configure: error: in
> >>>
> `/usr/local/Software/build/lm3-w091/binutils/2.31.1/dummy-/binutils-2.31.1/gold':
>
> >>>
> >>> configure: error: C++ preprocessor "/lib/cpp" fails sanity check
> >>> See `config.log' for more details
> >>> yes
> >>> checking whether compiling a cross-assembler... no
> >>> checking for size_t... checking locale.h usability... make[1]: ***
> >>> [configure-gold] Error 1
> >>> make[1]: *** Waiting for unfinished jobs
> >>>
> >>>
> >>> I guess that doing: "yum install gcc-c++" would solve the issue.
> >>> But I have not tested yet. But does it make sense to do that?
> >>
> >> Your suggestion fixed the problem with binutils: yum install gcc-c++
> >> Now it build correctly, and the foss-2019a build process is continuing.
> >>
> >> What's the root cause of this issue?  I'm guessing that the EB file
> >>
> .../EasyBuild/3.8.1/lib/python2.7/site-packages/easybuild_easyconfigs-3.8.1-py2.7.egg/easybuild/easyconfigs/b/binutils/binutils-2.31.1.eb
>
> >>
> >>
> >> must include gcc-c++ as an osdependencies package.
> >>
> >> If this guess is correct, I could open an issue.
>


-- 
Pablo Escobar López
Linux/HPC systems engineer
sciCORE, University of Basel
SIB Swiss Institute of Bioinformatics

Re: [easybuild] Building foss-2019a fails in binutils-2.31.1.eb (Skylake node)

[Ole Holm Nielsen]

On 2/26/19 11:24 AM, Kenneth Hoste wrote:

On 22/02/2019 14:40, Ole Holm Nielsen wrote:

On 2/22/19 1:24 PM, Lars Viklund wrote:
A system C and C++ compiler is documented as a required dependency of 
EasyBuild

if you are to install toolchains with it:

https://easybuild.readthedocs.io/en/latest/Installation.html#required-dependencies 



As such, I would argue that it's not worth declaring it up-front in 
osdependencies
in all software that needs a system compiler, particularly as the 
package

will be named differently on different distros.


Thanks for pointing this out!  I agree with you.

It's all too easy to miss the general EB prerequisites/dependencies 
when installing a new node.  I've added the CentOS 7 specifics to my 
EB Wiki page:
https://wiki.fysik.dtu.dk/niflheim/EasyBuild_modules#easybuild-prerequisites 




One easy thing we could do is make the binutils easyblock check whether 
both 'gcc' and 'g++' are present, and emit a clear warning if they're 
missing?
That would help significantly, since pinpointing the underlying problem 
is clearly not trivial.


Not sure we should make that a hard failure though, as there may be 
situation where not having gcc/g++ is actually fine (e.g. when 'cc' and 
'c++' compilers are available, and can be used to compile binutils).


One other option could be to detect that the build failed because g++ is 
not there (by recognizing the pattern in the configure output or in 
config.log).


Same applies for GCC(core), where you also need a system C++ compiler 
with sufficiently recent versions...


I'm definitely voting for such a check!!  This would have saved me a lot 
of time when binutils refused to build (due to my own error, as it 
turned out).  I don't know the best solution, I'll leave that to the EB 
experts.


Thanks,
Ole

Re: [easybuild] Building foss-2019a fails in binutils-2.31.1.eb (Skylake node)

[Kenneth Hoste]

On 22/02/2019 14:40, Ole Holm Nielsen wrote:

On 2/22/19 1:24 PM, Lars Viklund wrote:
A system C and C++ compiler is documented as a required dependency of 
EasyBuild

if you are to install toolchains with it:

   
https://easybuild.readthedocs.io/en/latest/Installation.html#required-dependencies 



As such, I would argue that it's not worth declaring it up-front in 
osdependencies

in all software that needs a system compiler, particularly as the package
will be named differently on different distros.


Thanks for pointing this out!  I agree with you.

It's all too easy to miss the general EB prerequisites/dependencies when 
installing a new node.  I've added the CentOS 7 specifics to my EB Wiki 
page:
https://wiki.fysik.dtu.dk/niflheim/EasyBuild_modules#easybuild-prerequisites 



One easy thing we could do is make the binutils easyblock check whether 
both 'gcc' and 'g++' are present, and emit a clear warning if they're 
missing?
That would help significantly, since pinpointing the underlying problem 
is clearly not trivial.


Not sure we should make that a hard failure though, as there may be 
situation where not having gcc/g++ is actually fine (e.g. when 'cc' and 
'c++' compilers are available, and can be used to compile binutils).


One other option could be to detect that the build failed because g++ is 
not there (by recognizing the pattern in the configure output or in 
config.log).


Same applies for GCC(core), where you also need a system C++ compiler 
with sufficiently recent versions...



regards,

Kenneth




/Ole

From: easybuild-requ...@lists.ugent.be 
 on behalf of Ole Holm Nielsen 


Sent: Friday, February 22, 2019 09:11
To: easybuild@lists.ugent.be
Subject: Re: [easybuild] Building foss-2019a fails in 
binutils-2.31.1.eb (Skylake node)


Hi Olivier,

On 2/20/19 10:18 PM, Olivier Mattelaer wrote:

I actually face the same issue.

The actual error message is this one:

configure: error: in
`/usr/local/Software/build/lm3-w091/binutils/2.31.1/dummy-/binutils-2.31.1/gold': 


configure: error: C++ preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details
yes
checking whether compiling a cross-assembler... no
checking for size_t... checking locale.h usability... make[1]: ***
[configure-gold] Error 1
make[1]: *** Waiting for unfinished jobs


I guess that doing: "yum install gcc-c++" would solve the issue.
But I have not tested yet. But does it make sense to do that?


Your suggestion fixed the problem with binutils: yum install gcc-c++
Now it build correctly, and the foss-2019a build process is continuing.

What's the root cause of this issue?  I'm guessing that the EB file
.../EasyBuild/3.8.1/lib/python2.7/site-packages/easybuild_easyconfigs-3.8.1-py2.7.egg/easybuild/easyconfigs/b/binutils/binutils-2.31.1.eb 



must include gcc-c++ as an osdependencies package.

If this guess is correct, I could open an issue.

Re: [easybuild] Building foss-2019a fails in binutils-2.31.1.eb (Skylake node)

[Mikael Öhman]

And, apparently I hadn't refreshed this window for 2 days so I just replied
to an outdated message! Sorry for the noise
/ Mikael

On Fri, Feb 22, 2019 at 4:32 PM Mikael Öhman  wrote:

> Hi Olivier,
>
> The server I installed from indeed had gcc-c++ installed, so it's
> consistent with the error you see. I didn't get any of those lines at all
> in my build log (since I didn't get the error).
> To be honest, I'm a bit unsure about what system packages should come into
> play when bootstrapping toolchains, so I'll avoid guessing any more than
> this.
>
> On Wed, Feb 20, 2019 at 10:18 PM Olivier Mattelaer <
> olivier.mattel...@uclouvain.be> wrote:
>
>> Hi Ole, Mikael,
>>
>> I actually face the same issue.
>>
>> The actual error message is this one:
>>
>> configure: error: in
>> `/usr/local/Software/build/lm3-w091/binutils/2.31.1/dummy-/binutils-2.31.1/gold':
>> configure: error: C++ preprocessor "/lib/cpp" fails sanity check
>> See `config.log' for more details
>> yes
>> checking whether compiling a cross-assembler... no
>> checking for size_t... checking locale.h usability... make[1]: ***
>> [configure-gold] Error 1
>> make[1]: *** Waiting for unfinished jobs
>>
>>
>> I guess that doing: "yum install gcc-c++" would solve the issue.
>> But I have not tested yet. But does it make sense to do that?
>>
>> Olivier
>>
>>
>>
>>
>>
>> On 20 Feb 2019, at 21:27, Mikael Öhman  wrote:
>>
>> Hi Ole,
>>
>> That still isn't the error; there should be the actual line, doing
>> whatever compilation or linking, that failed. They just tend to be
>> somewhere in middle of the huge output from the make command (even worse
>> with parallel builds).
>> You can put the entire log in some pastebin and someone is  (probably)
>> willing to take a look.
>>
>> I've built the entire 2019a toolchains on skylake server (with AVX512),
>> without any modifications to any configs or blocks (on a virtual machine
>> though, but all CPU features were exposed to the VM)
>>
>> Best regards, Mikael
>>
>>
>> On Wed, Feb 20, 2019 at 8:58 PM Ole Holm Nielsen <
>> ole.h.niel...@fysik.dtu.dk> wrote:
>>
>>> Hi Åke,
>>>
>>> The make actually fails as shown below.  There are hundreds of configure
>>> and checking lines above the lines I display, and the first make command
>>> fails as shown in the output.
>>>
>>> Can you suggest anything else to check?  Are there issues with AVX512 on
>>> Skylake, and if so, how to work around it?
>>>
>>> FYI, the foss-2018a and foss-2018b toolchains have been built without
>>> problems on the Skylake node.
>>>
>>> Thanks,
>>> Ole
>>>
>>>
>>> On 20-02-2019 18:01, Åke Sandgren wrote:
>>> > That's not the real problem.
>>> > You have to look through that log and figure out what it really is.
>>> > I.e., where does the make actually fail.
>>> >
>>> > On 2/20/19 4:10 PM, Ole Holm Nielsen wrote:
>>> >> On 2/20/19 2:45 PM, Åke Sandgren wrote:
>>> >>> What is the actual error? Look in
>>> >>> /tmp/eb-dyNH9x/easybuild-binutils-2.31.1-20190220.140138.qdBpn.log
>>> >>
>>> >> It's:
>>> >>
>>> >> $ tail
>>> /tmp/eb-dyNH9x/easybuild-binutils-2.31.1-20190220.140138.qdBpn.log
>>> >> config.status: executing default commands
>>> >> make[1]: Leaving directory
>>> >> `/home/modules/build/binutils/2.31.1/dummy-/binutils-2.31.1'
>>> >> make: *** [all] Error 2
>>> >>   (at easybuild/tools/run.py:501 in parse_cmd_output)
>>> >> == 2019-02-20 14:02:45,435 easyblock.py:2870 WARNING build failed
>>> (first
>>> >> 300 chars): cmd " env LIBS='-Wl,-rpath=/usr/lib -Wl,-rpath=/usr/lib64'
>>> >> make -j 80  CFLAGS="-g -O2 -fPIC" " exited with exit code 2 and
>>> output:
>>> >> make[1]: Entering directory
>>> >> `/home/modules/build/binutils/2.31.1/dummy-/binutils-2.31.1'
>>> >> make[1]: Nothing to be done for `all-target'.
>>> >> Configuring in ./libiberty
>>> >> Config
>>> >> == 2019-02-20 14:02:45,435 easyblock.py:288 INFO Closing log for
>>> >> application name binutils version 2.31.1
>>> >
>>> >
>>>
>>
>>

Re: [easybuild] Building foss-2019a fails in binutils-2.31.1.eb (Skylake node)

[Mikael Öhman]

Hi Olivier,

The server I installed from indeed had gcc-c++ installed, so it's
consistent with the error you see. I didn't get any of those lines at all
in my build log (since I didn't get the error).
To be honest, I'm a bit unsure about what system packages should come into
play when bootstrapping toolchains, so I'll avoid guessing any more than
this.

On Wed, Feb 20, 2019 at 10:18 PM Olivier Mattelaer <
olivier.mattel...@uclouvain.be> wrote:

> Hi Ole, Mikael,
>
> I actually face the same issue.
>
> The actual error message is this one:
>
> configure: error: in
> `/usr/local/Software/build/lm3-w091/binutils/2.31.1/dummy-/binutils-2.31.1/gold':
> configure: error: C++ preprocessor "/lib/cpp" fails sanity check
> See `config.log' for more details
> yes
> checking whether compiling a cross-assembler... no
> checking for size_t... checking locale.h usability... make[1]: ***
> [configure-gold] Error 1
> make[1]: *** Waiting for unfinished jobs
>
>
> I guess that doing: "yum install gcc-c++" would solve the issue.
> But I have not tested yet. But does it make sense to do that?
>
> Olivier
>
>
>
>
>
> On 20 Feb 2019, at 21:27, Mikael Öhman  wrote:
>
> Hi Ole,
>
> That still isn't the error; there should be the actual line, doing
> whatever compilation or linking, that failed. They just tend to be
> somewhere in middle of the huge output from the make command (even worse
> with parallel builds).
> You can put the entire log in some pastebin and someone is  (probably)
> willing to take a look.
>
> I've built the entire 2019a toolchains on skylake server (with AVX512),
> without any modifications to any configs or blocks (on a virtual machine
> though, but all CPU features were exposed to the VM)
>
> Best regards, Mikael
>
>
> On Wed, Feb 20, 2019 at 8:58 PM Ole Holm Nielsen <
> ole.h.niel...@fysik.dtu.dk> wrote:
>
>> Hi Åke,
>>
>> The make actually fails as shown below.  There are hundreds of configure
>> and checking lines above the lines I display, and the first make command
>> fails as shown in the output.
>>
>> Can you suggest anything else to check?  Are there issues with AVX512 on
>> Skylake, and if so, how to work around it?
>>
>> FYI, the foss-2018a and foss-2018b toolchains have been built without
>> problems on the Skylake node.
>>
>> Thanks,
>> Ole
>>
>>
>> On 20-02-2019 18:01, Åke Sandgren wrote:
>> > That's not the real problem.
>> > You have to look through that log and figure out what it really is.
>> > I.e., where does the make actually fail.
>> >
>> > On 2/20/19 4:10 PM, Ole Holm Nielsen wrote:
>> >> On 2/20/19 2:45 PM, Åke Sandgren wrote:
>> >>> What is the actual error? Look in
>> >>> /tmp/eb-dyNH9x/easybuild-binutils-2.31.1-20190220.140138.qdBpn.log
>> >>
>> >> It's:
>> >>
>> >> $ tail
>> /tmp/eb-dyNH9x/easybuild-binutils-2.31.1-20190220.140138.qdBpn.log
>> >> config.status: executing default commands
>> >> make[1]: Leaving directory
>> >> `/home/modules/build/binutils/2.31.1/dummy-/binutils-2.31.1'
>> >> make: *** [all] Error 2
>> >>   (at easybuild/tools/run.py:501 in parse_cmd_output)
>> >> == 2019-02-20 14:02:45,435 easyblock.py:2870 WARNING build failed
>> (first
>> >> 300 chars): cmd " env LIBS='-Wl,-rpath=/usr/lib -Wl,-rpath=/usr/lib64'
>> >> make -j 80  CFLAGS="-g -O2 -fPIC" " exited with exit code 2 and output:
>> >> make[1]: Entering directory
>> >> `/home/modules/build/binutils/2.31.1/dummy-/binutils-2.31.1'
>> >> make[1]: Nothing to be done for `all-target'.
>> >> Configuring in ./libiberty
>> >> Config
>> >> == 2019-02-20 14:02:45,435 easyblock.py:288 INFO Closing log for
>> >> application name binutils version 2.31.1
>> >
>> >
>>
>
>

Re: [easybuild] Building foss-2019a fails in binutils-2.31.1.eb (Skylake node)

[Ole Holm Nielsen]

On 2/22/19 1:24 PM, Lars Viklund wrote:

A system C and C++ compiler is documented as a required dependency of EasyBuild
if you are to install toolchains with it:

   
https://easybuild.readthedocs.io/en/latest/Installation.html#required-dependencies

As such, I would argue that it's not worth declaring it up-front in 
osdependencies
in all software that needs a system compiler, particularly as the package
will be named differently on different distros.


Thanks for pointing this out!  I agree with you.

It's all too easy to miss the general EB prerequisites/dependencies when 
installing a new node.  I've added the CentOS 7 specifics to my EB Wiki 
page:

https://wiki.fysik.dtu.dk/niflheim/EasyBuild_modules#easybuild-prerequisites

/Ole


From: easybuild-requ...@lists.ugent.be  on behalf 
of Ole Holm Nielsen 
Sent: Friday, February 22, 2019 09:11
To: easybuild@lists.ugent.be
Subject: Re: [easybuild] Building foss-2019a fails in binutils-2.31.1.eb 
(Skylake node)

Hi Olivier,

On 2/20/19 10:18 PM, Olivier Mattelaer wrote:

I actually face the same issue.

The actual error message is this one:

configure: error: in
`/usr/local/Software/build/lm3-w091/binutils/2.31.1/dummy-/binutils-2.31.1/gold':
configure: error: C++ preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details
yes
checking whether compiling a cross-assembler... no
checking for size_t... checking locale.h usability... make[1]: ***
[configure-gold] Error 1
make[1]: *** Waiting for unfinished jobs


I guess that doing: "yum install gcc-c++" would solve the issue.
But I have not tested yet. But does it make sense to do that?


Your suggestion fixed the problem with binutils: yum install gcc-c++
Now it build correctly, and the foss-2019a build process is continuing.

What's the root cause of this issue?  I'm guessing that the EB file
.../EasyBuild/3.8.1/lib/python2.7/site-packages/easybuild_easyconfigs-3.8.1-py2.7.egg/easybuild/easyconfigs/b/binutils/binutils-2.31.1.eb

must include gcc-c++ as an osdependencies package.

If this guess is correct, I could open an issue.

Re: [easybuild] Building foss-2019a fails in binutils-2.31.1.eb (Skylake node)

[Lars Viklund]

A system C and C++ compiler is documented as a required dependency of EasyBuild
if you are to install toolchains with it:

  
https://easybuild.readthedocs.io/en/latest/Installation.html#required-dependencies

As such, I would argue that it's not worth declaring it up-front in 
osdependencies
in all software that needs a system compiler, particularly as the package
will be named differently on different distros.

// Lars

From: easybuild-requ...@lists.ugent.be  on 
behalf of Ole Holm Nielsen 
Sent: Friday, February 22, 2019 09:11
To: easybuild@lists.ugent.be
Subject: Re: [easybuild] Building foss-2019a fails in binutils-2.31.1.eb 
(Skylake node)

Hi Olivier,

On 2/20/19 10:18 PM, Olivier Mattelaer wrote:
> I actually face the same issue.
>
> The actual error message is this one:
>
> configure: error: in
> `/usr/local/Software/build/lm3-w091/binutils/2.31.1/dummy-/binutils-2.31.1/gold':
> configure: error: C++ preprocessor "/lib/cpp" fails sanity check
> See `config.log' for more details
> yes
> checking whether compiling a cross-assembler... no
> checking for size_t... checking locale.h usability... make[1]: ***
> [configure-gold] Error 1
> make[1]: *** Waiting for unfinished jobs
>
>
> I guess that doing: "yum install gcc-c++" would solve the issue.
> But I have not tested yet. But does it make sense to do that?

Your suggestion fixed the problem with binutils: yum install gcc-c++
Now it build correctly, and the foss-2019a build process is continuing.

What's the root cause of this issue?  I'm guessing that the EB file
.../EasyBuild/3.8.1/lib/python2.7/site-packages/easybuild_easyconfigs-3.8.1-py2.7.egg/easybuild/easyconfigs/b/binutils/binutils-2.31.1.eb

must include gcc-c++ as an osdependencies package.

If this guess is correct, I could open an issue.

Thanks,
Ole

Re: [easybuild] Building foss-2019a fails in binutils-2.31.1.eb (Skylake node)

[Ole Holm Nielsen]

Hi Olivier,

On 2/20/19 10:18 PM, Olivier Mattelaer wrote:

I actually face the same issue.

The actual error message is this one:

configure: error: in 
`/usr/local/Software/build/lm3-w091/binutils/2.31.1/dummy-/binutils-2.31.1/gold':

configure: error: C++ preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details
yes
checking whether compiling a cross-assembler... no
checking for size_t... checking locale.h usability... make[1]: *** 
[configure-gold] Error 1

make[1]: *** Waiting for unfinished jobs


I guess that doing: "yum install gcc-c++" would solve the issue.
But I have not tested yet. But does it make sense to do that?


Your suggestion fixed the problem with binutils: yum install gcc-c++
Now it build correctly, and the foss-2019a build process is continuing.

What's the root cause of this issue?  I'm guessing that the EB file
.../EasyBuild/3.8.1/lib/python2.7/site-packages/easybuild_easyconfigs-3.8.1-py2.7.egg/easybuild/easyconfigs/b/binutils/binutils-2.31.1.eb

must include gcc-c++ as an osdependencies package.

If this guess is correct, I could open an issue.

Thanks,
Ole

Re: [easybuild] Building foss-2019a fails in binutils-2.31.1.eb (Skylake node)

[Ole Holm Nielsen]

Hi Olivier,

Looking further for errors in the logfile I see the same as you point out:

== 2019-02-20 14:02:32,930 build_log.py:251 INFO building...
== 2019-02-20 14:02:32,930 easyblock.py:2616 INFO Starting build step
== 2019-02-20 14:02:32,931 easyblock.py:2622 INFO Running method 
build_step part of step build
== 2019-02-20 14:02:32,931 run.py:192 INFO running cmd:  env 
LIBS='-Wl,-rpath=/usr/lib -Wl,-rpath=/usr/lib64'  make -j 80  CFLAGS="-g 
-O2 -fPIC"
== 2019-02-20 14:02:45,434 build_log.py:162 ERROR EasyBuild crashed with 
an error (at ?:124 in __init__): cmd " env LIBS='-Wl,-rpath=/usr/lib 
-Wl,-rpath=/usr/lib64'  make -j 80  CFLAGS="-g -O2 -fPIC" " exited with 
exit code 2 and output:
make[1]: Entering directory 
`/home/modules/build/binutils/2.31.1/dummy-/binutils-2.31.1'

make[1]: Nothing to be done for `all-target'.

...

checking for working alloca.h... checking elf-hints.h usability... 
checking locale.h usability... configure: error: in 
`/home/modules/build/binutils/2.31.1/dummy-/binutils-2.31.1/gold':

configure: error: C++ preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details

...

In the binutils config.log file there are more details:

configure:5044: gcc -o conftest -g -O2 -fPICconftest.c 
-Wl,-rpath=/usr/lib -Wl,-rpath=/usr/lib64 >&5

/tmp/eb-dyNH9x/cclfs0Uf.o: In function `main':
/home/modules/build/binutils/2.31.1/dummy-/binutils-2.31.1/gold/conftest.c:40: 
undefined reference to `dlsym'

collect2: error: ld returned 1 exit status
configure:5044: $? = 1
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME "gold"
| #define PACKAGE_TARNAME "gold"
| #define PACKAGE_VERSION "0.1"
| #define PACKAGE_STRING "gold 0.1"

Also, the CentOS 7 built-in GCC is used, I don't know if that's intended:
gcc version 4.8.5 20150623 (Red Hat 4.8.5-36) (GCC)


Can anyone shed light on this issue?

Thanks,
Ole

On 2/20/19 10:18 PM, Olivier Mattelaer wrote:

Hi Ole, Mikael,

I actually face the same issue.

The actual error message is this one:

configure: error: in 
`/usr/local/Software/build/lm3-w091/binutils/2.31.1/dummy-/binutils-2.31.1/gold':

configure: error: C++ preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details
yes
checking whether compiling a cross-assembler... no
checking for size_t... checking locale.h usability... make[1]: *** 
[configure-gold] Error 1

make[1]: *** Waiting for unfinished jobs


I guess that doing: "yum install gcc-c++" would solve the issue.
But I have not tested yet. But does it make sense to do that?

Olivier





On 20 Feb 2019, at 21:27, Mikael Öhman > wrote:


Hi Ole,

That still isn't the error; there should be the actual line, doing 
whatever compilation or linking, that failed. They just tend to be 
somewhere in middle of the huge output from the make command (even 
worse with parallel builds).
You can put the entire log in some pastebin and someone is  (probably) 
willing to take a look.


I've built the entire 2019a toolchains on skylake server (with 
AVX512), without any modifications to any configs or blocks (on a 
virtual machine though, but all CPU features were exposed to the VM)


Best regards, Mikael


On Wed, Feb 20, 2019 at 8:58 PM Ole Holm Nielsen 
mailto:ole.h.niel...@fysik.dtu.dk>> wrote:


Hi Åke,

The make actually fails as shown below.  There are hundreds of
configure
and checking lines above the lines I display, and the first make
command
fails as shown in the output.

Can you suggest anything else to check?  Are there issues with
AVX512 on
Skylake, and if so, how to work around it?

FYI, the foss-2018a and foss-2018b toolchains have been built without
problems on the Skylake node.

Thanks,
Ole


On 20-02-2019 18:01, Åke Sandgren wrote:
> That's not the real problem.
> You have to look through that log and figure out what it really is.
> I.e., where does the make actually fail.
>
> On 2/20/19 4:10 PM, Ole Holm Nielsen wrote:
>> On 2/20/19 2:45 PM, Åke Sandgren wrote:
>>> What is the actual error? Look in
>>> /tmp/eb-dyNH9x/easybuild-binutils-2.31.1-20190220.140138.qdBpn.log
>>
>> It's:
>>
>> $ tail
/tmp/eb-dyNH9x/easybuild-binutils-2.31.1-20190220.140138.qdBpn.log
>> config.status: executing default commands
>> make[1]: Leaving directory
>> `/home/modules/build/binutils/2.31.1/dummy-/binutils-2.31.1'
>> make: *** [all] Error 2
>>   (at easybuild/tools/run.py:501 in parse_cmd_output)
>> == 2019-02-20 14:02:45,435 easyblock.py:2870 WARNING build
failed (first
>> 300 chars): cmd " env LIBS='-Wl,-rpath=/usr/lib
-Wl,-rpath=/usr/lib64'
>> make -j 80  CFLAGS="-g -O2 -fPIC" " exited with exit code 2 and
output:
>> make[1]: Entering directory
>> `/home/modules/build/binutils/2.31.1/dummy-/binutils-2.31.1'
>> make[1]: Nothing to be done for `all-target'.
>> Configuring in ./libiberty
>> 

Re: [easybuild] Building foss-2019a fails in binutils-2.31.1.eb (Skylake node)

[Olivier Mattelaer]

Hi Ole, Mikael,

I actually face the same issue.

The actual error message is this one:

configure: error: in 
`/usr/local/Software/build/lm3-w091/binutils/2.31.1/dummy-/binutils-2.31.1/gold':
configure: error: C++ preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details
yes
checking whether compiling a cross-assembler... no
checking for size_t... checking locale.h usability... make[1]: *** 
[configure-gold] Error 1
make[1]: *** Waiting for unfinished jobs


I guess that doing: "yum install gcc-c++" would solve the issue.
But I have not tested yet. But does it make sense to do that?

Olivier





On 20 Feb 2019, at 21:27, Mikael Öhman 
mailto:micket...@gmail.com>> wrote:

Hi Ole,

That still isn't the error; there should be the actual line, doing whatever 
compilation or linking, that failed. They just tend to be somewhere in middle 
of the huge output from the make command (even worse with parallel builds).
You can put the entire log in some pastebin and someone is  (probably) willing 
to take a look.

I've built the entire 2019a toolchains on skylake server (with AVX512), without 
any modifications to any configs or blocks (on a virtual machine though, but 
all CPU features were exposed to the VM)

Best regards, Mikael


On Wed, Feb 20, 2019 at 8:58 PM Ole Holm Nielsen 
mailto:ole.h.niel...@fysik.dtu.dk>> wrote:
Hi Åke,

The make actually fails as shown below.  There are hundreds of configure
and checking lines above the lines I display, and the first make command
fails as shown in the output.

Can you suggest anything else to check?  Are there issues with AVX512 on
Skylake, and if so, how to work around it?

FYI, the foss-2018a and foss-2018b toolchains have been built without
problems on the Skylake node.

Thanks,
Ole


On 20-02-2019 18:01, Åke Sandgren wrote:
> That's not the real problem.
> You have to look through that log and figure out what it really is.
> I.e., where does the make actually fail.
>
> On 2/20/19 4:10 PM, Ole Holm Nielsen wrote:
>> On 2/20/19 2:45 PM, Åke Sandgren wrote:
>>> What is the actual error? Look in
>>> /tmp/eb-dyNH9x/easybuild-binutils-2.31.1-20190220.140138.qdBpn.log
>>
>> It's:
>>
>> $ tail /tmp/eb-dyNH9x/easybuild-binutils-2.31.1-20190220.140138.qdBpn.log
>> config.status: executing default commands
>> make[1]: Leaving directory
>> `/home/modules/build/binutils/2.31.1/dummy-/binutils-2.31.1'
>> make: *** [all] Error 2
>>   (at easybuild/tools/run.py:501 in parse_cmd_output)
>> == 2019-02-20 14:02:45,435 easyblock.py:2870 WARNING build failed (first
>> 300 chars): cmd " env LIBS='-Wl,-rpath=/usr/lib -Wl,-rpath=/usr/lib64'
>> make -j 80  CFLAGS="-g -O2 -fPIC" " exited with exit code 2 and output:
>> make[1]: Entering directory
>> `/home/modules/build/binutils/2.31.1/dummy-/binutils-2.31.1'
>> make[1]: Nothing to be done for `all-target'.
>> Configuring in ./libiberty
>> Config
>> == 2019-02-20 14:02:45,435 easyblock.py:288 INFO Closing log for
>> application name binutils version 2.31.1
>
>

Re: [easybuild] Building foss-2019a fails in binutils-2.31.1.eb (Skylake node)

[Mikael Öhman]

Hi Ole,

That still isn't the error; there should be the actual line, doing whatever
compilation or linking, that failed. They just tend to be somewhere in
middle of the huge output from the make command (even worse with parallel
builds).
You can put the entire log in some pastebin and someone is  (probably)
willing to take a look.

I've built the entire 2019a toolchains on skylake server (with AVX512),
without any modifications to any configs or blocks (on a virtual machine
though, but all CPU features were exposed to the VM)

Best regards, Mikael


On Wed, Feb 20, 2019 at 8:58 PM Ole Holm Nielsen 
wrote:

> Hi Åke,
>
> The make actually fails as shown below.  There are hundreds of configure
> and checking lines above the lines I display, and the first make command
> fails as shown in the output.
>
> Can you suggest anything else to check?  Are there issues with AVX512 on
> Skylake, and if so, how to work around it?
>
> FYI, the foss-2018a and foss-2018b toolchains have been built without
> problems on the Skylake node.
>
> Thanks,
> Ole
>
>
> On 20-02-2019 18:01, Åke Sandgren wrote:
> > That's not the real problem.
> > You have to look through that log and figure out what it really is.
> > I.e., where does the make actually fail.
> >
> > On 2/20/19 4:10 PM, Ole Holm Nielsen wrote:
> >> On 2/20/19 2:45 PM, Åke Sandgren wrote:
> >>> What is the actual error? Look in
> >>> /tmp/eb-dyNH9x/easybuild-binutils-2.31.1-20190220.140138.qdBpn.log
> >>
> >> It's:
> >>
> >> $ tail
> /tmp/eb-dyNH9x/easybuild-binutils-2.31.1-20190220.140138.qdBpn.log
> >> config.status: executing default commands
> >> make[1]: Leaving directory
> >> `/home/modules/build/binutils/2.31.1/dummy-/binutils-2.31.1'
> >> make: *** [all] Error 2
> >>   (at easybuild/tools/run.py:501 in parse_cmd_output)
> >> == 2019-02-20 14:02:45,435 easyblock.py:2870 WARNING build failed (first
> >> 300 chars): cmd " env LIBS='-Wl,-rpath=/usr/lib -Wl,-rpath=/usr/lib64'
> >> make -j 80  CFLAGS="-g -O2 -fPIC" " exited with exit code 2 and output:
> >> make[1]: Entering directory
> >> `/home/modules/build/binutils/2.31.1/dummy-/binutils-2.31.1'
> >> make[1]: Nothing to be done for `all-target'.
> >> Configuring in ./libiberty
> >> Config
> >> == 2019-02-20 14:02:45,435 easyblock.py:288 INFO Closing log for
> >> application name binutils version 2.31.1
> >
> >
>

Re: [easybuild] Building foss-2019a fails in binutils-2.31.1.eb (Skylake node)

[Ole Holm Nielsen]

Hi Åke,

The make actually fails as shown below.  There are hundreds of configure 
and checking lines above the lines I display, and the first make command 
fails as shown in the output.


Can you suggest anything else to check?  Are there issues with AVX512 on 
Skylake, and if so, how to work around it?


FYI, the foss-2018a and foss-2018b toolchains have been built without 
problems on the Skylake node.


Thanks,
Ole


On 20-02-2019 18:01, Åke Sandgren wrote:

That's not the real problem.
You have to look through that log and figure out what it really is.
I.e., where does the make actually fail.

On 2/20/19 4:10 PM, Ole Holm Nielsen wrote:

On 2/20/19 2:45 PM, Åke Sandgren wrote:

What is the actual error? Look in
/tmp/eb-dyNH9x/easybuild-binutils-2.31.1-20190220.140138.qdBpn.log


It's:

$ tail /tmp/eb-dyNH9x/easybuild-binutils-2.31.1-20190220.140138.qdBpn.log
config.status: executing default commands
make[1]: Leaving directory
`/home/modules/build/binutils/2.31.1/dummy-/binutils-2.31.1'
make: *** [all] Error 2
  (at easybuild/tools/run.py:501 in parse_cmd_output)
== 2019-02-20 14:02:45,435 easyblock.py:2870 WARNING build failed (first
300 chars): cmd " env LIBS='-Wl,-rpath=/usr/lib -Wl,-rpath=/usr/lib64'
make -j 80  CFLAGS="-g -O2 -fPIC" " exited with exit code 2 and output:
make[1]: Entering directory
`/home/modules/build/binutils/2.31.1/dummy-/binutils-2.31.1'
make[1]: Nothing to be done for `all-target'.
Configuring in ./libiberty
Config
== 2019-02-20 14:02:45,435 easyblock.py:288 INFO Closing log for
application name binutils version 2.31.1

Re: [easybuild] Building foss-2019a fails in binutils-2.31.1.eb (Skylake node)

[Ole Holm Nielsen]

On 2/20/19 2:45 PM, Åke Sandgren wrote:

What is the actual error? Look in
/tmp/eb-dyNH9x/easybuild-binutils-2.31.1-20190220.140138.qdBpn.log


It's:

$ tail /tmp/eb-dyNH9x/easybuild-binutils-2.31.1-20190220.140138.qdBpn.log
config.status: executing default commands
make[1]: Leaving directory 
`/home/modules/build/binutils/2.31.1/dummy-/binutils-2.31.1'

make: *** [all] Error 2
 (at easybuild/tools/run.py:501 in parse_cmd_output)
== 2019-02-20 14:02:45,435 easyblock.py:2870 WARNING build failed (first 
300 chars): cmd " env LIBS='-Wl,-rpath=/usr/lib -Wl,-rpath=/usr/lib64' 
make -j 80  CFLAGS="-g -O2 -fPIC" " exited with exit code 2 and output:
make[1]: Entering directory 
`/home/modules/build/binutils/2.31.1/dummy-/binutils-2.31.1'

make[1]: Nothing to be done for `all-target'.
Configuring in ./libiberty
Config
== 2019-02-20 14:02:45,435 easyblock.py:288 INFO Closing log for 
application name binutils version 2.31.1





On 2/20/19 2:18 PM, Ole Holm Nielsen wrote:

I'm trying to build the foss-2019a toolchain with EB 3.8.1 on a new
Intel Skylake node (40 cores + hyperthreading = 80 cores) but it fails
in binutils-2.31.1.eb as shown below.  I've tried to increase some
system limits, but that doesn't seem to help.  My current limits are:

$ ulimit -a
core file size  (blocks, -c) 0
data seg size   (kbytes, -d) 5000
scheduling priority (-e) 0
file size   (blocks, -f) unlimited
pending signals (-i) 3088986
max locked memory   (kbytes, -l) 64
max memory size (kbytes, -m) 5000
open files  (-n) 2500
pipe size    (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority  (-r) 0
stack size  (kbytes, -s) 4000
cpu time   (seconds, -t) 3
max user processes  (-u) 2000
virtual memory  (kbytes, -v) unlimited
file locks  (-x) unlimited

Output from the build process:

$ eb foss-2019a.eb -r
== temporary log file in case of crash /tmp/eb-dyNH9x/easybuild-u8cWAg.log
== resolving dependencies ...
== processing EasyBuild easyconfig
/home/modules/software/EasyBuild/3.8.1/lib/python2.7/site-packages/easybuild_easyconfigs-3.8.1-py2.7.egg/easybuild/easyconfigs/b/binutils/binutils-2.31.1.eb

== building and installing binutils/2.31.1...
== fetching files...
== creating build dir, resetting environment...
== unpacking...
== patching...
== preparing...
== configuring...
== building...
== FAILED: Installation ended unsuccessfully (build directory:
/home/modules/build/binutils/2.31.1/dummy-): build failed (first 300
chars): cmd " env LIBS='-Wl,-rpath=/usr/lib -Wl,-rpath=/usr/lib64'  make
-j 80  CFLAGS="-g -O2 -fPIC" " exited with exit code 2 and output:
make[1]: Entering directory
`/home/modules/build/binutils/2.31.1/dummy-/binutils-2.31.1'
make[1]: Nothing to be done for `all-target'.
Configuring in ./libiberty
Config
== Results of the build can be found in the log file(s)
/tmp/eb-dyNH9x/easybuild-binutils-2.31.1-20190220.140138.qdBpn.log
ERROR: Build of
/home/modules/software/EasyBuild/3.8.1/lib/python2.7/site-packages/easybuild_easyconfigs-3.8.1-py2.7.egg/easybuild/easyconfigs/b/binutils/binutils-2.31.1.eb
failed (err: 'build failed (first 300 chars): cmd " env
LIBS=\'-Wl,-rpath=/usr/lib -Wl,-rpath=/usr/lib64\'  make -j 80
CFLAGS="-g -O2 -fPIC" " exited with exit code 2 and output:\nmake[1]:
Entering directory
`/home/modules/build/binutils/2.31.1/dummy-/binutils-2.31.1\'\nmake[1]:
Nothing to be done for `all-target\'.\nConfiguring in ./libiberty\nConfig')

Can anyone help me fix this issue?

Thanks,
Ole





--
Ole Holm Nielsen
PhD, Senior HPC Officer
Department of Physics, Technical University of Denmark,
Building 307, DK-2800 Kongens Lyngby, Denmark
E-mail: ole.h.niel...@fysik.dtu.dk
Homepage: http://dcwww.fysik.dtu.dk/~ohnielse/
Tel: (+45) 4525 3187 / Mobile (+45) 5180 1620

Re: [easybuild] Building foss-2019a fails in binutils-2.31.1.eb (Skylake node)

[Alvarez, Damian]

I have binutils 2.31.1 on Skylake. It has been compiled without avx512 support 
though. I am not sure if that could play a role.

Damian

On 20.02.19, 14:46, "easybuild-requ...@lists.ugent.be on behalf of Åke 
Sandgren"  wrote:

What is the actual error? Look in
/tmp/eb-dyNH9x/easybuild-binutils-2.31.1-20190220.140138.qdBpn.log


On 2/20/19 2:18 PM, Ole Holm Nielsen wrote:
> I'm trying to build the foss-2019a toolchain with EB 3.8.1 on a new
> Intel Skylake node (40 cores + hyperthreading = 80 cores) but it fails
> in binutils-2.31.1.eb as shown below.  I've tried to increase some
> system limits, but that doesn't seem to help.  My current limits are:
>
> $ ulimit -a
> core file size  (blocks, -c) 0
> data seg size   (kbytes, -d) 5000
> scheduling priority (-e) 0
> file size   (blocks, -f) unlimited
> pending signals (-i) 3088986
> max locked memory   (kbytes, -l) 64
> max memory size (kbytes, -m) 5000
> open files  (-n) 2500
> pipe size(512 bytes, -p) 8
> POSIX message queues (bytes, -q) 819200
> real-time priority  (-r) 0
> stack size  (kbytes, -s) 4000
> cpu time   (seconds, -t) 3
> max user processes  (-u) 2000
> virtual memory  (kbytes, -v) unlimited
> file locks  (-x) unlimited
>
> Output from the build process:
>
> $ eb foss-2019a.eb -r
> == temporary log file in case of crash /tmp/eb-dyNH9x/easybuild-u8cWAg.log
> == resolving dependencies ...
> == processing EasyBuild easyconfig
> 
/home/modules/software/EasyBuild/3.8.1/lib/python2.7/site-packages/easybuild_easyconfigs-3.8.1-py2.7.egg/easybuild/easyconfigs/b/binutils/binutils-2.31.1.eb
>
> == building and installing binutils/2.31.1...
> == fetching files...
> == creating build dir, resetting environment...
> == unpacking...
> == patching...
> == preparing...
> == configuring...
> == building...
> == FAILED: Installation ended unsuccessfully (build directory:
> /home/modules/build/binutils/2.31.1/dummy-): build failed (first 300
> chars): cmd " env LIBS='-Wl,-rpath=/usr/lib -Wl,-rpath=/usr/lib64'  make
> -j 80  CFLAGS="-g -O2 -fPIC" " exited with exit code 2 and output:
> make[1]: Entering directory
> `/home/modules/build/binutils/2.31.1/dummy-/binutils-2.31.1'
> make[1]: Nothing to be done for `all-target'.
> Configuring in ./libiberty
> Config
> == Results of the build can be found in the log file(s)
> /tmp/eb-dyNH9x/easybuild-binutils-2.31.1-20190220.140138.qdBpn.log
> ERROR: Build of
> 
/home/modules/software/EasyBuild/3.8.1/lib/python2.7/site-packages/easybuild_easyconfigs-3.8.1-py2.7.egg/easybuild/easyconfigs/b/binutils/binutils-2.31.1.eb
> failed (err: 'build failed (first 300 chars): cmd " env
> LIBS=\'-Wl,-rpath=/usr/lib -Wl,-rpath=/usr/lib64\'  make -j 80
> CFLAGS="-g -O2 -fPIC" " exited with exit code 2 and output:\nmake[1]:
> Entering directory
> `/home/modules/build/binutils/2.31.1/dummy-/binutils-2.31.1\'\nmake[1]:
> Nothing to be done for `all-target\'.\nConfiguring in 
./libiberty\nConfig')
>
> Can anyone help me fix this issue?
>
> Thanks,
> Ole
>

--
Ake Sandgren, HPC2N, Umea University, S-90187 Umea, Sweden
Internet: a...@hpc2n.umu.se   Phone: +46 90 7866134 Fax: +46 90-580 14
Mobile: +46 70 7716134 WWW: http://www.hpc2n.umu.se






Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher
Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender),
Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
Prof. Dr. Sebastian M. Schmidt

Re: [easybuild] Building foss-2019a fails in binutils-2.31.1.eb (Skylake node)

[Åke Sandgren]

What is the actual error? Look in
/tmp/eb-dyNH9x/easybuild-binutils-2.31.1-20190220.140138.qdBpn.log


On 2/20/19 2:18 PM, Ole Holm Nielsen wrote:
> I'm trying to build the foss-2019a toolchain with EB 3.8.1 on a new
> Intel Skylake node (40 cores + hyperthreading = 80 cores) but it fails
> in binutils-2.31.1.eb as shown below.  I've tried to increase some
> system limits, but that doesn't seem to help.  My current limits are:
> 
> $ ulimit -a
> core file size  (blocks, -c) 0
> data seg size   (kbytes, -d) 5000
> scheduling priority (-e) 0
> file size   (blocks, -f) unlimited
> pending signals (-i) 3088986
> max locked memory   (kbytes, -l) 64
> max memory size (kbytes, -m) 5000
> open files  (-n) 2500
> pipe size    (512 bytes, -p) 8
> POSIX message queues (bytes, -q) 819200
> real-time priority  (-r) 0
> stack size  (kbytes, -s) 4000
> cpu time   (seconds, -t) 3
> max user processes  (-u) 2000
> virtual memory  (kbytes, -v) unlimited
> file locks  (-x) unlimited
> 
> Output from the build process:
> 
> $ eb foss-2019a.eb -r
> == temporary log file in case of crash /tmp/eb-dyNH9x/easybuild-u8cWAg.log
> == resolving dependencies ...
> == processing EasyBuild easyconfig
> /home/modules/software/EasyBuild/3.8.1/lib/python2.7/site-packages/easybuild_easyconfigs-3.8.1-py2.7.egg/easybuild/easyconfigs/b/binutils/binutils-2.31.1.eb
> 
> == building and installing binutils/2.31.1...
> == fetching files...
> == creating build dir, resetting environment...
> == unpacking...
> == patching...
> == preparing...
> == configuring...
> == building...
> == FAILED: Installation ended unsuccessfully (build directory:
> /home/modules/build/binutils/2.31.1/dummy-): build failed (first 300
> chars): cmd " env LIBS='-Wl,-rpath=/usr/lib -Wl,-rpath=/usr/lib64'  make
> -j 80  CFLAGS="-g -O2 -fPIC" " exited with exit code 2 and output:
> make[1]: Entering directory
> `/home/modules/build/binutils/2.31.1/dummy-/binutils-2.31.1'
> make[1]: Nothing to be done for `all-target'.
> Configuring in ./libiberty
> Config
> == Results of the build can be found in the log file(s)
> /tmp/eb-dyNH9x/easybuild-binutils-2.31.1-20190220.140138.qdBpn.log
> ERROR: Build of
> /home/modules/software/EasyBuild/3.8.1/lib/python2.7/site-packages/easybuild_easyconfigs-3.8.1-py2.7.egg/easybuild/easyconfigs/b/binutils/binutils-2.31.1.eb
> failed (err: 'build failed (first 300 chars): cmd " env
> LIBS=\'-Wl,-rpath=/usr/lib -Wl,-rpath=/usr/lib64\'  make -j 80
> CFLAGS="-g -O2 -fPIC" " exited with exit code 2 and output:\nmake[1]:
> Entering directory
> `/home/modules/build/binutils/2.31.1/dummy-/binutils-2.31.1\'\nmake[1]:
> Nothing to be done for `all-target\'.\nConfiguring in ./libiberty\nConfig')
> 
> Can anyone help me fix this issue?
> 
> Thanks,
> Ole
> 

-- 
Ake Sandgren, HPC2N, Umea University, S-90187 Umea, Sweden
Internet: a...@hpc2n.umu.se   Phone: +46 90 7866134 Fax: +46 90-580 14
Mobile: +46 70 7716134 WWW: http://www.hpc2n.umu.se

[easybuild] Building foss-2019a fails in binutils-2.31.1.eb (Skylake node)

[Ole Holm Nielsen]

I'm trying to build the foss-2019a toolchain with EB 3.8.1 on a new 
Intel Skylake node (40 cores + hyperthreading = 80 cores) but it fails 
in binutils-2.31.1.eb as shown below.  I've tried to increase some 
system limits, but that doesn't seem to help.  My current limits are:


$ ulimit -a
core file size  (blocks, -c) 0
data seg size   (kbytes, -d) 5000
scheduling priority (-e) 0
file size   (blocks, -f) unlimited
pending signals (-i) 3088986
max locked memory   (kbytes, -l) 64
max memory size (kbytes, -m) 5000
open files  (-n) 2500
pipe size(512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority  (-r) 0
stack size  (kbytes, -s) 4000
cpu time   (seconds, -t) 3
max user processes  (-u) 2000
virtual memory  (kbytes, -v) unlimited
file locks  (-x) unlimited

Output from the build process:

$ eb foss-2019a.eb -r
== temporary log file in case of crash /tmp/eb-dyNH9x/easybuild-u8cWAg.log
== resolving dependencies ...
== processing EasyBuild easyconfig 
/home/modules/software/EasyBuild/3.8.1/lib/python2.7/site-packages/easybuild_easyconfigs-3.8.1-py2.7.egg/easybuild/easyconfigs/b/binutils/binutils-2.31.1.eb

== building and installing binutils/2.31.1...
== fetching files...
== creating build dir, resetting environment...
== unpacking...
== patching...
== preparing...
== configuring...
== building...
== FAILED: Installation ended unsuccessfully (build directory: 
/home/modules/build/binutils/2.31.1/dummy-): build failed (first 300 
chars): cmd " env LIBS='-Wl,-rpath=/usr/lib -Wl,-rpath=/usr/lib64'  make 
-j 80  CFLAGS="-g -O2 -fPIC" " exited with exit code 2 and output:
make[1]: Entering directory 
`/home/modules/build/binutils/2.31.1/dummy-/binutils-2.31.1'

make[1]: Nothing to be done for `all-target'.
Configuring in ./libiberty
Config
== Results of the build can be found in the log file(s) 
/tmp/eb-dyNH9x/easybuild-binutils-2.31.1-20190220.140138.qdBpn.log
ERROR: Build of 
/home/modules/software/EasyBuild/3.8.1/lib/python2.7/site-packages/easybuild_easyconfigs-3.8.1-py2.7.egg/easybuild/easyconfigs/b/binutils/binutils-2.31.1.eb 
failed (err: 'build failed (first 300 chars): cmd " env 
LIBS=\'-Wl,-rpath=/usr/lib -Wl,-rpath=/usr/lib64\'  make -j 80 
CFLAGS="-g -O2 -fPIC" " exited with exit code 2 and output:\nmake[1]: 
Entering directory 
`/home/modules/build/binutils/2.31.1/dummy-/binutils-2.31.1\'\nmake[1]: 
Nothing to be done for `all-target\'.\nConfiguring in ./libiberty\nConfig')


Can anyone help me fix this issue?

Thanks,
Ole

--
Ole Holm Nielsen
PhD, Senior HPC Officer
Department of Physics, Technical University of Denmark