Undefined reference to vaCopy
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- build-system
Research direction
Reproduce the Yocto build and start with videoprocess/vacopy.cpp at line 544, then inspect the vacopy target around Makefile lines 487 and 459. Determine why the linker cannot resolve vaCopy; done means the vacopy target links successfully and the build completes without this error.
Written by the indexing model from the issue text.
Description
Building the latest libva-utils on yocto gives the following error. Request you to provide a solution.
/usr/lib64/gcc/x86_64-ese-linux/9.3.0/../../../../x86_64-ese-linux/bin/ld: vacopy.o: in function `main':
/home/root/hemanth/libva-utils/videoprocess/vacopy.cpp:544: undefined reference to `vaCopy'
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:487: vacopy] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory '/home/root/hemanth/libva-utils/videoprocess'
make[1]: *** [Makefile:459: all-recursive] Error 1
make[1]: Leaving directory '/home/root/hemanth/libva-utils'
make: *** [Makefile:391: all] Error 2
- Dominant language
- C
- Stars
- 244
- Forks
- 175
- Avg merge
- 9d 7h
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from intel/libva-utils
-
av1encode: reference_frames[2..7] left as surface 0 (memset only covers 8 bytes)Possibly taken @0z5a claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
intel/libva-utils#390 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
intel/libva-utils#387 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
intel/libva-utils#378 · 6 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
intel/libva-utils#376 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
intel/libva-utils#374 ·
All issues in intel/libva-utils
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
[LOGO] VentoOSOpenlogo request
Difficulty 1/5 Under an hour Newbie friendliness 80/100
fastfetch-cli/fastfetch#2742 ·
Maintainers usually reply within 1 day
-
ecs_ptr_from_json does not free the buffer of a string longer than 256 bytes on two error pathsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SanderMertens/flecs#2444 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100