All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Patchwork cleanup week #24
Date: Wed, 22 Jun 2016 22:57:38 +0200	[thread overview]
Message-ID: <f767a47d-6908-ba5c-5884-60b572503a27@mind.be> (raw)
In-Reply-To: <20160615220634.67eb8fa9@free-electrons.com>

On 15-06-16 22:06, Thomas Petazzoni wrote:
>  3. toolchain-wrapper: prevent use of unsupported -fstack-protector*
>     http://patchwork.ozlabs.org/patch/545315/
> 
>     This patch proposes to make the toolchain wrapper fail immediately
>     when -fstack-protector is passed to gcc, but SSP support is not
>     available. This helps with some packages that assume that compiling
>     with -fstack-protector is enough to determine if SSP support is
>     available, while in several cases, doing a link test is necessary.
> 
>     I personally don't really like this change, as I believe it's
>     adding even more sorcery to our toolchain wrapper. Instead, the
>     problematic upstream packages should be fixed. Plus, at the time,
>     we had a few packages in this situation, but nowadays, I don't
>     think we have build failures due to this.
> 
>     So, my proposal would be to reject this patch.

 I originally advocated for this patch (see
https://patchwork.ozlabs.org/patch/543115/ ). My reasoning was that it's very
hard to write a reliable test for stackprotector, because optimisations can
easily elide so much from the test that the stackprotector disappears.
Therefore, a test that works fine for the current compiler may break down with
future gcc releases.

 Also, I prefer to be able to resolve entire classes of build problems rather
than patching individual packages. The toolchain wrapper is a clear example of
this: it only exists because packages don't reliable handle CFLAGS, otherwise we
could just pass --sysroot etc. in CFLAGS.

 On the other hand, for this particular case, autobuilder errors will appear for
failing packages, so at least it's not a hidden issue.

 Regards,
 Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

  parent reply	other threads:[~2016-06-22 20:57 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-15 20:06 [Buildroot] Patchwork cleanup week #24 Thomas Petazzoni
     [not found] ` <CAJsd3zJkzAUJhvBPJ9hdQ60YmjSjuB7sahptmLFx6-1V70fLAg@mail.gmail.com>
2016-06-15 21:18   ` Thomas Petazzoni
2016-06-16  7:18 ` Thomas De Schampheleire
2016-06-16  7:32   ` Thomas Petazzoni
2016-06-16  9:52     ` Thomas De Schampheleire
2016-06-16  9:56       ` Thomas Petazzoni
2016-06-16 17:30         ` Yann E. MORIN
2016-06-16 17:23       ` Yann E. MORIN
2016-06-18 20:56         ` Thomas Petazzoni
2016-06-18 14:14 ` Romain Naour
     [not found] ` <4209f432-0fbd-8d44-7194-c99829f66e2e@smile.fr>
2016-06-22  5:45   ` Alexey Brodkin
2016-06-24  7:24     ` Vlad Zakharov
2016-06-24  7:32       ` Thomas Petazzoni
2016-06-24  9:13         ` Alexey Brodkin
2016-06-24  9:15           ` Thomas Petazzoni
2016-06-24  9:17             ` Alexey Brodkin
2016-07-01  7:59       ` Romain Naour
2016-06-22  6:14 ` Cam Hutchison
2016-06-30 23:51   ` Cam Hutchison
2016-07-01  7:01     ` Thomas Petazzoni
2016-06-22 20:57 ` Arnout Vandecappelle [this message]
2016-06-26 11:07 ` Jörg Krause
2016-06-26 12:53   ` Thomas Petazzoni
2016-07-24 20:23 ` Thomas Petazzoni

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=f767a47d-6908-ba5c-5884-60b572503a27@mind.be \
    --to=arnout@mind.be \
    --cc=buildroot@busybox.net \
    /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.