Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] revert GLIBC_MINOR bump in uClibc-ng 1.0 branch
Date: Mon, 14 Dec 2015 07:47:31 +0000	[thread overview]
Message-ID: <1450079251.4735.11.camel@synopsys.com> (raw)
In-Reply-To: <20151214060418.GA8958@waldemar-brodkorb.de>

Hi Waldemar,

On Mon, 2015-12-14 at 07:04 +0100, Waldemar Brodkorb wrote:
> Hi Thomas, Khem, Alexey,
> 
> recently Khem tried to use systemd with openembedded and uClibc-ng.
> Most of the needed stuff is ready and will be committed soon.
> 
> There is one open issue I want to discuss with you.
> The GLIBC_MINOR bump in commit
> 4a05ed87ceb946608100642121c32e642b58cd0d is breaking SSP detection
> in GCC. This was discovered in Buildroot and fixed.
> It seems there is a major problem to fix it in OpenEmbedded, so
> Khem is asking for revert of this commit for the next release.
> 
> What do you think about it?
> 
> Isn't the boost problem solved anyway in another way?

I think it is by that commit https://git.busybox.net/buildroot/commit/?id=b7aee38fe2d6409caa2b12d2b6a1e6acdf19014f

> May be we just learned what it means to bump this number and
> can revert it back to the old value. We should still try
> to get a patch into gcc to avoid any misdetection regarding
> SSP for the next major gcc release.

Well even though we may easily revert that GLIBC_MINOR bump
IMHO it's better cure problems in tools that improperly use
that define.

I mean if we revert that bump we will simply hide those issues
again and there's a chance these issues will never be fixed.

OTOH it's sad but from what I may see with hardware getting
more and more powerful uClibc is getting less and less used.
People switch to either full glibc or musl. In that light
we may want indeed just to solve our local problems keeping
external tools as they are.

In other words I don't really have any strong pro et contra.

-Alexey

      reply	other threads:[~2015-12-14  7:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-14  6:04 [Buildroot] revert GLIBC_MINOR bump in uClibc-ng 1.0 branch Waldemar Brodkorb
2015-12-14  7:47 ` Alexey Brodkin [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=1450079251.4735.11.camel@synopsys.com \
    --to=alexey.brodkin@synopsys.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox