From: Johnnynator <Johnnynator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] chromium: create debug package on 64bit archs
Date: Tue, 05 May 2020 23:43:40 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21667@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 348 bytes --]
There is a new pull request by Johnnynator against master on the void-packages repository
https://github.com/Johnnynator/void-packages chromium
https://github.com/void-linux/void-packages/pull/21667
chromium: create debug package on 64bit archs
[ci skip]
A patch file from https://github.com/void-linux/void-packages/pull/21667.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-chromium-21667.patch --]
[-- Type: text/x-diff, Size: 1311 bytes --]
From c39418ed92f556dc4629ed53b37ba1f3cead46e7 Mon Sep 17 00:00:00 2001
From: John <me@johnnynator.dev>
Date: Tue, 5 May 2020 23:41:54 +0200
Subject: [PATCH] chromium: create debug package on 64bit archs
[ci skip]
---
srcpkgs/chromium/template | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/srcpkgs/chromium/template b/srcpkgs/chromium/template
index d25cd8fba99..24196eec067 100644
--- a/srcpkgs/chromium/template
+++ b/srcpkgs/chromium/template
@@ -12,7 +12,6 @@ distfiles="https://commondatastorage.googleapis.com/chromium-browser-official/${
checksum=ff74592f83ed91c082f746c6b0a3acf384bad91f170bd24548971c17f43046d3
lib32disabled=yes
-nodebug=yes
nopie=yes # contains tools that are not PIE, enables PIE itself
build_options="clang js_optimize vaapi"
@@ -44,6 +43,10 @@ case "${XBPS_TARGET_MACHINE}" in
i686) broken="what(): std::bad_alloc during linking" ;;
esac
+if [ "$XBPS_WORDSIZE" -eq 32 ]; then
+ nodebug=yes
+fi
+
post_extract() {
case "${XBPS_TARGET_MACHINE}" in
*-musl)
@@ -79,6 +82,10 @@ post_extract() {
do_configure() {
local system="" conf=()
export -n CFLAGS CXXFLAGS LDFLAGS
+ if [ -n "$XBPS_DEBUG_PKGS" ] && [ -z $nodebug ]; then
+ export CFLAGS=-g
+ export CXXFLAGS=-g
+ fi
if [ "$build_option_clang" ]; then
export CC=clang
next reply other threads:[~2020-05-05 21:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 21:43 Johnnynator [this message]
2020-05-06 16:27 ` anddam
2020-05-06 16:33 ` Johnnynator
2020-05-10 15:31 ` Johnnynator
2020-05-16 16:52 ` Johnnynator
2020-09-06 11:23 ` [PR PATCH] [Updated] " Johnnynator
2020-12-13 21:49 ` ericonr
2021-11-01 13:08 ` Johnnynator
2021-11-01 13:08 ` [PR PATCH] [Closed]: " Johnnynator
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21667@inbox.vuxu.org \
--to=johnnynator@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).