From: Titus von Boxberg <titus@elbe-informatik.de>
To: Alexey Neyman <stilor@att.net>
Cc: "crossgcc@sourceware.org" <crossgcc@sourceware.org>
Subject: canadian cross host mingw: build of liblto_plugin-0.dll fails
Date: Fri, 15 Sep 2017 11:33:00 -0000 [thread overview]
Message-ID: <eccc45ee26674fcaa6ba87a80e98e9b1@elbe-informatik.de> (raw)
Alexey, all,
on opensuse linux, I'm trying to build an arm-none toolchain for host mingw-w64
with a fairly recent crosstool-NG.
As the build machine compiler I'm using gcc-7.2 from opensuse package
https://build.opensuse.org/package/show/windows%3Amingw%3Awin64/mingw64-cross-gcc
Everything is going smooth except that in the build step for the final gcc
libtool refuses to generate the liblto_plugin-0.dll
The command line is:
./libtool --tag=CC --tag=disable-static --mode=link x86_64-host_w64-mingw32-gcc -Wall -O2 -g -pipe -I/home/ELBE/titus/tmp/m32-ctng-m7/.build/HOST-x86_64-w64-mingw32/arm-m7-eabi/buildtools/complibs-host/include -Os -D__USE_MINGW_ACCESS -Wc,-static-libgcc -no-undefined -bindir "/opt/cross/arm-m7-eabi/bin" -module -bindir /opt/cross/arm-m7-eabi/libexec/gcc/arm-m7-eabi/7.2.0 -Wc,../libiberty/libiberty.a -Xcompiler '-static-libstdc++' -Xcompiler '-static-libgcc' '-L/home/ELBE/titus/tmp/m32-ctng-m7/.build/HOST-x86_64-w64-mingw32/arm-m7-eabi/buildtools/complibs-host/lib' '-lstdc++' '-lm' '-Wl,--stack,12582912' -o liblto_plugin.la -rpath /opt/cross/arm-m7-eabi/libexec/gcc/arm-m7-eabi/7.2.0 lto-plugin.lo
The message is:
*** Warning: linker path does not have real file for library -lstdc++.
*** I have the capability to make that library automatically link in when
*** you link to this library. But I can only do this if you have a
*** shared version of the library, which you do not appear to have
*** because I did check the linker path looking for a file starting
*** with libstdc++ but no candidates were found. (...for file magic test)
*** Warning: libtool could not satisfy all declared inter-library
*** dependencies of module liblto_plugin. Therefore, libtool will create
*** a static module, that should work as long as the dlopening
*** application is linked with the -dlopen flag.
libtool is looking into these paths:
/home/ELBE/titus/tmp/m32-ctng-m7/.build/HOST-x86_64-w64-mingw32/arm-m7-eabi/buildtools/complibs-host/lib
/usr/x86_64-w64-mingw32/lib
/usr/x86_64-w64-mingw32/sys-root/mingw/lib
I found that the opensuse c++ runtime package installs libstdc++-6.dll
into the bin directory of the sysroot
/usr/x86_64-w64-mingw32/sys-root/mingw/bin
When manually copying libstdc++-6.dll into the sysroot's lib directory, libtool is happy.
Any ideas where to look to get this fixed reliably?
Thanks already!
Regards,
Titus
next reply other threads:[~2017-09-15 11:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-15 11:33 Titus von Boxberg [this message]
2017-09-16 18:46 ` Alexey Neyman
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=eccc45ee26674fcaa6ba87a80e98e9b1@elbe-informatik.de \
--to=titus@elbe-informatik.de \
--cc=crossgcc@sourceware.org \
--cc=stilor@att.net \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).