https://bugs.winehq.org/show_bug.cgi?id=42406
Bug ID: 42406 Summary: Wine compilation hangs starting from 1.9.22 version Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: vityokster@gmail.com Distribution: ---
Wine compilation hangs on compiling dll/ntdll/server.c starting from 1.9.22 version.
Using git bisect I found bad commit:
3b30002aecf7cd55970979f7e02a53866fe66f1f is the first bad commit commit 3b30002aecf7cd55970979f7e02a53866fe66f1f Author: Jacek Caban jacek@codeweavers.com Date: Mon Oct 24 17:48:49 2016 +0200
ntdll: Cache error information for cacheable handles with no fd.
Signed-off-by: Jacek Caban jacek@codeweavers.com Signed-off-by: Alexandre Julliard julliard@winehq.org
I compile wine using this command: CC="ccache gcc" CFLAGS="-O2 -march=i686" ./configure --verbose --disable-tests && make -j1
At git commit 27759315367428c6bd4bed5cf410407bd2d18fb9 compilation hangs at the same file.
https://bugs.winehq.org/show_bug.cgi?id=42406
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download, regression CC| |austinenglish@gmail.com, | |jacek@codeweavers.com
--- Comment #1 from Austin English austinenglish@gmail.com --- What complier/version?
https://bugs.winehq.org/show_bug.cgi?id=42406
--- Comment #2 from Viktor Yu. Kovalskiy vityokster@gmail.com --- gcc -v Using built-in specs. COLLECT_GCC=/usr/i686-pc-linux-gnu/gcc-bin/5.4.0/gcc COLLECT_LTO_WRAPPER=/usr/libexec/gcc/i686-pc-linux-gnu/5.4.0/lto-wrapper Target: i686-pc-linux-gnu Configured with: /var/tmp/portage/sys-devel/gcc-5.4.0-r3/work/gcc-5.4.0/configure --host=i686-pc-linux-gnu --build=i686-pc-linux-gnu --prefix=/usr --bindir=/usr/i686-pc-linux-gnu/gcc-bin/5.4.0 --includedir=/usr/lib/gcc/i686-pc-linux-gnu/5.4.0/include --datadir=/usr/share/gcc-data/i686-pc-linux-gnu/5.4.0 --mandir=/usr/share/gcc-data/i686-pc-linux-gnu/5.4.0/man --infodir=/usr/share/gcc-data/i686-pc-linux-gnu/5.4.0/info --with-gxx-include-dir=/usr/lib/gcc/i686-pc-linux-gnu/5.4.0/include/g++-v5 --with-python-dir=/share/gcc-data/i686-pc-linux-gnu/5.4.0/python --enable-languages=c,c++,fortran --enable-obsolete --enable-secureplt --disable-werror --with-system-zlib --enable-nls --without-included-gettext --enable-checking=release --with-bugurl=https://bugs.gentoo.org/ --with-pkgversion='Gentoo 5.4.0-r3 p1.3, pie-0.6.5' --enable-libstdcxx-time --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --disable-multilib --disable-altivec --disable-fixed-point --with-arch=i686 --enable-targets=all --disable-libgcj --enable-libgomp --disable-libmudflap --disable-libssp --disable-libcilkrts --disable-libmpx --enable-vtable-verify --enable-libvtv --enable-lto --without-isl --enable-libsanitizer Thread model: posix gcc version 5.4.0 (Gentoo 5.4.0-r3 p1.3, pie-0.6.5)
https://bugs.winehq.org/show_bug.cgi?id=42406
--- Comment #3 from Alexandre Julliard julliard@winehq.org --- You should probably file a bug with Gentoo then.
https://bugs.winehq.org/show_bug.cgi?id=42406
NP-Hardass np.hardass@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |np.hardass@gmail.com
--- Comment #4 from NP-Hardass np.hardass@gmail.com --- (In reply to Alexandre Julliard from comment #3)
You should probably file a bug with Gentoo then.
I am the Gentoo maintainer for Wine.
I reproduced the bug on both Gentoo (GCC-5.4.0) and Ubuntu (GCC-5.4.1), so it looks more likely that it is a GCC-5.4 issue than a Gentoo one.
From the Gentoo bug: compiling with CFLAGS="-march=i686 -O2" causes the hang,
but CFLAGS="-march=i686 -mtune=generic -O2" succeeds.
https://bugs.winehq.org/show_bug.cgi?id=42406
Robert Walker bob.mt.wya@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |bob.mt.wya@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=42406
winetest@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest@luukku.com
--- Comment #5 from winetest@luukku.com --- (In reply to NP-Hardass from comment #4)
(In reply to Alexandre Julliard from comment #3)
You should probably file a bug with Gentoo then.
I am the Gentoo maintainer for Wine.
I reproduced the bug on both Gentoo (GCC-5.4.0) and Ubuntu (GCC-5.4.1), so it looks more likely that it is a GCC-5.4 issue than a Gentoo one.
From the Gentoo bug: compiling with CFLAGS="-march=i686 -O2" causes the hang, but CFLAGS="-march=i686 -mtune=generic -O2" succeeds.
So could someone open a compiler bug then? Keeping bugs alive with no efforts fixing upsream helps none.
https://bugs.winehq.org/show_bug.cgi?id=42406
tt_1 herrtimson@yahoo.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |herrtimson@yahoo.de
https://bugs.winehq.org/show_bug.cgi?id=42406
--- Comment #6 from Viktor Yu. Kovalskii vityokster@gmail.com --- (In reply to winetest from comment #5)
(In reply to NP-Hardass from comment #4)
(In reply to Alexandre Julliard from comment #3)
You should probably file a bug with Gentoo then.
I am the Gentoo maintainer for Wine.
I reproduced the bug on both Gentoo (GCC-5.4.0) and Ubuntu (GCC-5.4.1), so it looks more likely that it is a GCC-5.4 issue than a Gentoo one.
From the Gentoo bug: compiling with CFLAGS="-march=i686 -O2" causes the hang, but CFLAGS="-march=i686 -mtune=generic -O2" succeeds.
So could someone open a compiler bug then? Keeping bugs alive with no efforts fixing upsream helps none.
Upstream (GCC) bug was reported:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78911
https://bugs.winehq.org/show_bug.cgi?id=42406
Viktor Yu. Kovalskii vityokster@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=78911
https://bugs.winehq.org/show_bug.cgi?id=42406
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTOURBUG
--- Comment #7 from Alexandre Julliard julliard@winehq.org --- Resolving NOTOURBUG then.
https://bugs.winehq.org/show_bug.cgi?id=42406
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #8 from Austin English austinenglish@gmail.com --- Closing.
https://bugs.winehq.org/show_bug.cgi?id=42406
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |RESOLVED
--- Comment #9 from Austin English austinenglish@gmail.com --- This was inadvertently caught up in my unclosed bugs filter. NOTOURBUG should only be closed when fixed upstream.
Setting back to RESOLVED NOTOURBUG.
Sorry for the spam.
https://bugs.winehq.org/show_bug.cgi?id=42406
Matteo Bruni matteo.mystral@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #10 from Matteo Bruni matteo.mystral@gmail.com --- Upstream bug suggests this is fixed in GCC 7+.
-
wine-bugs＠winehq.org