From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] host-lua: fix bug #5354
Date: Sat, 17 Nov 2012 20:48:28 +0100 [thread overview]
Message-ID: <87boewt3hv.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1353146744-13529-1-git-send-email-francois.perrad@gadz.org> (Francois Perrad's message of "Sat, 17 Nov 2012 11:05:43 +0100")
>>>>> "Francois" == Francois Perrad <fperrad@gmail.com> writes:
Francois> see https://bugs.busybox.net/show_bug.cgi?id=5354
Thanks, but I don't get the problem in the first place. Lua links
lua/luac using gcc, so why doesn't it pick up the stack protection bits?
Francois> Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
Francois> ---
Francois> package/lua/lua.mk | 2 +-
Francois> 1 file changed, 1 insertion(+), 1 deletion(-)
Francois> diff --git a/package/lua/lua.mk b/package/lua/lua.mk
Francois> index 9e0d387..3ce9867 100644
Francois> --- a/package/lua/lua.mk
Francois> +++ b/package/lua/lua.mk
Francois> @@ -24,7 +24,7 @@ endif
Francois> # We never want to have host-readline and host-ncurses as dependencies
Francois> # of host-lua.
Francois> HOST_LUA_DEPENDENCIES =
Francois> -HOST_LUA_CFLAGS = -Wall -fPIC -DLUA_USE_DLOPEN -DLUA_USE_POSIX
Francois> +HOST_LUA_CFLAGS = -Wall -fPIC -fno-stack-protector -DLUA_USE_DLOPEN -DLUA_USE_POSIX
Francois> HOST_LUA_MYLIBS = -ldl
Francois> define LUA_BUILD_CMDS
Francois> --
Francois> 1.7.9.5
Francois> _______________________________________________
Francois> buildroot mailing list
Francois> buildroot at busybox.net
Francois> http://lists.busybox.net/mailman/listinfo/buildroot
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2012-11-17 19:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-17 10:05 [Buildroot] [PATCH] host-lua: fix bug #5354 Francois Perrad
2012-11-17 19:48 ` Peter Korsgaard [this message]
2012-11-17 19:56 ` Peter Korsgaard
2012-11-17 20:21 ` Gustavo Zacarias
2012-11-17 21:43 ` Peter Korsgaard
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=87boewt3hv.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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