Your message dated Wed, 9 Dec 2020 11:18:02 +0100
with message-id <[email protected]>
and subject line Re: Bug#976947: mapbox-variant: FTBFS on ppc64el
(arch:all-only src pkg): g++: error: unrecognized command-line option
‘-march=native’; did you mean ‘-mcpu=native’?
has caused the Debian Bug report #976947,
regarding mapbox-variant: FTBFS on ppc64el (arch:all-only src pkg): g++: error:
unrecognized command-line option ‘-march=native’; did you mean ‘-mcpu=native’?
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
976947: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976947
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: mapbox-variant
Version: 1.2.0-1
Severity: serious
Justification: FTBFS on ppc64el
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el
Hi,
During a rebuild of all packages in sid, your package failed to build
on ppc64el. At the same time, it did not fail on amd64.
I'm marking this bug as severity:serious since your package has only
Architecture:all binary packages, and should thus, in theory, build
everywhere. Failure to build on ppc64el might indicate a serious issue
in this package or in another package.
But feel free to downgrade or close if you believe that this is only a
build-time issue. (I would personnally prefer a severity:minor bug just to
track that the package can only be built on specific architectures.)
Relevant part (hopefully):
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> mkdir -p ./out
> mkdir -p ./out
> mkdir -p ./out
> mkdir -p ./out
> g++ -o out/bench-variant test/bench_variant.cpp -I./include -isystem
> test/include -std=c++11 -Werror -Wall -Wextra -pedantic -Wformat=2
> -Wsign-conversion -Wshadow -Wunused-parameter -O3 -DNDEBUG -march=native
> -DSINGLE_THREADED -fvisibility-inlines-hidden -fvisibility=hidden -g -O2
> -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat
> -Werror=format-security -pthread -Wl,-z,relro
> g++ -o out/unique_ptr_test test/unique_ptr_test.cpp -I./include -isystem
> test/include -std=c++11 -Werror -Wall -Wextra -pedantic -Wformat=2
> -Wsign-conversion -Wshadow -Wunused-parameter -O3 -DNDEBUG -march=native
> -DSINGLE_THREADED -fvisibility-inlines-hidden -fvisibility=hidden -g -O2
> -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat
> -Werror=format-security -pthread -Wl,-z,relro
> mkdir -p ./out
> g++ -o out/recursive_wrapper_test test/recursive_wrapper_test.cpp -I./include
> -isystem test/include -std=c++11 -Werror -Wall -Wextra -pedantic -Wformat=2
> -Wsign-conversion -Wshadow -Wunused-parameter -O3 -DNDEBUG -march=native
> -DSINGLE_THREADED -fvisibility-inlines-hidden -fvisibility=hidden -g -O2
> -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat
> -Werror=format-security -pthread -Wl,-z,relro
> g++ -o out/binary_visitor_test test/binary_visitor_test.cpp -I./include
> -isystem test/include -std=c++11 -Werror -Wall -Wextra -pedantic -Wformat=2
> -Wsign-conversion -Wshadow -Wunused-parameter -O3 -DNDEBUG -march=native
> -DSINGLE_THREADED -fvisibility-inlines-hidden -fvisibility=hidden -g -O2
> -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat
> -Werror=format-security -pthread -Wl,-z,relro
> mkdir -p ./out
> g++ -o out/lambda_overload_test test/lambda_overload_test.cpp -I./include
> -isystem test/include -std=c++11 -Werror -Wall -Wextra -pedantic -Wformat=2
> -Wsign-conversion -Wshadow -Wunused-parameter -O3 -DNDEBUG -march=native
> -DSINGLE_THREADED -fvisibility-inlines-hidden -fvisibility=hidden -g -O2
> -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat
> -Werror=format-security -pthread -Wl,-z,relro
> g++ -o out/hashable_test test/hashable_test.cpp -I./include -isystem
> test/include -std=c++11 -Werror -Wall -Wextra -pedantic -Wformat=2
> -Wsign-conversion -Wshadow -Wunused-parameter -O3 -DNDEBUG -march=native
> -DSINGLE_THREADED -fvisibility-inlines-hidden -fvisibility=hidden -g -O2
> -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat
> -Werror=format-security -pthread -Wl,-z,relro
> g++: error: unrecognized command-line option ‘-march=native’; did you mean
> ‘-mcpu=native’?
> make[1]: *** [Makefile:78: out/binary_visitor_test] Error 1
The full build log is available from:
http://qa-logs.debian.net/2020/12/09/mapbox-variant_1.2.0-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.
About the archive rebuild: The rebuild was done on a Power8 cluster part of the
Grid'5000 testbed. Hardware specs:
https://www.grid5000.fr/w/Grenoble:Hardware#drac
--- End Message ---
--- Begin Message ---
severity 976947 minor
tags 976947 wontfix
thanks
On 12/9/20 10:25 AM, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on ppc64el. At the same time, it did not fail on amd64.
>
> I'm marking this bug as severity:serious since your package has only
> Architecture:all binary packages, and should thus, in theory, build
> everywhere. Failure to build on ppc64el might indicate a serious issue
> in this package or in another package.
>
> But feel free to downgrade or close if you believe that this is only a
> build-time issue. (I would personnally prefer a severity:minor bug just to
> track that the package can only be built on specific architectures.)
The RC severity is not appropriate for theoretical issues. As long as
arch:all packages aren't actually built on non-x86 it is not a high
severity issue.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
--- End Message ---
_______________________________________________
Pkg-grass-devel mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-grass-devel
