Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <pb@pbcl.net>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: perl build failure
Date: Tue, 24 May 2011 13:32:29 +0100	[thread overview]
Message-ID: <1306240349.2525.167.camel@phil-desktop> (raw)

My eglibc builds are failing in perl with:

| ccache i586-oe-linux-gcc -march=i586 --sysroot=/home/pb/oe/build-meta/tmp-eglibc/sysroots/qemux86 -Wl,-O1  -Wl,--as-needed -o miniperl \
| 	      gv.o toke.o perly.o pad.o regcomp.o dump.o util.o mg.o reentr.o mro.o hv.o av.o run.o pp_hot.o sv.o pp.o scope.o pp_ctl.o pp_sys.o doop.o doio.o regexec.o utf8.o taint.o deb.o universal.o globals.o perlio.o perlapi.o numeric.o mathoms.o locale.o pp_pack.o pp_sort.o   \
| 	    miniperlmain.o opmini.o perlmini.o -lnsl -ldl -lm -lcrypt -lutil -lpthread -lc
| toke.o: In function `S_scan_str':
| /home/pb/oe/build-meta/tmp-eglibc/work/i586-oe-linux/perl-5.12.3-r0/perl-5.12.3/toke.c:12609: undefined reference to `__stack_chk_guard'

What seems to be happening is that perl is adding -fstack-protector to
CFLAGS but then somehow forgetting to include it during final link of
miniperl.

I see that -fstack-protector is being forced off altogether for uclibc
builds which presumably is why the problem doesn't occur there.  But I
am somewhat baffled as to why this is apparently not happening for
anybody else with eglibc.

Anyway, does anybody have an idea what is going wrong here?  I had a
quick look at it but the perl cross-compilation process seems to be
slightly baroque and I couldn't immediately figure out how the various
makefiles and config fragments were meant to be interacting.

p.





                 reply	other threads:[~2011-05-24 12:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1306240349.2525.167.camel@phil-desktop \
    --to=pb@pbcl.net \
    --cc=openembedded-core@lists.openembedded.org \
    /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