From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] undefined reference to '__stack_chk_fail'
Date: Tue, 16 Sep 2014 11:31:57 +0200 [thread overview]
Message-ID: <20140916093157.GC18865@pengutronix.de> (raw)
In-Reply-To: <CAJyGpipDWNVC+8R92E0ZRQ+Pq4cWtOUAk6KpuO8hXqQXA7MqxA@mail.gmail.com>
On Tue, Sep 16, 2014 at 10:45:55AM +0530, Arpit Jain wrote:
> Hi,
> I am trying to compile imx-bootlets-src-10.08.01 with ptxdist-2014.09.0,
> using OSELAS.Toolchain-2012.12.1, and it is giving a series of compilation
> errors all similar to these two
>
> *undefined reference to '__stack_chk_fail'*
> *undefined reference to '__stack_chk_guard'*
>
> A small research shows it is because of SSP package, which is protecting
> stack and not allowing some libraries to link with bootlets, but I am still
> not sure how to resolve this error.
>
> Any leads someone can provide?
The imx-bootlets are not part of upstream ptxdist so I'm guessing you have
some local rules for this.
You've probably enabled the stack protector in the platformconfig. PTXdist
will the inject the corresponding options into the build of all packages.
You need to blacklist the stack protector for the imx-bootlets.
search for _WRAPPER_BLACKLIST in the existing rules for examples. You need
to add TARGET_HARDEN_STACK to the blacklist.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2014-09-16 9:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 5:15 Arpit Jain
2014-09-16 9:31 ` Michael Olbrich [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=20140916093157.GC18865@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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