From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Toolchin build fails with "debuggable toolchain internals"
Date: Wed, 8 Feb 2017 15:53:17 +0100 [thread overview]
Message-ID: <20170208145317.xa7pw67vjvqsmaqr@pengutronix.de> (raw)
In-Reply-To: <2001695162.155270.1485161757952@email.1und1.de>
Hi,
Please don't send html mails.
I've not tested this option in a long time. I think it may be related to
the linaro gcc release. Have you tried this with a newer toolchain?
Michael
On Mon, Jan 23, 2017 at 09:55:57AM +0100, - - wrote:
> <!DOCTYPE html>
> <html><head>
> <meta charset="UTF-8">
> </head><body><p>Hello,<br></p><p>to getting Valgrind running on my device I've need a toolchain with debug info. So I tried to compile the OSELAS.Toolchain-2012.12.1 with enabled "misc->debuggable toolchain internals".</p><p>Unfortunately the build fails with following error:<br></p><p>make[6]: Entering directory `/home/mm/Downloads/OSELAS.Toolchain-2012.12.1/platform-arm-cortexa8-linux-gnueabihf-gcc-4.7.3-glibc-2.16.0-binutils-2.22-kernel-3.6-sanitized/build-cross/gcc-linaro-4.7-2012.11-build/arm-cortexa8-linux-gnueabihf/libstdc++-v3/src'<br>/bin/bash ../libtool --tag CXX   --mode=link /home/mm/Downloads/OSELAS.Toolchain-2012.12.1/platform-arm-cortexa8-linux-gnueabihf-gcc-4.7.3-glibc-2.16.0-binutils-2.22-kernel-3.6-sanitized/build-cross/gcc-linaro-4.7-2012.11-build/./gcc/xgcc -shared-libgcc -B/home/mm/Downloads/OSELAS.Toolchain-2012.12.1/platform-arm-cortexa8-linux-gnueabihf-gcc-4.7.3-glibc-2.16.0-binutils-2.22-kernel-3.6-sanitized/build-cross/gcc-linaro-4.7-2012.11-build/./gcc -nostdinc++ -L/home/mm/Downloads/OSELAS.Toolchain-2012.12.1/platform-arm-cortexa8-linux-gnueabihf-gcc-4.7.3-glibc-2.16.0-binutils-2.22-kernel-3.6-sanitized/build-cross/gcc-linaro-4.7-2012.11-build/arm-cortexa8-linux-gnueabihf/libstdc++-v3/src -L/home/mm/Downloads/OSELAS.Toolchain-2012.12.1/platform-arm-cortexa8-linux-gnueabihf-gcc-4.7.3-glibc-2.16.0-binutils-2.22-kernel-3.6-sanitized/build-cross/gcc-linaro-4.7-2012.11-build/arm-cortexa8-linux-gnueabihf/libstdc++-v3/src/.libs -B/opt/OSELAS.Toolchain-2012.12.1/arm-cortexa8-linux-gnueabihf/gcc-4.7.3-glibc-2.16.0-binutils-2.22-kernel-3.6-sanitized/arm-cortexa8-linux-gnueabihf/bin/ -B/opt/OSELAS.Toolchain-2012.12.1/arm-cortexa8-linux-gnueabihf/gcc-4.7.3-glibc-2.16.0-binutils-2.22-kernel-3.6-sanitized/arm-cortexa8-linux-gnueabihf/lib/ -isystem /opt/OSELAS.Toolchain-2012.12.1/arm-cortexa8-linux-gnueabihf/gcc-4.7.3-glibc-2.16.0-binutils-2.22-kernel-3.6-sanitized/arm-cortexa8-linux-gnueabihf/include -isystem /opt/OSELAS.Toolchain-2012.12.1/arm-cortexa8-linux-gnueabihf/gcc-4.7.3-glibc-2.16.0-binutils-2.22-kernel-3.6-sanitized/arm-cortexa8-linux-gnueabihf/sys-include    -Wl,-O1 -Wl,-z,relro -Wl,--gc-sections  -fPIC -DPIC  -Wall -Wextra -Wwrite-strings -Wcast-qual -Wabi  -fdiagnostics-show-location=once   -ffunction-sections -fdata-sections  -frandom-seed=libstdc++convenience.la  -o libstdc++convenience.la  ../libsupc++/libsupc++convenience.la ../src/c++98/libc++98convenience.la ../src/c++11/libc++11convenience.la ; \<br>    if test ! -f .libs/libstdc++.a; then \<br>      cp .libs/libstdc++convenience.a .libs/libstdc++.a; \<br>    fi; \<br>    echo `date` > stamp-libstdc++convenience;<br>(cd /home/mm/Downloads/OSELAS.Toolchain-2012.12.1/platform-arm-cortexa8-linux-gnueabihf-gcc-4.7.3-glibc-2.16.0-binutils-2.22-kernel-3.6-sanitized/build-cross/gcc-linaro-4.7-2012.11-build/arm-cortexa8-linux-gnueabihf/libstdc++-v3/src/debug; \<br>      mv Makefile Makefile.tmp; \<br>      sed -e 's,all-local: all-once,all-local:,' \<br>          -e 's,install-data-local: install-data-once,install-data-local:,' \<br>          -e '/vpath/!s,src/c,src/debug/c,' \<br>      < Makefile.tmp > Makefile ; \<br>      make CXXFLAGS='-gdwarf-4 -g3 -O0' \<br>      toolexeclibdir=/opt/OSELAS.Toolchain-2012.12.1/arm-cortexa8-linux-gnueabihf/gcc-4.7.3-glibc-2.16.0-binutils-2.22-kernel-3.6-sanitized/arm-cortexa8-linux-gnueabihf/lib/debug all) ;<br>cat: /opt/OSELAS.Toolchain-2012.12.1/arm-cortexa8-linux-gnueabihf/gcc-4.7.3-glibc-2.16.0-binutils-2.22-kernel-3.6-sanitized/src/debug/cross/gcc-linaro-4.7-2012.11/libstdc++-v3/../gcc/BASE-VER: No such file or directory<br></p><p><br></p><p>Without the debug optimization everything compiles well. I've tried also newer Toolchains but all failed with same error.<br></p><p>Any ideas?<br></p><p>Best Regards,<br></p><p>Ingo<br></p></body></html>
>
>
> _______________________________________________
> ptxdist mailing list
> ptxdist@pengutronix.de
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2017-02-08 14:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 8:55 - -
2017-02-08 14:53 ` Michael Olbrich [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170208145317.xa7pw67vjvqsmaqr@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox