All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>, buildroot@buildroot.org
Cc: Pascal Huerst <pascal.huerst@gmail.com>,
	Anisse Astier <anisse@astier.eu>
Subject: Re: [Buildroot] [PATCH 1/1] package/google-breakpad: fix build with glibc >= 2.33
Date: Sun, 26 Sep 2021 21:49:47 +0200	[thread overview]
Message-ID: <458809e2-a345-3f44-dcbd-f675019b6e5a@mind.be> (raw)
In-Reply-To: <20210926083501.3514060-1-fontaine.fabrice@gmail.com>



On 26/09/2021 10:35, Fabrice Fontaine wrote:
> Fix the following build failure with glibc >= 2.33:
> 
> src/client/linux/handler/exception_handler.cc: In function 'void google_breakpad::{anonymous}::InstallAlternateStackLocked()':
> src/client/linux/handler/exception_handler.cc:147:49: error: no matching function for call to 'max(int, long int)'
>    147 |   static const unsigned kSigStackSize = std::max(16384, SIGSTKSZ);
>        |                                         ~~~~~~~~^~~~~~~~~~~~~~~~~
> 
> Fixes:
>   - http://autobuild.buildroot.org/results/61a89fa954db16a7b5b9fcee55c545e489f8d489
> 
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>

  Applied to master, thanks.

  Regards,
  Arnout

> ---
>   .../0004-Fix-for-non-constant-SIGSTKSZ.patch  | 34 +++++++++++++++++++
>   1 file changed, 34 insertions(+)
>   create mode 100644 package/google-breakpad/0004-Fix-for-non-constant-SIGSTKSZ.patch
> 
> diff --git a/package/google-breakpad/0004-Fix-for-non-constant-SIGSTKSZ.patch b/package/google-breakpad/0004-Fix-for-non-constant-SIGSTKSZ.patch
> new file mode 100644
> index 0000000000..4291216c61
> --- /dev/null
> +++ b/package/google-breakpad/0004-Fix-for-non-constant-SIGSTKSZ.patch
> @@ -0,0 +1,34 @@
> +From 4a332d01186b09a9d46390b845024d914d9149cb Mon Sep 17 00:00:00 2001
> +From: Michel Alexandre Salim <michel@michel-slm.name>
> +Date: Sun, 21 Mar 2021 13:17:00 -0700
> +Subject: [PATCH] Fix for non-constant SIGSTKSZ
> +
> +On glibc > 2.33, `SIGSTKSZ` might not be constant (in which case
> +it expands to a call to `sysconf` which returns a `long int`); see
> +http://sourceware-org.1504.n7.nabble.com/PATCH-sysconf-Add-SC-MINSIGSTKSZ-SC-SIGSTKSZ-BZ-20305-td650948.html
> +
> +Cast the two arguments to `max` to `unsigned`, which is the type of the variable
> +we're storing the result in anyway, so that it works both with the old-style constant
> +`SIGSTKSZ` and the new configurable one.
> +
> +Signed-off-by: Michel Alexandre Salim <michel@michel-slm.name>
> +Change-Id: I3d87048561a87c6b9fcdbb14b3d53dd45b0a00f0
> +
> +[Retrieved from:
> +https://chromium-review.googlesource.com/c/breakpad/breakpad/+/2776379]
> +Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> +---
> +
> +diff --git a/src/client/linux/handler/exception_handler.cc b/src/client/linux/handler/exception_handler.cc
> +index ca353c4..3788829 100644
> +--- a/src/client/linux/handler/exception_handler.cc
> ++++ b/src/client/linux/handler/exception_handler.cc
> +@@ -138,7 +138,7 @@
> +   // SIGSTKSZ may be too small to prevent the signal handlers from overrunning
> +   // the alternative stack. Ensure that the size of the alternative stack is
> +   // large enough.
> +-  static const unsigned kSigStackSize = std::max(16384, SIGSTKSZ);
> ++  static const unsigned kSigStackSize = std::max((unsigned) 16384, (unsigned) SIGSTKSZ);
> +
> +   // Only set an alternative stack if there isn't already one, or if the current
> +   // one is too small.
> 
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2021-09-26 19:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-26  8:35 [Buildroot] [PATCH 1/1] package/google-breakpad: fix build with glibc >= 2.33 Fabrice Fontaine
2021-09-26 19:49 ` Arnout Vandecappelle [this message]
2021-10-05 15:24 ` Peter Korsgaard

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=458809e2-a345-3f44-dcbd-f675019b6e5a@mind.be \
    --to=arnout@mind.be \
    --cc=anisse@astier.eu \
    --cc=buildroot@buildroot.org \
    --cc=fontaine.fabrice@gmail.com \
    --cc=pascal.huerst@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.