From: Alan Mackenzie <acm@muc.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Can't emerge libreoffice-3.5.6.2
Date: Sun, 7 Oct 2012 15:18:42 +0000 [thread overview]
Message-ID: <20121007151842.GA9706@acm.acm> (raw)
Hi, Gentoo!
When I try to emerge libreoffice-3.5.6.2, I get the following failure:
#########################################################################
-----------------------------------------------------------------------
Oh dear - something failed during the build - sorry !
For more help with debugging build errors, please see the section in:
http://wiki.documentfoundation.org/Development
internal build errors:
ERROR: error 65280 occurred while making
/var/tmp/portage/app-office/libreoffice-3.5.6.2/work/libreoffice-core-3.5.6.2/sal/qa/sal
it seems that the error is inside 'sal', please re-run build
inside this module to isolate the error and/or test your fix:
-----------------------------------------------------------------------
/bin/sh
cd
/var/tmp/portage/app-office/libreoffice-3.5.6.2/work/libreoffice-core-3.5.6.2
source ./Env.Host.sh
cd sal
rm -Rf
/var/tmp/portage/app-office/libreoffice-3.5.6.2/work/libreoffice-core-3.5.6.2/sal/unxlngx6.pro
# optional module 'clean'
build
when the problem is isolated and fixed exit and re-run 'make' from the
top-level
make[1]: *** [build] Error 1
make[1]: Leaving directory
`/var/tmp/portage/app-office/libreoffice-3.5.6.2/work/libreoffice-core-3.5.6.2'
make: *** [source-env-and-recurse] Error 2
* ERROR: app-office/libreoffice-3.5.6.2 failed (compile phase):
* (no error message)
*
* Call stack:
* ebuild.sh, line 85: Called src_compile
* environment, line 8968: Called die
* The specific snippet of code:
* make build || die
*
* If you need support, post the output of `emerge --info
* '=app-office/libreoffice-3.5.6.2'`,
* the complete build log and the output of `emerge -pqv
* '=app-office/libreoffice-3.5.6.2'`.
!!! When you file a bug report, please include the following
information:
GENTOO_VM= CLASSPATH="" JAVA_HOME=""
JAVACFLAGS="" COMPILER=""
#########################################################################
. There is a bug report on this, allegedly, bug #393413, but this has
been open since last December.
Has anybody else encountered this, and is there a known workaround?
TIA!
--
Alan Mackenzie (Nuremberg, Germany).
reply other threads:[~2012-10-07 15:25 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=20121007151842.GA9706@acm.acm \
--to=acm@muc.de \
--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