-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build error on arm32v7/debian:stretch #76
Comments
Read your configure.log. This is a problem of your environment. |
Here the incriminated log
This also happens, with the same error output, with the My best guess is that it's related to these lines: Lines 136 to 157 in 66e43c4
gcc is now -ge 6 in arm32v7/debian:stretch .
# gcc --version
gcc (Debian 6.3.0-18+deb9u1) 6.3.0 20170516
Copyright (C) 2016 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
$ gcc --version
gcc (Raspbian 6.3.0-18+rpi1+deb9u1) 6.3.0 20170516
Copyright (C) 2016 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. This line in particular seems to be the culprit Line 153 in 66e43c4
|
@devster31 I need an |
CPPFLAGS are used for building both C and C++ programs, and clang complains when -std=c++11 is used when the driver is invoked in C mode. Using CXXFLAGS to set this allows rtorrent-ps to be successfully built with clang. Unfortunately, fixing CXXFLAGS requires a new hack to ensure -O2 is uniformly used. Otherwise, autoconf will break when detecting XMLRPC-C support with an error like the one in pyroscope#76.
Changes to CFLAGS/CXXFLAGS/LIBS affect following lines in configure.ac. As originally written, this would cause random libraries, such as libtorrent, to be linked into the autoconf test program. Occasionally, this would cause the things like the pkgconfig checks to fail with mysterious linker errors (e.g. pyroscope#76). Instead, only populate these global flags with the additional flags for dependencies at the very end, before the invocation of AC_OUTPUT.
Changes to CFLAGS/CXXFLAGS/LIBS affect following lines in configure.ac. As originally written, this would cause random libraries, such as libtorrent, to be linked into the autoconf test program. Occasionally, this would cause the things like the pkgconfig checks to fail with mysterious linker errors (e.g. pyroscope#76). Instead, only populate these global flags with the additional flags for dependencies at the very end, before the invocation of AC_OUTPUT.
Changes to CFLAGS/CXXFLAGS/LIBS affect following lines in configure.ac. As originally written, this would cause random libraries, such as libtorrent, to be linked into the autoconf test program. Occasionally, this would cause the things like the pkgconfig checks to fail with mysterious linker errors (e.g. pyroscope#76). Instead, only populate these global flags with the additional flags for dependencies at the very end, before the invocation of AC_OUTPUT.
CPPFLAGS are used for building both C and C++ programs, and clang complains when -std=c++11 is used when the driver is invoked in C mode. Using CXXFLAGS to set this allows rtorrent-ps to be successfully built with clang. Unfortunately, fixing CXXFLAGS requires a new hack to ensure -O2 is uniformly used. Otherwise, autoconf will break when detecting XMLRPC-C support with an error like the one in pyroscope#76. (cherry picked from commit 4453af5)
Changes to CFLAGS/CXXFLAGS/LIBS affect following lines in configure.ac. As originally written, this would cause random libraries, such as libtorrent, to be linked into the autoconf test program. Occasionally, this would cause the things like the pkgconfig checks to fail with mysterious linker errors (e.g. pyroscope#76). Instead, only populate these global flags with the additional flags for dependencies at the very end, before the invocation of AC_OUTPUT. (cherry picked from commit 9fb9d88)
I'm encountering the below error on a clean system after following instruction and documentation.
checking for XMLRPC-C... failed configure: error: Could not compile XMLRPC-C test.
and here the entire history of commands ran:
The system is a Scaleway server (C1) with an
armv7l_armhf
CPU (Marvell Armada I believe).The failure is, as far as I can see, during the building steps for
rtorrent
itself.The text was updated successfully, but these errors were encountered: