public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Vibhav Garg <vgarg@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] (media-video) ffmpeg and a52dec
Date: Wed, 20 Apr 2005 16:34:11 -0500	[thread overview]
Message-ID: <4266CAD3.6030809@gentoo.org> (raw)
In-Reply-To: <20050418205517.GH13272@mustard.flatmonk.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I am getting the following error while emerging
ffmpeg-0.4.9_p20050226-r3 on amd64

xvidff.c:682: error: `XVID_VOP_INTER4V' undeclared (first use in this
function)
xvidff.c:683: error: `XVID_VOP_HQACPRED' undeclared (first use in this
function)xvidff.c:685: error: `XVID_VOL_GMC' undeclared (first use in
this function)
xvidff.c: At top level:
xvidff.c:701: error: parse error before "xvid_plg_data_t"
xvidff.c: In function `xvid_ff_2pass_after':
xvidff.c:702: error: `ref' undeclared (first use in this function)
xvidff.c:711: error: `param' undeclared (first use in this function)
xvidff.c: In function `xvid_ff_2pass':
xvidff.c:738: error: `XVID_PLG_INFO' undeclared (first use in this function)
xvidff.c:739: error: `XVID_PLG_FRAME' undeclared (first use in this
function)
xvidff.c:742: error: `XVID_PLG_BEFORE' undeclared (first use in this
function)
xvidff.c:745: error: `XVID_PLG_CREATE' undeclared (first use in this
function)
xvidff.c:748: error: `XVID_PLG_AFTER' undeclared (first use in this
function)
xvidff.c:751: error: `XVID_PLG_DESTROY' undeclared (first use in this
function)
make[1]: *** [xvidff.o] Error 1
make[1]: Leaving directory
`/var/tmp/portage/ffmpeg-0.4.9_p20050226-r3/work/ffmpeg-0.4.9-p20050226-static/libavcodec'
make: *** [lib] Error 2

Vibhav
Aron Griffis wrote:
> Presently vlc doesn't merge (given the right USE flags) because of
> bugs in ffmpeg when built with gcc-3.4 (bug 88472).  Marking the newer
> ffmpeg stable relies on marking a52dec-0.7.4-r4 stable as well.  From
> what I can see in bgo, this seems like a reasonable thing to do...
> 
> Both of these packages appear to have been most recently maintained by
> Chris White, and in fact bug 84670 is a tracer bug in which he was
> recording all the things that would be fixed by marking the packages
> stable.
> 
> Does somebody from the media-video team mind marking those packages
> stable and working on the list of bugs that Chris White was previously
> looking after?
> 
> Regards,
> Aron
> 
> --
> Aron Griffis
> Gentoo Linux Developer
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCZsrRiriTCkdDSX4RAgXOAJ0VVG+fWbyjM3y67IJEHw6mdeiEmACg0bA3
Vyu/z1omDYbAuhFPCeZ2hx8=
=gZK3
-----END PGP SIGNATURE-----
-- 
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2005-04-20 21:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-18 20:55 [gentoo-dev] (media-video) ffmpeg and a52dec Aron Griffis
2005-04-18 21:26 ` Aron Griffis
2005-04-19  0:34   ` Diego 'Flameeyes' Pettenò
2005-04-19 11:40     ` Luca Barbato
2005-04-18 21:29 ` Diego 'Flameeyes' Pettenò
2005-04-18 21:35   ` Aron Griffis
2005-04-19  1:32   ` Lina Pezzella
2005-04-20 21:34 ` Vibhav Garg [this message]
2005-04-20 22:20   ` Aron Griffis

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=4266CAD3.6030809@gentoo.org \
    --to=vgarg@gentoo.org \
    --cc=gentoo-dev@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