Compiling with just vp9 throws an error

[GoogleCodeExporter]

What is the expected behavior? What do you see instead?
./configure --enable-vp9 --disable-vp8
sudo make clean
sudo make

Throws a

    [CXX] test/external_frame_buffer_test.cc.o
test/external_frame_buffer_test.cc:236:22: error: no member named 
'kVP8TestVectors' in namespace 'libvpx_test'; did you mean 'kVP9TestVectors'?
  (void)libvpx_test::kVP8TestVectors;
        ~~~~~~~~~~~~~^~~~~~~~~~~~~~~
                     kVP9TestVectors
./test/test_vectors.h:30:20: note: 'kVP9TestVectors' declared here
extern const char *kVP9TestVectors[kNumVp9TestVectors];

What version are you using? On what operating system?
OSX

Can you reproduce using the vpxdec or vpxenc tools? What command line are
you using?
Can't compile with this config, so N/A.

Please provide any additional information below.
Compiling with both codecs works.  However, I was hoping to force only vp9 (or 
short of that, figure out how to get ffmpeg to play nice and request vp9)

Original issue reported on code.google.com by benh...@google.com on 17 Dec 2013 at 5:42

[GoogleCodeExporter]

./configure --enable-vp9  --enable-postproc --enable-vp9-postproc --enable-small
works just fine.  (With some warnings, but nothing bad)

Original comment by benh...@google.com on 17 Dec 2013 at 5:49

[GoogleCodeExporter]

Original comment by ya...@google.com on 9 Jan 2014 at 11:11

• Changed state: Started

[GoogleCodeExporter]

https://gerrit.chromium.org/gerrit/#/c/68163/

Original comment by fgalli...@google.com on 10 Jan 2014 at 6:10

• Changed state: Fixed

[GoogleCodeExporter]

Now compiles for me using original commands, thank you!
(now if I could just figure out how to tell brew's ffmpeg to pick up the recent 
compile of vp9, I'd be all set, but that isn't a bug)

Original comment by benh...@google.com on 10 Jan 2014 at 6:28

[GoogleCodeExporter]

Yeah I just build FFmpeg directly.

Original comment by fgalli...@google.com on 10 Jan 2014 at 6:34

• Changed state: Verified