Gcenx / macports-wine

Updated wine Portfiles for macports
90 stars 11 forks source link

python310 - build failure (Mojave 10.14.6) #37

Closed contextnerror closed 1 year ago

contextnerror commented 1 year ago

Python310 fails during the build stage, preventing wine-devel from being installed. MacOSX10.13.sdk port has been installed, .conf file has been changed per README. Logs for wine and python are attached. wine-main.log python-main.log

Gcenx commented 1 year ago

I’ve looked over the relevant log python-main.log and it seems the issue might be related to having installed Xcode Command Line tools 11.

I have Xcode Command Line Tools 10 installed on my own macOS Mojave install

Once I’m home I’ll pull python310 into the overlay within a PR and add the muniversal portgroup that might help resolved this one from the looks of it.

Gcenx commented 1 year ago

I’ve not had time to test if using the muniversal portgroup helps or not but I’d recommend removing Xcode11 command line tools and instead installing Xcode 10 command line tools and ensure to Xcode select it.

contextnerror commented 1 year ago

Python worked using Xcode 10. Now it's getting stuck on gstreamer1 instead.

Error: Cannot install wine-devel for the archs 'i386 x86_64' because
Error: its dependency gstreamer1 does not build for the required archs by default
Error: and does not have a universal variant.
Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug.
Error: Processing of port wine-devel failed

It should be trying to use the modified version of the port, since using port info lists you as the maintainer.

Gcenx commented 1 year ago

If you’ve installed Xcode10 Command Line Tools you’ll need to deactivate MacOSX10.13.SDK and install it again so the required symlink gets fixed

Probably need to run clean on gstreamer1 along with wine-devel so it doesn’t get confused.

contextnerror commented 1 year ago

I had done those the first time, but tried again just in case. No change.

Gcenx commented 1 year ago

macOS Mojave gstreamer1+universal_main.log

I have no issue building gstreamer1 as +universal on my macOS Mojave drive.

contextnerror commented 1 year ago

Decided to start fresh since it seems like I bungled something at some point. Uninstalled all of MacPorts (local and bootstrap), uninstalled and reinstalled CLT 10.3, rebuilt MacPorts per these instructions, then cloned the repo into /opt and tried portindex. This now fails to parse the actual wine ports.

Failed to parse file emulators/wine-devel/Portfile: invalid command name "patchfiles-appended"
Failed to parse file emulators/wine-stable/Portfile: invalid command name "patchfiles-appended"
Total number of ports parsed:   72 
Ports successfully parsed:  70 
Ports failed:           2 
Up-to-date ports skipped:   0

Did something in the repo change during the few hours I was reinstalling?

Gcenx commented 1 year ago

Looks like I missed that error, fixed.

Still theres no need to manually run portindex once if you've setup this overlay as explained that will be generated automatically and updated when you run port selfupdate

contextnerror commented 1 year ago

Almost there, just one last hiccup during wine-devel configure step. Seems to be missing SDL.

Log Excerpt ``` :info:configure checking for SDL.h... no :info:configure configure: error: libSDL2 32-bit development files not found, SDL2 won't be supported. :info:configure This is an error since --with-sdl was requested. :info:configure Command failed: cd "/opt/local/var/macports/build/_opt_macports-wine_emulators_wine-devel/wine-devel/work/wine-wine-7.22-i386" && ./configure --prefix=/opt/local --without-alsa --without-capi --with-coreaudio --with-cups --without-dbus --without-fontconfig --with-freetype --with-gettext --without-gettextpo --without-gphoto --with-gnutls --without-gssapi --with-gstreamer --without-inotify --without-krb5 --with-ldap --with-mingw --without-netapi --with-opencl --with-opengl --without-oss --with-pcap --with-pthread --without-pulse --without-sane --with-sdl --without-udev --with-unwind --without-usb --without-v4l2 --without-x --with-wine64=/opt/local/var/macports/build/_opt_macports-wine_emulators_wine-devel/wine-devel/work/wine-wine-7.22-x86_64 --without-vulkan :info:configure Exit code: 1 :error:configure Failed to configure wine-devel: consult /opt/local/var/macports/build/_opt_macports-wine_emulators_wine-devel/wine-devel/work/wine-wine-7.22-i386/config.log :error:configure Failed to configure wine-devel: configure failure: command execution failed :debug:configure Error code: NONE :debug:configure Backtrace: configure failure: command execution failed :debug:configure while executing :debug:configure "portconfigure::configure_main_orig" :debug:configure (procedure "portconfigure::configure_main" line 32) :debug:configure invoked from within :debug:configure "$procedure $targetname" :error:configure See /opt/local/var/macports/logs/_opt_macports-wine_emulators_wine-devel/wine-devel/main.log for details. ```

Config and main log are attached. config.log main.log

Gcenx commented 1 year ago

Should be fixed with https://github.com/Gcenx/macports-wine/commit/4036d93afa82c251f77fdfad2209b0a821941750

Seems pkgconfig isn't finding anything for i386 only x86_64 no idea why.

contextnerror commented 1 year ago

Command execution failed during the build phase now. main.log

Gcenx commented 1 year ago

An issue only on the i386 slice and it looks like gstreamer.

I’ve not ran a full build on my macOS Mojave system since the gstreamer update, I’m currently testing a possible fix.

Gcenx commented 1 year ago

No issues on my end so it should have been resolved via https://github.com/Gcenx/macports-wine/commit/adfe53a7c1e11ea31f84031b81412cea27ca21e8

contextnerror commented 1 year ago

Thank you very much, it's installed working now. Do I still need to keep the deployment_target and sdk_version in my .conf file?

Gcenx commented 1 year ago

Thank you very much, it's installed working now.

Glad it’s now working for you.

Do I still need to keep the deployment_target and sdk_version in my .conf file?

Yes those are required to enable i386 support on macOS Mojave.