https://bugs.winehq.org/show_bug.cgi?id=40473
Bug ID: 40473 Summary: wine stops to compile with >=glibc-2.23 Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: darkcircle.0426@gmail.com Distribution: ---
I'm using gentoo distribution and with unstable amd64 arch tree branch, so I'm glad to test early version of wine. ;) some of user reported build issue, and i made patch to this below link
https://bugs.gentoo.org/show_bug.cgi?id=580046
and we should test which is working well or not.
so please help me to test my patch to eliminate compile stopping issue with =glibc-2.23
Thank you for advance.
https://bugs.winehq.org/show_bug.cgi?id=40473
--- Comment #2 from Seong-ho Cho darkcircle.0426@gmail.com --- Created attachment 54230 --> https://bugs.winehq.org/attachment.cgi?id=54230 This patch is following autoconf manual given by Mike Frysinger, Thanks.
I modified a patch from initially submitted one to the gentoo bugzilla.
https://bugs.winehq.org/show_bug.cgi?id=40473
Mike Frysinger vapier@gentoo.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |vapier@gentoo.org
--- Comment #1 from Mike Frysinger vapier@gentoo.org --- the build failure is semi-specific to Gentoo at this time. the plan is to deprecate these things in mainline glibc. other C libraries have dropped it (or never had it in the first place), although i'm guessing wine doesn't cover glibc too much atm.
the AC_HEADER_MAJOR autoconf macro is designed to support this.
https://www.gnu.org/software/autoconf/manual/autoconf-2.69/html_node/Particu...
https://bugs.winehq.org/show_bug.cgi?id=40473
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |austinenglish@gmail.com Summary|wine stops to compile with |wine fails to compile with |>=glibc-2.23 |>=glibc-2.23
https://bugs.winehq.org/show_bug.cgi?id=40473
Alistair Leslie-Hughes leslie_alistair@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |patch
https://bugs.winehq.org/show_bug.cgi?id=40473
--- Comment #3 from Mike Frysinger vapier@gentoo.org --- not sure if there's a more central location to put these (not terribly familiar w/wine codebase), but if there isn't, that patch looks good. thanks!
https://bugs.winehq.org/show_bug.cgi?id=40473
Sebastian Lackner sebastian@fds-team.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sebastian@fds-team.de
--- Comment #4 from Sebastian Lackner sebastian@fds-team.de --- Patches have to be submitted to the wine-patches mailing list for inclusion, see https://wiki.winehq.org/Submitting_Patches.
The proposed solution also looks good to me, but it doesn't apply cleanly on current Wine git. Make sure that the patch applies without --fuzz before sending it. Also, you might want to add a space inbetween of "#" and "include", like in the other lines above and below, but thats a minor issue. ;)
https://bugs.winehq.org/show_bug.cgi?id=40473
--- Comment #5 from Seong-ho Cho darkcircle.0426@gmail.com --- (In reply to Sebastian Lackner from comment #4)
Patches have to be submitted to the wine-patches mailing list for inclusion, see https://wiki.winehq.org/Submitting_Patches.
The proposed solution also looks good to me, but it doesn't apply cleanly on current Wine git. Make sure that the patch applies without --fuzz before sending it. Also, you might want to add a space inbetween of "#" and "include", like in the other lines above and below, but thats a minor issue. ;)
Thank you for telling about how to submit patch.
I sent my patch to wine-patches@whq.org via 'git send-email' I don't know that my patch is really good, and it goes well into the mail server. because, it's just my first patch submission *(-_-)*
https://bugs.winehq.org/show_bug.cgi?id=40473
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Keywords| |download, source
--- Comment #6 from Austin English austinenglish@gmail.com --- (In reply to Seong-ho Cho from comment #5)
(In reply to Sebastian Lackner from comment #4)
Patches have to be submitted to the wine-patches mailing list for inclusion, see https://wiki.winehq.org/Submitting_Patches.
The proposed solution also looks good to me, but it doesn't apply cleanly on current Wine git. Make sure that the patch applies without --fuzz before sending it. Also, you might want to add a space inbetween of "#" and "include", like in the other lines above and below, but thats a minor issue. ;)
Thank you for telling about how to submit patch.
I sent my patch to wine-patches@whq.org via 'git send-email' I don't know that my patch is really good, and it goes well into the mail server. because, it's just my first patch submission *(-_-)*
It will show here: https://source.winehq.org/patches/
once it's gone through moderation (assuming you haven't subscribed to wine-patches@).
https://bugs.winehq.org/show_bug.cgi?id=40473
super_man@post.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |super_man@post.com
--- Comment #7 from super_man@post.com --- This should be fixed now? All the 3 patches were committed.
https://bugs.winehq.org/show_bug.cgi?id=40473
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Fixed by SHA1| |ca8a08606d3f0900b3f4aa8f2e6 | |547882a22dba8 Resolution|--- |FIXED
--- Comment #8 from Austin English austinenglish@gmail.com --- Fixed by https://source.winehq.org/git/wine.git/commitdiff/ca8a08606d3f0900b3f4aa8f2e...
Thanks Seong-ho!
https://bugs.winehq.org/show_bug.cgi?id=40473
--- Comment #9 from Seong-ho Cho darkcircle.0426@gmail.com --- Thank you for helping me everyone :D !!
https://bugs.winehq.org/show_bug.cgi?id=40473
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #10 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 1.9.9.
https://bugs.winehq.org/show_bug.cgi?id=40473
Michael Stefaniuc mstefani@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |1.8.x CC| |mstefani@redhat.com
https://bugs.winehq.org/show_bug.cgi?id=40473
Michael Stefaniuc mstefani@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|1.8.x |---
--- Comment #11 from Michael Stefaniuc mstefani@redhat.com --- Removing 1.8.x milestone from bugs included in 1.8.3.