From: Dirk Heinrichs <dirk.heinrichs.ext@nsn.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] openoffice emerge failing
Date: Thu, 20 Nov 2008 16:11:06 +0100 [thread overview]
Message-ID: <200811201611.20235.dirk.heinrichs.ext@nsn.com> (raw)
In-Reply-To: <20081120145153.GA31497@anton.digitaltorque.ca>
[-- Attachment #1: Type: text/plain, Size: 1848 bytes --]
Am Donnerstag 20 November 2008 15:51:54 schrieb ext Michael P. Soulier:
> On 20/11/08 Qian Qiao said:
> > That still doesn't show where the error occured, try to dig out the
> > actual error in build.log, or attach it.
>
> http://home.digitaltorque.ca/build.log.gz
So you should add this part of it to the bug you've already created:
/var/tmp/portage/app-office/openoffice-3.0.0/work/ooo/build/ooo300-
m9/chart2/source/controller/dialogs
Running processes: 2
------------------------------
Making: ../../../unxlngi6.pro/slo/ObjectNameProvider.obj
Making: ../../../unxlngi6.pro/slo/DataSeriesPointWrapper.obj
Making: ../../../unxlngi6.pro/slo/TimerTriggeredControllerLock.obj
Making: ../../../unxlngi6.pro/slo/ChangingResource.obj
Making: ../../../unxlngi6.pro/slo/DataBrowser.obj
Making: ../../../unxlngi6.pro/slo/DiagramWrapper.obj
Making: ../../../unxlngi6.pro/slo/DataBrowserModel.obj
Making: ../../../unxlngi6.pro/slo/GridWrapper.obj
Making: ../../../unxlngi6.pro/slo/DialogModel.obj
Making: ../../../unxlngi6.pro/slo/LegendWrapper.obj
{standard input}: Assembler messages:
{standard input}:1013: Error: invalid character (0x16) in operand 1
{standard input}:9931: Error: suffix or operands invalid for `push'
{standard input}:9931: Error: junk at end of line, first unrecognized
character is `%'
dmake: Error code 1, while making
'../../../unxlngi6.pro/slo/LegendWrapper.obj'
Running processes: 1
Bye...
Dirk
BTW: grep -i error the_log_file would have helped a lot.
--
Dirk Heinrichs | Tel: +49 (0)162 234 3408
Configuration Manager | Fax: +49 (0)211 47068 111
Capgemini Deutschland | Mail: dirk.heinrichs@capgemini.com
Wanheimerstraße 68 | Web: http://www.capgemini.com
D-40468 Düsseldorf | ICQ#: 110037733
GPG Public Key C2E467BB | Keyserver: wwwkeys.pgp.net
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-11-20 15:11 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-20 12:39 [gentoo-user] openoffice emerge failing Michael P. Soulier
2008-11-20 12:42 ` Qian Qiao
2008-11-20 12:48 ` Michael P. Soulier
2008-11-20 12:49 ` deface
2008-11-20 12:59 ` Dirk Heinrichs
2008-11-20 13:10 ` Florian Philipp
2008-11-21 0:19 ` Iain Buchanan
2008-11-21 0:26 ` Paul Hartman
2008-11-21 6:51 ` Dirk Heinrichs
2008-11-21 6:52 ` Daniel Pielmeier
2008-11-21 15:25 ` Paul Hartman
2008-11-20 13:14 ` Dirk Uys
2008-11-20 13:24 ` Dirk Heinrichs
2008-11-20 20:22 ` Dale
2008-11-20 13:37 ` Michael P. Soulier
2008-11-20 14:11 ` Philip Webb
2008-11-20 12:55 ` Qian Qiao
2008-11-20 14:51 ` Michael P. Soulier
2008-11-20 15:11 ` Dirk Heinrichs [this message]
2008-11-20 14:29 ` Redouane Boumghar
2008-11-20 14:54 ` Michael P. Soulier
2008-11-21 14:17 ` Michael P. Soulier
2008-11-21 17:51 ` Joshua Murphy
2008-11-23 9:13 ` Jorge Peixoto de Morais Neto
2008-11-21 0:27 ` Iain Buchanan
2008-11-21 9:11 ` Redouane Boumghar
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=200811201611.20235.dirk.heinrichs.ext@nsn.com \
--to=dirk.heinrichs.ext@nsn.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