the ebuild's using local myconf="${EXTRA_ECONF}" while EXTRA_ECONF is already passed to econf which leads to nice errors, for example: loki ~ # EXTRA_ECONF="-q" emerge ffmpeg >>> Verifying ebuild Manifests... >>> Emerging (1 of 1) media-video/ffmpeg-0.4.9_p20070616-r1 to / * Applying ffmpeg-libdir-2007.patch ... [ ok ] * Applying ffmpeg-shared-gcc4.1.patch ... [ ok ] Unknown option "-q". See ./configure --help for available options. * * ERROR: media-video/ffmpeg-0.4.9_p20070616-r1 failed. removing said line from the ebuild fixes this and configure stays quiet (so -q is actually valid, configure just doesn't like it twice)
Well, ffmpeg doesn't use autotools and its configure bails out on unknown option, so I'd say it's your fault for having fed it with an invalid option :) (note that the configure is quiet regardless of using -q or not) From my pov, the bug is invalid. What can be questionned is why using extra_econf for a non autotoolized configure, but I'm sure Luca has a good reason for that.
(In reply to comment #1) > Well, ffmpeg doesn't use autotools and its configure bails out on unknown > option, so I'd say it's your fault for having fed it with an invalid option :) > (note that the configure is quiet regardless of using -q or not) > > From my pov, the bug is invalid. What can be questionned is why using > extra_econf for a non autotoolized configure, but I'm sure Luca has a good > reason for that. closing as invalid then
