-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build failure, undefined reference. #4894
Comments
This was caused by a change in waf.
https://github.com/waf-project/waf/commit/fa145ed65395d6c2c2f15ea54398aa010d91306f |
config.log - https://pastebin.com/6U1ZtvGS |
Unless you are the mpv maintainers, please use the waf version that comes with mpv. In this particular case, mpv has its own version of diff --git a/waftools/syms.py b/waftools/syms.py
index eff35e75a3..271dfe4ad2 100644
--- a/waftools/syms.py
+++ b/waftools/syms.py
@@ -33,7 +33,7 @@ class compile_sym(Task):
raise WafError('NotImplemented')
@feature('syms')
-@after_method('process_source', 'process_use', 'apply_link', 'process_uselib_local')
+@after_method('process_source', 'process_use', 'apply_link', 'process_uselib_local', 'propagate_uselib_vars')
def do_the_symbol_stuff(self):
tsk = self.create_task('compile_sym',
[self.path.find_node(self.export_symbols_def)], |
Your patch seems to allow waf-2.0 to finish compiling mpv, thanks! Is this something that should be eventually merged into mpv or was the change in waf incorrect? My build script will clone the mpv master and then the waf master, build waf and use that to build mpv. This has worked well for over a year so I never realized that mpv provided its own waf? However I think my current method is preferable because it will uncover issues like this and I assume that mpv will want to resolve this unless the devs plan to use waf 1.9 for ever? :) |
Use the build instructions provided by mpv. |
Can we please keep this discussion directed towards a solution instead? |
The solution is to use the version of waf that the mpv build scripts depend on. |
That is not a solution, that is a workaround. This will have to be fixed either way eventually, no? |
Thanks to ita1024 for the patch. Fixes mpv-player#4894
Thanks to ita1024 for the patch. Fixes #4894 Signed-off-by: wm4 <wm4@nowhere>
FWIW, with commit c09760d , mpv-build on osx started spawning several identical warnings of:
This is seemingly because the final linkage command has several
And for reference the beginning of the linkage command before this commit (no
FWIW, the compile commands did have several The warnings can be observed with waf 1.8.12 and waf 2.0.3, and were confirmed on three different systems (@Akemi , @Argon- and myself). |
mpv version and platform
mpv master (80e3173)
gcc-7.2.0
glibc-2.26
ffmpeg-3.3.4
OS:
Slackware64-current
Reproduction steps
Build mpv.
Expected behavior
Build should finish.
Actual behavior
Log file
Build log - https://pastebin.com/AESrf805
The text was updated successfully, but these errors were encountered: