All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 2995] -fstack-protector-all causes ssh to SIGSEGV
Date: Mon, 20 Dec 2010 15:56:02 +0000 (UTC)	[thread overview]
Message-ID: <20101220155602.264928DEB5@busybox.osuosl.org> (raw)
In-Reply-To: <bug-2995-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=2995

Peter Korsgaard <jacmet@uclibc.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED

--- Comment #1 from Peter Korsgaard <jacmet@uclibc.org>  ---
Do you have "Enable stack protection support" (BR2_TOOLCHAIN_BUILDROOT_USE_SSP)
enabled? If yes, do things work if you disable that and do a fresh rebuild
(make clean; make)

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

  reply	other threads:[~2010-12-20 15:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-20 15:43 [Buildroot] [Bug 2995] New: -fstack-protector-all causes ssh to SIGSEGV bugzilla at busybox.net
2010-12-20 15:56 ` bugzilla at busybox.net [this message]
2010-12-20 16:52 ` [Buildroot] [Bug 2995] " bugzilla at busybox.net
2010-12-20 16:56 ` bugzilla at busybox.net
2010-12-20 21:01 ` bugzilla at busybox.net
2011-03-02 13:51 ` bugzilla at busybox.net
2011-03-02 14:35 ` bugzilla at busybox.net
2011-09-18 10:18 ` bugzilla at busybox.net
2013-11-28 17:15 ` bugzilla at busybox.net

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=20101220155602.264928DEB5@busybox.osuosl.org \
    --to=bugzilla@busybox.net \
    --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.