public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Liviu Andronic" <landronimirc@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] AbiWord 2.6.4 build failure
Date: Sun, 19 Oct 2008 23:36:27 +0200	[thread overview]
Message-ID: <68b1e2610810191436q76e9e327yf4293a13a5f45407@mail.gmail.com> (raw)
In-Reply-To: <68b1e2610810191418q3ef850d6oe093235b4ca85dff@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1698 bytes --]

On 10/19/08, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
>>  * If you need support, post the topmost build error, and the call stack
>> if
>> relevant.
>                                    ^^^^^^^
>
> You did not do this. You posted the bottommost error.
>
Well, the error message essentially didn't change from my first posting, so
the second time I posted only the diff. Below is the topmost error; if not,
please tell me how you would expect it to be.

Thank you,
Liviu

################
make[4]: Leaving directory
`/var/tmp/portage/app-office/abiword-2.6.4/work/abiword-2.6.4/src/af/xap/xp'
Making all in unix
make[4]: Entering directory
`/var/tmp/portage/app-office/abiword-2.6.4/work/abiword-2.6.4/src/af/xap/unix'
GNUmakefile:964: *** mixed implicit and normal rules.  Stop.
make[4]: Leaving directory
`/var/tmp/portage/app-office/abiword-2.6.4/work/abiword-2.6.4/src/af/xap/unix'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory
`/var/tmp/portage/app-office/abiword-2.6.4/work/abiword-2.6.4/src/af/xap'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/var/tmp/portage/app-office/abiword-2.6.4/work/abiword-2.6.4/src/af'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/var/tmp/portage/app-office/abiword-2.6.4/work/abiword-2.6.4/src'
make: *** [all-recursive] Error 1
 *
 * ERROR: app-office/abiword-2.6.4 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 3298:  Called gnome2_src_compile
 *             environment, line 2311:  Called die
 * The specific snippet of code:
 *       emake || die "compile failure"
 *  The die message:
 *   compile failure
#################

[-- Attachment #2: Type: text/html, Size: 2462 bytes --]

  reply	other threads:[~2008-10-19 21:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-18 18:20 [gentoo-user] AbiWord 2.6.4 build failure Liviu Andronic
2008-10-18 18:34 ` Fabrice Delliaux
2008-10-18 18:56   ` Liviu Andronic
2008-10-19 10:59     ` Arttu V.
2008-10-19 11:08       ` Alan McKinnon
2008-10-19 14:51       ` Liviu Andronic
2008-10-19 15:20         ` Daniel Pielmeier
2008-10-19 15:25         ` Alan McKinnon
2008-10-19 21:18           ` Liviu Andronic
2008-10-19 21:36             ` Liviu Andronic [this message]
2008-10-20 23:17     ` Walter Dnes
2008-10-21  9:21       ` Liviu Andronic
2008-10-21 10:23         ` Fabrice Delliaux
2008-10-22 10:09           ` Liviu Andronic
2008-10-22 12:24             ` Fabrice Delliaux
2008-10-22 18:45               ` Liviu Andronic
2008-10-22 20:25                 ` Fabrice Delliaux
2008-10-23 18:09                   ` Liviu Andronic

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=68b1e2610810191436q76e9e327yf4293a13a5f45407@mail.gmail.com \
    --to=landronimirc@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