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 -fPIC conftest.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 <micket...@gmail.com <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 <ole.h.niel...@fysik.dtu.dk <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
    >
    >

Reply via email to