Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Waldemar Brodkorb <wbx@openadk.org>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/gcc: fix missing .note.GNU-stack section
Date: Sun, 17 Sep 2023 08:30:56 +0200	[thread overview]
Message-ID: <87v8c9tiov.fsf@48ers.dk> (raw)
In-Reply-To: <ZPQ2zZ1dgo6K2mdO@waldemar-brodkorb.de> (Waldemar Brodkorb's message of "Sun, 3 Sep 2023 09:33:33 +0200")

>>>>> "Waldemar" == Waldemar Brodkorb <wbx@openadk.org> writes:

 > Shellinabox configure fails to detect ptsname_r, because of the following warning
 > binutils 2.39+ emits:
 > ld: warning: crtend.o: missing .note.GNU-stack section implies executable stack
 > ld: NOTE: This behaviour is deprecated and will be removed in a future version of the linker

 > Then the build errors out with:
 > shellinabox/launcher.c:772:12: error: static declaration of 'ptsname_r' follows non-static declaration

 > The same issue exist for cairo 1.16.0 and the detection of pthreads.

 > Fixes:
 >  - http://autobuild.buildroot.net/results/3e4/3e478d22e820703ddfd11d1491e631ef8ed6b29b
 >  - http://autobuild.buildroot.net/results/f60/f602ea17d5938a5beb81d07e13de75ba41d5f6a1

 > Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>

Committed to 2023.08.x, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2023-09-17  6:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-03  7:33 [Buildroot] [PATCH] package/gcc: fix missing .note.GNU-stack section Waldemar Brodkorb
2023-09-11 20:57 ` Thomas Petazzoni via buildroot
2023-09-17  6:30 ` Peter Korsgaard [this message]

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=87v8c9tiov.fsf@48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=wbx@openadk.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