From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] New package: ugdb-0.1.7.
Date: Sat, 11 Jul 2020 18:17:41 +0200 [thread overview]
Message-ID: <20200711161741.H29YiZNE6mSF1NNTcozORmdOQAuPuP6TVNZDsZv9pfY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23520@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 4049 bytes --]
New review comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/pull/23520#discussion_r453210054
Comment:
`vsed`ing the version seems to have done the trick.
Do you know of a test I could run to check how those pkg-config flags are being propagated across the build system?
```
The following warnings were emitted during compilation:
warning: cc1: sorry, unimplemented: 64-bit mode not compiled in
warning: cc1: sorry, unimplemented: 64-bit mode not compiled in
error: failed to run custom build command for `libz-sys v1.0.25`
Caused by:
process didn't exit successfully: `/builddir/ugdb-0.1.7/target/release/build/libz-sys-cf7ed1fe02cbb4c6/build-script-build` (exit code: 1)
--- stdout
cargo:rerun-if-env-changed=LIBZ_SYS_STATIC
cargo:rerun-if-changed=build.rs
cargo:rerun-if-env-changed=ZLIB_NO_PKG_CONFIG
cargo:rerun-if-env-changed=PKG_CONFIG
cargo:rerun-if-env-changed=ZLIB_STATIC
cargo:rerun-if-env-changed=ZLIB_DYNAMIC
cargo:rerun-if-env-changed=PKG_CONFIG_ALL_STATIC
cargo:rerun-if-env-changed=PKG_CONFIG_ALL_DYNAMIC
cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64-unknown-linux-musl
cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64_unknown_linux_musl
cargo:rerun-if-env-changed=HOST_PKG_CONFIG_PATH
cargo:rerun-if-env-changed=PKG_CONFIG_PATH
cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64-unknown-linux-musl
cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64_unknown_linux_musl
cargo:rerun-if-env-changed=HOST_PKG_CONFIG_LIBDIR
cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR
cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64-unknown-linux-musl
cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64_unknown_linux_musl
cargo:rerun-if-env-changed=HOST_PKG_CONFIG_SYSROOT_DIR
cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR
TARGET = Some("x86_64-unknown-linux-musl")
OPT_LEVEL = Some("3")
HOST = Some("x86_64-unknown-linux-musl")
CC_x86_64-unknown-linux-musl = None
CC_x86_64_unknown_linux_musl = None
HOST_CC = None
CC = Some("i686-linux-musl-gcc")
CFLAGS_x86_64-unknown-linux-musl = None
CFLAGS_x86_64_unknown_linux_musl = None
HOST_CFLAGS = None
CFLAGS = Some("-fstack-clash-protection -D_FORTIFY_SOURCE=2 -O2 -pipe -march=i686 -I/usr/i686-linux-musl/usr/include")
CRATE_CC_NO_DEFAULTS = None
DEBUG = Some("false")
CARGO_CFG_TARGET_FEATURE = Some("fxsr,sse,sse2")
running: "i686-linux-musl-gcc" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-m64" "-fstack-clash-protection" "-D_FORTIFY_SOURCE=2" "-O2" "-pipe" "-march=i686" "-I/usr/i686-linux-musl/usr/include" "-I" "src/zlib" "-fvisibility=hidden" "-DSTDC" "-D_LARGEFILE64_SOURCE" "-D_POSIX_SOURCE" "-o" "/builddir/ugdb-0.1.7/target/release/build/libz-sys-4d4fdfddee6ecc41/out/build/src/zlib/adler32.o" "-c" "src/zlib/adler32.c"
cargo:warning=cc1: sorry, unimplemented: 64-bit mode not compiled in
exit code: 1
running: "i686-linux-musl-gcc" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-m64" "-fstack-clash-protection" "-D_FORTIFY_SOURCE=2" "-O2" "-pipe" "-march=i686" "-I/usr/i686-linux-musl/usr/include" "-I" "src/zlib" "-fvisibility=hidden" "-DSTDC" "-D_LARGEFILE64_SOURCE" "-D_POSIX_SOURCE" "-o" "/builddir/ugdb-0.1.7/target/release/build/libz-sys-4d4fdfddee6ecc41/out/build/src/zlib/compress.o" "-c" "src/zlib/compress.c"
cargo:warning=cc1: sorry, unimplemented: 64-bit mode not compiled in
exit code: 1
--- stderr
error occurred: Command "i686-linux-musl-gcc" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-m64" "-fstack-clash-protection" "-D_FORTIFY_SOURCE=2" "-O2" "-pipe" "-march=i686" "-I/usr/i686-linux-musl/usr/include" "-I" "src/zlib" "-fvisibility=hidden" "-DSTDC" "-D_LARGEFILE64_SOURCE" "-D_POSIX_SOURCE" "-o" "/builddir/ugdb-0.1.7/target/release/build/libz-sys-4d4fdfddee6ecc41/out/build/src/zlib/adler32.o" "-c" "src/zlib/adler32.c" with args "i686-linux-musl-gcc" did not execute successfully (status code exit code: 1).
warning: build failed, waiting for other jobs to finish...
error: build failed
```
next prev parent reply other threads:[~2020-07-11 16:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-11 7:58 [PR PATCH] " ericonr
2020-07-11 10:50 ` [PR REVIEW] " q66
2020-07-11 15:08 ` ericonr
2020-07-11 15:09 ` ericonr
2020-07-11 15:35 ` [PR PATCH] [Updated] " ericonr
2020-07-11 15:36 ` [PR REVIEW] " ericonr
2020-07-11 15:58 ` q66
2020-07-11 15:59 ` q66
2020-07-11 16:17 ` ericonr [this message]
2020-07-11 22:30 ` [PR PATCH] [Updated] " ericonr
2020-07-12 13:25 ` ericonr
2020-07-15 21:40 ` [PR PATCH] [Updated] " ericonr
2020-07-15 21:45 ` ericonr
2020-07-17 9:51 ` [PR PATCH] [Merged]: New package: ugdb-0.1.8 Piraty
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=20200711161741.H29YiZNE6mSF1NNTcozORmdOQAuPuP6TVNZDsZv9pfY@z \
--to=ericonr@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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 NNTP newsgroup(s).