>>/usr/lib64/libva-0.31.0.5.so.1: could not read symbols: Invalid operation
> It's a different command failing, that one has -lva-x11
> and -lva-glx but not -lva . With all three, the command succeeds. D'oh!
Please remember to file a bug report against binutils. You've identified
a reproducible
On Mon, 2010-03-15 at 19:24 -0700, Adam Williamson wrote:
> On Mon, 2010-03-15 at 18:31 -0700, Roland McGrath wrote:
> > > Knock yourself out:
> > >
> > > http://fpaste.org/FnFc/
> > >
> > > as I replied to John, though, oddly enough when I re-ran the command
> > > manually, it succeeded. Trying
On Mon, 2010-03-15 at 18:31 -0700, Roland McGrath wrote:
> > Knock yourself out:
> >
> > http://fpaste.org/FnFc/
> >
> > as I replied to John, though, oddly enough when I re-ran the command
> > manually, it succeeded. Trying to see if it builds through mock now.
>
> Are you sure that's the right
On Mon, 2010-03-15 at 21:05 -0400, i.g...@comcast.net wrote:
> On Mon, Mar 15, 2010 at 05:27:55PM -0700, Adam Williamson wrote:
> > On Mon, 2010-03-15 at 15:48 -0700, John Reiser wrote:
> > > > "could not read symbols: Invalid operation"
> > >
> > > Could "Invalid operation" be an error message th
> Knock yourself out:
>
> http://fpaste.org/FnFc/
>
> as I replied to John, though, oddly enough when I re-ran the command
> manually, it succeeded. Trying to see if it builds through mock now.
Are you sure that's the right command? The ld error mentions
libvo/vo_vaapi.o, but that file name doe
On Mon, Mar 15, 2010 at 05:27:55PM -0700, Adam Williamson wrote:
> On Mon, 2010-03-15 at 15:48 -0700, John Reiser wrote:
> > > "could not read symbols: Invalid operation"
> >
> > Could "Invalid operation" be an error message that corresponds to
> > an error from a system call? Apply 'strace' to t
On Mon, 2010-03-15 at 17:27 -0700, Adam Williamson wrote:
> On Mon, 2010-03-15 at 15:48 -0700, John Reiser wrote:
> > > "could not read symbols: Invalid operation"
> >
> > Could "Invalid operation" be an error message that corresponds to
> > an error from a system call? Apply 'strace' to the link
On Mon, 2010-03-15 at 16:22 -0700, Roland McGrath wrote:
> > Also, the "undefined reference to symbol" error is typical for the 'you
> > left it out of the linker line' situation, but "could not read symbols:
> > Invalid operation" is not, I've never seen that error before.
>
> This and several ot
On Mon, 2010-03-15 at 15:48 -0700, John Reiser wrote:
> > "could not read symbols: Invalid operation"
>
> Could "Invalid operation" be an error message that corresponds to
> an error from a system call? Apply 'strace' to the link step
> to see what happens shortly before the write() to stderr.
H
> Also, the "undefined reference to symbol" error is typical for the 'you
> left it out of the linker line' situation, but "could not read symbols:
> Invalid operation" is not, I've never seen that error before.
This and several other odd-looking things are "normal" cascade errors from
an undefine
> "could not read symbols: Invalid operation"
Could "Invalid operation" be an error message that corresponds to
an error from a system call? Apply 'strace' to the link step
to see what happens shortly before the write() to stderr.
--
--
devel mailing list
devel@lists.fedoraproject.org
https://
On Mon, 2010-03-15 at 14:51 -0700, Adam Williamson wrote:
> On Mon, 2010-03-15 at 17:45 -0400, Roland Grunberg wrote:
> > >/usr/bin/ld: libvo/vo_vaapi.o: undefined reference to symbol
> > >'vaGetConfigAttributes'
> > >/usr/bin/ld: note: 'vaGetConfigAttributes' is defined in DSO
> > >/usr/lib64/li
On Mon, 2010-03-15 at 17:45 -0400, Roland Grunberg wrote:
> >/usr/bin/ld: libvo/vo_vaapi.o: undefined reference to symbol
> >'vaGetConfigAttributes'
> >/usr/bin/ld: note: 'vaGetConfigAttributes' is defined in DSO
> >/usr/lib64/libva-0.31.0.5.so.1 so try adding it to the linker command line
> >/us
>/usr/bin/ld: libvo/vo_vaapi.o: undefined reference to symbol
>'vaGetConfigAttributes'
>/usr/bin/ld: note: 'vaGetConfigAttributes' is defined in DSO
>/usr/lib64/libva-0.31.0.5.so.1 so try adding it to the linker command line
>/usr/lib64/libva-0.31.0.5.so.1: could not read symbols: Invalid operati
Hitting an odd error during a build that I've never seen before today,
looks like something to do with recent linker changes.
I maintain a side repo with an mplayer build with VA-API support, so I
rebuild that quite often. If I try and build it on F13 currently, I get
this when linking:
/usr/bin/
15 matches
Mail list logo
