public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Arttu V." <arttuv69@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] transcode 1.07 compile errors
Date: Wed, 4 Nov 2009 22:04:09 +0200	[thread overview]
Message-ID: <fecdbac60911041204m14623490o4a3e12ca3c78d8e5@mail.gmail.com> (raw)
In-Reply-To: <4AF1D842.4000107@myfairpoint.net>

On 11/4/09, sean <tech.junk@myfairpoint.net> wrote:
> Is anyone else having problems getting transcode to compile?

Just successfully re-emerged it on two mostly stable amd64's (although
they both have been using gcc 4.4 for quite some time). No problems.

> make[3]: Leaving directory
> `/var/tmp/portage/media-video/transcode-1.0.7/work/transcode-1.0.7/import'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory
> `/var/tmp/portage/media-video/transcode-1.0.7/work/transcode-1.0.7/import'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory
> `/var/tmp/portage/media-video/transcode-1.0.7/work/transcode-1.0.7'
> make: *** [all] Error 2
>  *
>  * ERROR: media-video/transcode-1.0.7 failed.
>  * Call stack:
>  *               ebuild.sh, line   49:  Called src_compile
>  *             environment, line 3123:  Called die
>  * The specific snippet of code:
>  *       emake all || die "emake failed"
>  *  The die message:
>  *   emake failed

What was the real error from make? It is somewhere there before these
lines -- not necessarily the first line before these, could be further
back (as you probably know).

-- 
Arttu V.



  reply	other threads:[~2009-11-04 20:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-04 19:38 [gentoo-amd64] transcode 1.07 compile errors sean
2009-11-04 20:04 ` Arttu V. [this message]
2009-11-08 12:18   ` sean

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=fecdbac60911041204m14623490o4a3e12ca3c78d8e5@mail.gmail.com \
    --to=arttuv69@gmail.com \
    --cc=gentoo-amd64@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