Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] mosh: fix build with the Codescape IMG toolchain
Date: Wed, 6 Apr 2016 01:23:55 +0200	[thread overview]
Message-ID: <5704490B.3020906@mind.be> (raw)
In-Reply-To: <57044575.7030307@mind.be>

On 04/06/16 01:08, Arnout Vandecappelle wrote:
> On 04/05/16 23:47, Arnout Vandecappelle wrote:
>> On 04/05/16 20:03, Baruch Siach wrote:
>>> The Codescape IMG toolchain does not provide the ssp library even though it's
>>> a glibc toolchain, and thus selects BR2_TOOLCHAIN_HAS_SSP. Add a patch that
>>> changes the compile test for -fstack-protector-all to a build test that
>>> correctly fails when ssp is missing.
>>>
>>> This makes the seeding of ssp related configure variables unnecessary.
>>
>>   So, this fixes the issue for mosh, but not for libpam-tacplus, powerpc-utils,
>> psmisc, ruby, sox, and stunnel...
>>
>>   Wouldn't it be better to fix BR2_TOOLCHAIN_HAS_SSP itself instead? Otherwise
>> there isn't much point in having this symbol... So it shouldn't be selected by
>> glibc/musl itself, but by the individual external toolchains. Cfr. the previous
>> discussion for sox [1].
>
>   And actually, Vicente already provided a patch for that:
> http://patchwork.ozlabs.org/patch/597701/

  Oh, and there is this one as well:

http://patchwork.ozlabs.org/patch/545315/

>
>   It is at place fifty-something of my patches-to-review list :-)

... at place sixty-something :-)

  Regards,
  Arnout

>
>   Regards,
>   Arnout
>
>>
>>   That said, it would of course be a great idea to upstream the patch to mosh so
>> we can remove our workaround at some point.
>>
>>   Regards,
>>   Arnout
>>
>> [1] http://patchwork.ozlabs.org/patch/590047/
>>
>>>
>>> Signed-off-by: Baruch Siach<baruch@tkos.co.il>
>>> ---
>>>   ...ure.ac-link-test-for-fstack-protector-all.patch | 33 ++++++++++++++++++++++
>>>   package/mosh/mosh.mk                               | 11 ++------
>>>   2 files changed, 35 insertions(+), 9 deletions(-)
>>>   create mode 100644
>>> package/mosh/0001-configure.ac-link-test-for-fstack-protector-all.patch
>>
>>
>
>


-- 
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

  reply	other threads:[~2016-04-05 23:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-05 18:03 [Buildroot] [PATCH] mosh: fix build with the Codescape IMG toolchain Baruch Siach
2016-04-05 20:25 ` Baruch Siach
2016-04-05 21:47 ` Arnout Vandecappelle
2016-04-05 23:08   ` Arnout Vandecappelle
2016-04-05 23:23     ` Arnout Vandecappelle [this message]
2016-04-06  3:27   ` Baruch Siach

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=5704490B.3020906@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox