From: Li <fender0107401@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Failed to emerge sys-devel/libperl-5.8.8-r2
Date: Wed, 13 Jan 2010 20:01:50 +0800 [thread overview]
Message-ID: <20100113120150.GA11595@PC-686.Workstation> (raw)
In-Reply-To: <201001131135.44829.alan.mckinnon@gmail.com>
On Wed, Jan 13, 2010 at 11:35:44AM +0200, Alan McKinnon wrote:
> On Wednesday 13 January 2010 11:15:09 Li wrote:
> > Hi all:
> > >>> Failed to emerge sys-devel/libperl-5.8.8-r2, Log file:
> > >>>
> > >>> '/var/tmp/portage/sys-devel/libperl-5.8.8-r2/temp/build.log'
> >
> > * Messages for package sys-devel/libperl-5.8.8-r2:
> >
> > *
> > * ERROR: sys-devel/libperl-5.8.8-r2 failed.
> >pecific snippet of code:
* Call stack:
> > * ebuild.sh, line 49: Called src_compile
> > * environment, line 2719: Called die
> > * The specific snippet of code:
> > * emake -j1 -f Makefile LDFLAGS="${LDFLAGS}"
> > * LIBPERL=${LIBPERL} ${LIBPERL} || die "Unable to make
> > * libperl$(get_libname)";
>kefile LDFLAGS="${LDFLAGS}" LIBPERL=${LIBPERL} ${LIBPERL} || die
>"Unable to make libperl$(get_libname)";
> * sage:
The die message:
> > * Unable to make libperl.so
> > *
> > * If you need support, post the topmost build error, and the
> ^^^^^^^^^^^^^^^^^^^
>
> Please do this step. That is where the actual error message is.
>
> You need to eyeball
> /var/tmp/portage/sys-devel/libperl-5.8.8-r2/temp/build.log
> to find the FIRST error message, then paste the relevant bits and post them
> here.
>
>
>
> --
> alan dot mckinnon at gmail dot com
CCCMD = x86_64-pc-linux-gnu-gcc -DPERL_CORE -c -fno-strict-aliasing -pipe -Wdeclaration-after-statement -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/include/gdbm -march=native -O2 -pipe -Wall
x86_64-pc-linux-gnu-gcc -march=native -O2 -pipe -o libperl.so.1.5.8 -shared -L/usr/local/lib64 -Wl,-O1 perl.o gv.o toke.o perly.o op.o pad.o regcomp.o dump.o util.o mg.o reentr.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 locale.o pp_pack.o pp_sort.o -lnsl -ldl -lm -lcrypt -lutil -lc -Wl,-soname -Wl,libperl.so.`echo libperl.so.1.5.8 | cut -d. -f3`
perlio.o: file not recognized: File format not recognized
collect2: ld returned 1 exit status
make: *** [libperl.so.1.5.8] Error 1
*
* ERROR: sys-devel/libperl-5.8.8-r2 failed.
* Call stack:
* ebuild.sh, line 49: Called src_compile
* environment, line 2719: Called die
* The specific snippet of code:
* emake -j1 -f Makefile LDFLAGS="${LDFLAGS}"
* LIBPERL=${LIBPERL} ${LIBPERL} || die "Unable to make
* libperl$(get_libname)";
* The die message:
* Unable to make libperl.so
*
* If you need support, post the topmost build error, and the
* call stack if relevant.
* A complete build log is located at
* '/var/tmp/portage/sys-devel/libperl-5.8.8-r2/temp/build.log'.
* The ebuild environment file is located at
* '/var/tmp/portage/sys-devel/libperl-5.8.8-r2/temp/environment'.
I think the first error is "perlio.o: file not recognized: File format
not recognized"
fender0107401
next prev parent reply other threads:[~2010-01-13 12:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 9:15 [gentoo-user] Failed to emerge sys-devel/libperl-5.8.8-r2 Li
2010-01-13 9:35 ` Alan McKinnon
2010-01-13 12:01 ` Li [this message]
2010-01-14 1:07 ` [gentoo-user] " walt
2010-01-14 2:39 ` Li
2010-01-14 5:00 ` Li
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=20100113120150.GA11595@PC-686.Workstation \
--to=fender0107401@gmail.com \
--cc=gentoo-user@lists.gentoo.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