Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Holger Freyther <holger+oe@freyther.de>
To: openembedded-devel@lists.openembedded.org
Subject: perl-native build failures on Ubuntu 11.04 in a Linux Container
Date: Sat, 14 May 2011 12:36:04 +0200	[thread overview]
Message-ID: <4DCE5B14.3090106@freyther.de> (raw)

Hi,

does anyone else see build errors with perl-native? The linker line looks
innocent but libc and pthread symbols can not be resolved...



Log data follows:
| + cd
/home/ich/build/mips/tmp/work/x86_64-linux/perl-native-5.10.1-r10/perl-5.10.1
| + do_compile
| + base_do_compile
| + '[' -e Makefile -o -e makefile -o -e GNUmakefile ']'
| + oe_runmake
| + oenote make -e MAKEFLAGS=
| + echo NOTE: 'make -e MAKEFLAGS='
| NOTE: make -e MAKEFLAGS=
| + make -e MAKEFLAGS=
| gcc -L/home/ich/build/mips/tmp/sysroots/x86_64-linux/usr/lib
-Wl,-rpath-link,/home/ich/build/mips/tmp/sysroots/x86_64-linux/usr/lib
-Wl,-rpath,/home/ich/build/mips/tmp/sysroots/x86_64-linux/usr/lib -Wl,-O1
-fstack-protector -L/usr/local/lib -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 xsutils.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
| util.o: In function `Perl_safesysmalloc':
| util.c:(.text+0x4d8): undefined reference to `pthread_getspecific'
| util.o: In function `Perl_safesysrealloc':



             reply	other threads:[~2011-05-14 10:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-14 10:36 Holger Freyther [this message]
2011-05-14 11:09 ` perl-native build failures on Ubuntu 11.04 in a Linux Container Eric Bénard

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=4DCE5B14.3090106@freyther.de \
    --to=holger+oe@freyther.de \
    --cc=openembedded-devel@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