[INFO ]  Installing C library: done in 993.53s (at 46:21)
[INFO ]  =================================================================
[INFO ]  Installing final gcc compiler
[ERROR]    {standard input}:1946129: Error: unknown pseudo-op: `.lbb8598'
[ERROR]    {standard input}: Error: open CFI at the end of file; missing .cfi_endproc directive
[ERROR]    g++: fatal error: Killed signal terminated program cc1plus
[ERROR]    make[4]: *** [Makefile:1158: gimple-match.o] Error 1
[ERROR]    make[4]: *** Waiting for unfinished jobs....
[ERROR]    make[3]: *** [Makefile:4625: all-gcc] Error 2
[ERROR]    make[2]: *** [Makefile:1042: all] Error 2
[ERROR]   
[ERROR]  >>
[ERROR]  >>  Build failed in step 'Installing final gcc compiler'
[ERROR]  >>        called in step '(top-level)'
[ERROR]  >>
[ERROR]  >>  Error happened in: CT_DoExecLog[scripts/functions@377]
[ERROR]  >>        called from: do_gcc_backend[scripts/build/cc/gcc.sh@1287]
[ERROR]  >>        called from: do_cc_for_host[scripts/build/cc/gcc.sh@893]
[ERROR]  >>        called from: main[scripts/crosstool-NG.sh@708]
[ERROR]  >>
[ERROR]  >>  For more info on this error, look at the file: 'build.log'
[ERROR]  >>  There is a list of known issues, some with workarounds, in:
[ERROR]  >>      https://crosstool-ng.github.io/docs/known-issues/
[ERROR]  >>
[ERROR]  >> NOTE: Your configuration includes features marked EXPERIMENTAL.
[ERROR]  >> Before submitting a bug report, try to reproduce it without enabling
[ERROR]  >> any experimental features. Otherwise, you'll need to debug it
[ERROR]  >> and present an explanation why it is a bug in crosstool-NG - or
[ERROR]  >> preferably, a fix.
[ERROR]  >>
[ERROR]  >>  If you feel this is a bug in crosstool-NG, report it at:
[ERROR]  >>      https://github.com/crosstool-ng/crosstool-ng/issues/
[ERROR]  >>
[ERROR]  >>  Make sure your report includes all the information pertinent to this issue.
[ERROR]  >>  Read the bug reporting guidelines here:
[ERROR]  >>      http://crosstool-ng.github.io/support/
[ERROR]   
[ERROR]  (elapsed: 89:41.60)
[89:44] / gmake[1]: *** [ct-ng:261: build] Fehler 2
make: *** [package/crosstool-ng/crosstool-ng.mk:120: crosstool-ng.do_compile] Fehler 2
janus@Martin:~/development/single_bs_ni$ 


[INFO ]  Installing C library: done in 1031.23s (at 46:48)
[INFO ]  =================================================================
[INFO ]  Installing final gcc compiler
[ERROR]    {standard input}:2098766: Error: no such instruction: `m'
[ERROR]    {standard input}: Error: open CFI at the end of file; missing .cfi_endproc directive
[ERROR]    g++: fatal error: Killed signal terminated program cc1plus
[ERROR]    make[4]: *** [Makefile:1158: gimple-match.o] Error 1
[ERROR]    make[3]: *** [Makefile:4625: all-gcc] Error 2
[ERROR]    make[2]: *** [Makefile:1042: all] Error 2
[ERROR]   
[ERROR]  >>
[ERROR]  >>  Build failed in step 'Installing final gcc compiler'
[ERROR]  >>        called in step '(top-level)'
[ERROR]  >>
[ERROR]  >>  Error happened in: CT_DoExecLog[scripts/functions@377]
[ERROR]  >>        called from: do_gcc_backend[scripts/build/cc/gcc.sh@1287]
[ERROR]  >>        called from: do_cc_for_host[scripts/build/cc/gcc.sh@893]
[ERROR]  >>        called from: main[scripts/crosstool-NG.sh@708]
[ERROR]  >>
[ERROR]  >>  For more info on this error, look at the file: 'build.log'
[ERROR]  >>  There is a list of known issues, some with workarounds, in:
[ERROR]  >>      https://crosstool-ng.github.io/docs/known-issues/
[ERROR]  >>
[ERROR]  >> NOTE: Your configuration includes features marked EXPERIMENTAL.
[ERROR]  >> Before submitting a bug report, try to reproduce it without enabling
[ERROR]  >> any experimental features. Otherwise, you'll need to debug it
[ERROR]  >> and present an explanation why it is a bug in crosstool-NG - or
[ERROR]  >> preferably, a fix.
[ERROR]  >>
[ERROR]  >>  If you feel this is a bug in crosstool-NG, report it at:
[ERROR]  >>      https://github.com/crosstool-ng/crosstool-ng/issues/
[ERROR]  >>
[ERROR]  >>  Make sure your report includes all the information pertinent to this issue.
[ERROR]  >>  Read the bug reporting guidelines here:
[ERROR]  >>      http://crosstool-ng.github.io/support/
[ERROR]   
[ERROR]  (elapsed: 69:27.79)
[69:30] / gmake[1]: *** [ct-ng:261: build] Fehler 2
make: *** [package/crosstool-ng/crosstool-ng.mk:120: crosstool-ng.do_compile] Fehler 2
janus@Martin:~/development/single_bs_ni$ 


Fehlerstelle im Code:
    # This while-loop goes hand-in-hand with the ERR trap handler:
    # - if the command terminates successfully, then we hit the break
    #   statement, and we exit the loop
    # - if the command terminates in error, then the ERR handler kicks
    #   in, then:
    #     - if the user did *not* ask for interactive debugging, the ERR
    #       handler exits, and we hit the end of the sub-shell
    #     - if the user did ask for interactive debugging, the ERR handler
    #       spawns a shell. Upon termination of this shell, the ERR handler
    #       examines the exit status of the shell:
    #         - if 1, the ERR handler returns; then we hit the else statement,
    #           then the break, and we exit the 'while' loop, to continue the
    #           build;
    #         - if 2, the ERR handler touches the repeat file, and returns;
    #           then we hit the if statement, and we loop for one more
    #           iteration;
    #         - if 3, the ERR handler exits with the command's exit status,
    #           and we're dead;
    #         - for any other exit status of the shell, the ERR handler
    #           prints an informational message, and respawns the shell
    #
    # This allows a user to get an interactive shell that has the same
    # environment (PATH and so on) that the failed command was ran with.
    while true; do
        rm -f "${CT_BUILD_DIR}/repeat"
	CT_DoLog DEBUG "==> Executing: ${cur_cmd}"

377         =>              "${@}" 2>&1 |CT_DoLog "${level}"

	ret="${?}"
	if [ -f "${CT_BUILD_DIR}/repeat" ]; then
            rm -f "${CT_BUILD_DIR}/repeat"
            continue
        elif [ -f "${CT_BUILD_DIR}/skip" ]; then
            rm -f "${CT_BUILD_DIR}/skip"
            ret=0
            break
        else
            break
        fi
    done
    CT_DoLog DEBUG "==> Return status ${ret}"
    exit ${ret}
    )
    # Catch failure of the sub-shell
    [ $? -eq 0 ]
}


