https://bugs.winehq.org/show_bug.cgi?id=55984
Bug ID: 55984 Summary: GStreamer 32bits headers not found even they're installed Product: Wine Version: 8.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: berillions@gmail.com Regression SHA1: 3aca5994584b3e91bc2abc138dde8422d0d15f24 Distribution: Debian
Hi,
There is a regression since wine-8.21 when i build wine 32bits on a x86_64 system. Gstreamer base development 32bits packages from repository (libgstreamer-plugins-base1.0-dev:i386 and libgstreamer1.0-dev:i386) are correctly installed.
Configure wine-8.20 has no issue, i don't have the warning about the headers not found and GStreamer not supported. Only with wine-8.21 + latest wine-git.
I did a regression test and found this commit which cause the issue. Revert it on wine-git fix the issue.
https://bugs.winehq.org/show_bug.cgi?id=55984
Maxime berillions@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression
https://bugs.winehq.org/show_bug.cgi?id=55984
--- Comment #1 from Alexandre Julliard julliard@winehq.org --- Please attach your config.log.
https://bugs.winehq.org/show_bug.cgi?id=55984
--- Comment #2 from Maxime berillions@gmail.com --- Created attachment 75586 --> https://bugs.winehq.org/attachment.cgi?id=75586 wine-8.20 config log
No issue in this log, GStreamer headers are found - Configure launched with "./configure --disable-tests CC='/usr/bin/i686-linux-gnu-gcc-12' CROSSCC='i686-w64-mingw32-gcc'"
https://bugs.winehq.org/show_bug.cgi?id=55984
--- Comment #3 from Maxime berillions@gmail.com --- Created attachment 75587 --> https://bugs.winehq.org/attachment.cgi?id=75587 wine-8.21 config log
Issue in this log, GStreamer headers are not found - Configure launched with "./configure --disable-tests CC='/usr/bin/i686-linux-gnu-gcc-12' CROSSCC='i686-w64-mingw32-gcc'"
https://bugs.winehq.org/show_bug.cgi?id=55984
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4@web.de
https://bugs.winehq.org/show_bug.cgi?id=55984
--- Comment #4 from Alexandre Julliard julliard@winehq.org --- It looks like the previous config.guess was detecting a 64-bit system, despite the compiler being 32-bit. I'd say that the new behavior is more correct. What happens if you don't set CC explicitly?
https://bugs.winehq.org/show_bug.cgi?id=55984
--- Comment #5 from Maxime berillions@gmail.com --- (In reply to Alexandre Julliard from comment #4)
It looks like the previous config.guess was detecting a 64-bit system, despite the compiler being 32-bit. I'd say that the new behavior is more correct. What happens if you don't set CC explicitly?
This is the ouput console i have if i don't set CC :
#####
checking build system type... x86_64-pc-linux-gnu checking host system type... x86_64-pc-linux-gnu checking whether make sets $(MAKE)... yes checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether the compiler supports GNU C... yes checking whether gcc accepts -g... yes checking for gcc option to enable C11 features... none needed checking for g++... g++ checking whether the compiler supports GNU C++... yes checking whether g++ accepts -g... yes checking for g++ option to enable C++11 features... none needed checking for cpp... cpp checking for ld... ld checking whether gcc -m32 works... no configure: error: Cannot build a 32-bit program, you need to install 32-bit development libraries. make: *** Pas de cible spécifiée et aucun makefile n'a été trouvé. Arrêt. make: *** Aucune règle pour fabriquer la cible « install ». Arrêt. make: *** Aucune règle pour fabriquer la cible « install ». Arrêt.
####
https://bugs.winehq.org/show_bug.cgi?id=55984
--- Comment #6 from Alexandre Julliard julliard@winehq.org --- Your setup sounds a bit strange... If the 32-bit libraries are not in the default places you'll probably need to set PKG_CONFIG_PATH accordingly.
https://bugs.winehq.org/show_bug.cgi?id=55984
--- Comment #7 from Maxime berillions@gmail.com --- (In reply to Alexandre Julliard from comment #6)
Your setup sounds a bit strange... If the 32-bit libraries are not in the default places you'll probably need to set PKG_CONFIG_PATH accordingly.
I need to check ... Thanks Debian and his multiarch system ...
https://bugs.winehq.org/show_bug.cgi?id=55984
--- Comment #8 from Maxime berillions@gmail.com --- (In reply to Maxime from comment #7)
(In reply to Alexandre Julliard from comment #6)
Your setup sounds a bit strange... If the 32-bit libraries are not in the default places you'll probably need to set PKG_CONFIG_PATH accordingly.
I need to check ... Thanks Debian and his multiarch system ...
Thanks to Zeb and Remi, i found the problem on my system ... Instead of to use 'gcc-multilib" package to build Wine, i used "i686gcc cross-compiler" package.
I cleaned up everything and now the compilation works fine. You can close this bug report AJ.
https://bugs.winehq.org/show_bug.cgi?id=55984
Zeb Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |z.figura12@gmail.com Resolution|--- |ABANDONED
--- Comment #9 from Zeb Figura z.figura12@gmail.com --- Resolving ABANDONED. It's not obvious whether failure of the cross-compiler to work with pkg-config is a Wine bug, a distribution bug, or user error, but it doesn't seem worth looking into.
https://bugs.winehq.org/show_bug.cgi?id=55984
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #10 from Austin English austinenglish@gmail.com --- Closing.
-
WineHQ Bugzilla