Created attachment 57356 [details] dbus compilation full log cross-compiling on top of mingw-w64 gcc, from ubuntu, with a modified version of mingw-cross-env, I run : automake && ./configure --host='x86_64-w64-mingw32' --prefix='/home/performance/prgm/mingw-cross-env-x86/usr/x86_64-w64-mingw32' --disable-shared --enable-static with this, I get errors, among which the first : CCLD dbus-launch.exe CC dbus-monitor.o CC dbus-print-message.o CCLD dbus-monitor.exe dbus-monitor.o: In function `profile_print_with_attrs': /home/performance/prgm/mingw-cross-env-x86/tmp-dbus/dbus-1.5.8/tools/dbus-monitor.c:154: undefined reference to `__imp_dbus_message_get_error_name' /home/performance/prgm/mingw-cross-env-x86/tmp-dbus/dbus-1.5.8/tools/dbus-monitor.c:151: undefined reference to `__imp_dbus_message_get_member' /home/performance/prgm/mingw-cross-env-x86/tmp-dbus/dbus-1.5.8/tools/dbus-monitor.c:148: undefined reference to `__imp_dbus_message_get_interface' /home/performance/prgm/mingw-cross-env-x86/tmp-dbus/dbus-1.5.8/tools/dbus-monitor.c:145: undefined reference to `__imp_dbus_message_get_path' /home/performance/prgm/mingw-cross-env-x86/tmp-dbus/dbus-1.5.8/tools/dbus-monitor.c:142: undefined reference to `__imp_dbus_message_get_destination' /home/performance/prgm/mingw-cross-env-x86/tmp-dbus/dbus-1.5.8/tools/dbus-monitor.c:139: undefined reference to `__imp_dbus_message_get_sender' /home/performance/prgm/mingw-cross-env-x86/tmp-dbus/dbus-1.5.8/tools/dbus-monitor.c:136: undefined reference to `__imp_dbus_message_get_reply_serial' /home/performance/prgm/mingw-cross-env-x86/tmp-dbus/dbus-1.5.8/tools/dbus-monitor.c:133: undefined reference to `__imp_dbus_message_get_serial' I am trying to compile "static", but it seems there is some confusion with dll?
(Why is everyone suddenly interested in building static binaries on Windows?) *** This bug has been marked as a duplicate of bug 46367 ***
*** This bug has been marked as a duplicate of bug 33973 ***
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.