Hi all, I'd like to share with you progress on gecko64. First of all, I think that it was never said in public, although I've been asked about it: there won't be gecko64 for 1.2 release. I think we will have Gecko release in the second half of this year it will support 64-bit, but it's not yet clear when exactly. We may try to do it near the next Firefox release, but time will show how it will work. However, it doesn't mean that nothing is going on around Wine Gecko. I've recently switched to mingw-w64 for 32-bit builds. I've very pleased with it. They are far better in co-operation, don't have senseless politics like mingw and their quality of headers and libraries is far better. We won't need to maintain fixes to build envinonment anymore. (I've been even talking about better co-operation between our projects, but that's OT here and I will report progress when there will be more to say). We're much nearer to allow packagers to build their own Gecko now. Back to gecko64, I've completed the first step. I have a working 64-bit Firefox crosscompiled with mingw-w64. See: https://bugzilla.mozilla.org/show_bug.cgi?id=570342 for details. It starts and runs on Windows. Now I wait for patches to be committed to Mozilla. It may take awhile :/ Before we may think about support for gecko64 in MSHTML, we have to fix its issues in Wine. Firefox is a good Gecko test and it needs to be fixed first. Unfortunately it currently doesn't even start. I've put a build on server in case anyone would like to try it: http://gerwazy.lo3.wroc.pl/~jcaban/wine/firefox-mingw-w64.tar.bz2 Volunteers on working on Wine side are very welcomed. There are also some other tests from Mozilla code. Note that before fixing any more sophisticated bug, it's worth to make sure on Windows, that the bug is in Wine, not in the build. All I verified is that Firefox should start and basic functionality works (and doesn't work on Wine). Any comments and suggestions are welcomed. Cheers, Jacek
Hi Jacek,
However, it doesn't mean that nothing is going on around Wine Gecko. I've recently switched to mingw-w64 for 32-bit builds. I've very pleased with it. They are far better in co-operation, don't have senseless politics like mingw and their quality of headers and libraries is far better.
Great news! This has been a senseless stumbling block for some time. I'm looking forward to the ability to build wine-gecko.
Any comments and suggestions are welcomed.
One suggestion is that bugs get logged about test failures on Wine wherever possible. Dan has done that for the chromium test suite, and that's led to several bugs getting converted to Wine regression tests, and even a few fixes ;-) Cheers, --Juan
Hi Juan, On 6/6/10 7:35 PM, Juan Lang wrote:
Any comments and suggestions are welcomed.
One suggestion is that bugs get logged about test failures on Wine wherever possible. Dan has done that for the chromium test suite, and that's led to several bugs getting converted to Wine regression tests, and even a few fixes ;-)
I agree, that's something I'd like to see as well. There are, in fact, two ways interesting me for running these tests: - Tests of MSVC builds That would be similar Chrome tests. It would be compiled the same way (under Wine) as official Firefox, so we'd find Wine bugs this way. The work on it was done in parallel to Chrome work, but it was never completed. AFAIK the main stopper is currently cmd implementation, so the SoC project should help. Dan will know more details about it. - Get tests of our mingw build There is a config in Wine Gecko Git tree that enables building them. They compile fine, but there is a problem with running them. I've played a bit with it in the past. To run them, a combination of python and makefiles is used. The compilation is done in Linux environment, without Wine involved, so we have to teach Mozilla build environment to run tests under Wine. By adding a simple wrapper I was able to run some subset of tests and they found a few bugs. This way we test both problems with mingw compilation and Wine and they have to be separated. From my experience there were more build bugs than Wine's. They are, however, interesting for us as well (for me even more, as we can fix Wine anytime and Wine Gecko releases are rare). The problem with running more tests is that we really need python scripts to be ran under Windows python and that's more tricky. I've never found the time to investigate it further. Cheers, Jacek
Hi Jacek, 2010/6/5 Jacek Caban <jacek(a)codeweavers.com>:
Hi all,
I'd like to share with you progress on gecko64. First of all, I think that it was never said in public, although I've been asked about it: there won't be gecko64 for 1.2 release. I think we will have Gecko release in the second half of this year it will support 64-bit, but it's not yet clear when exactly. We may try to do it near the next Firefox release, but time will show how it will work.
However, it doesn't mean that nothing is going on around Wine Gecko. I've recently switched to mingw-w64 for 32-bit builds. I've very pleased with it. They are far better in co-operation, don't have senseless politics like mingw and their quality of headers and libraries is far better. We won't need to maintain fixes to build envinonment anymore. (I've been even talking about better co-operation between our projects, but that's OT here and I will report progress when there will be more to say). We're much nearer to allow packagers to build their own Gecko now.
Back to gecko64, I've completed the first step. I have a working 64-bit Firefox crosscompiled with mingw-w64. See: https://bugzilla.mozilla.org/show_bug.cgi?id=570342 for details. It starts and runs on Windows. Now I wait for patches to be committed to Mozilla. It may take awhile :/ Before we may think about support for gecko64 in MSHTML, we have to fix its issues in Wine. Firefox is a good Gecko test and it needs to be fixed first. Unfortunately it currently doesn't even start. I've put a build on server in case anyone would like to try it: http://gerwazy.lo3.wroc.pl/~jcaban/wine/firefox-mingw-w64.tar.bz2 Volunteers on working on Wine side are very welcomed. There are also some other tests from Mozilla code. Note that before fixing any more sophisticated bug, it's worth to make sure on Windows, that the bug is in Wine, not in the build. All I verified is that Firefox should start and basic functionality works (and doesn't work on Wine).
I cannot find it the reference for it at the moment, but I remember that by default the stack is in memory < 4gb on 64-bits too, unless you did something. I wish I could remember how you could override the behavior, but this could be why it won't run in wine, but will in windows. For a stack variable: Wine64: &a = 0x7F9E9381FCDC Win64: &a = 0x22FE7C win64_32: &a = 0x28FF44 Cheers, Maarten
On Mon, Jun 7, 2010 at 10:38 AM, Maarten Lankhorst <m.b.lankhorst(a)gmail.com> wrote:
I cannot find it the reference for it at the moment, but I remember that by default the stack is in memory < 4gb on 64-bits too, unless you did something. I wish I could remember how you could override the behavior, but this could be why it won't run in wine, but will in windows.
For a stack variable:
Wine64: &a = 0x7F9E9381FCDC Win64: &a = 0x22FE7C win64_32: &a = 0x28FF44
Seems stack is always at higher addresses and heap at lower ones. The only sysctl which seems to affect this is kernel.randomize_va_space, but it won't change virtual address very much. $ sudo sysctl kernel.randomize_va_space=0 kernel.randomize_va_space = 0 $ cat /proc/self/maps | grep 'stack\|heap' 0060f000-00630000 rw-p 00000000 00:00 0 [heap] 7ffffffea000-7ffffffff000 rw-p 00000000 00:00 0 [stack] $ sudo sysctl kernel.randomize_va_space=2 kernel.randomize_va_space = 2 $ cat /proc/self/maps | grep 'stack\|heap' 00b6d000-00b8e000 rw-p 00000000 00:00 0 [heap] 7fff8676f000-7fff86784000 rw-p 00000000 00:00 0 [stack] Or are you talking about a wineloader kind of option? Octavian
On Mon, Jun 07, 2010 at 09:38:39AM +0200, Maarten Lankhorst wrote:
Hi Jacek,
2010/6/5 Jacek Caban <jacek(a)codeweavers.com>:
Hi all,
I'd like to share with you progress on gecko64. First of all, I think that it was never said in public, although I've been asked about it: there won't be gecko64 for 1.2 release. I think we will have Gecko release in the second half of this year it will support 64-bit, but it's not yet clear when exactly. We may try to do it near the next Firefox release, but time will show how it will work.
However, it doesn't mean that nothing is going on around Wine Gecko. I've recently switched to mingw-w64 for 32-bit builds. I've very pleased with it. They are far better in co-operation, don't have senseless politics like mingw and their quality of headers and libraries is far better. We won't need to maintain fixes to build envinonment anymore. (I've been even talking about better co-operation between our projects, but that's OT here and I will report progress when there will be more to say). We're much nearer to allow packagers to build their own Gecko now.
Back to gecko64, I've completed the first step. I have a working 64-bit Firefox crosscompiled with mingw-w64. See: https://bugzilla.mozilla.org/show_bug.cgi?id=570342 for details. It starts and runs on Windows. Now I wait for patches to be committed to Mozilla. It may take awhile :/ Before we may think about support for gecko64 in MSHTML, we have to fix its issues in Wine. Firefox is a good Gecko test and it needs to be fixed first. Unfortunately it currently doesn't even start. I've put a build on server in case anyone would like to try it: http://gerwazy.lo3.wroc.pl/~jcaban/wine/firefox-mingw-w64.tar.bz2 Volunteers on working on Wine side are very welcomed. There are also some other tests from Mozilla code. Note that before fixing any more sophisticated bug, it's worth to make sure on Windows, that the bug is in Wine, not in the build. All I verified is that Firefox should start and basic functionality works (and doesn't work on Wine).
I cannot find it the reference for it at the moment, but I remember that by default the stack is in memory < 4gb on 64-bits too, unless you did something. I wish I could remember how you could override the behavior, but this could be why it won't run in wine, but will in windows.
For a stack variable:
Wine64: &a = 0x7F9E9381FCDC Win64: &a = 0x22FE7C win64_32: &a = 0x28FF44
Is this really an issue with the above Firefox? I get a assertion in font handling on running here. Ciao, Marcus
On Sat, Jun 05, 2010 at 09:58:03PM +0200, Jacek Caban wrote:
Hi all,
I'd like to share with you progress on gecko64. First of all, I think that it was never said in public, although I've been asked about it: there won't be gecko64 for 1.2 release. I think we will have Gecko release in the second half of this year it will support 64-bit, but it's not yet clear when exactly. We may try to do it near the next Firefox release, but time will show how it will work.
Any comments and suggestions are welcomed.
It wants MSVCP100.DLL here. Where do I get that :( Ciao, Marcus
On 6/7/10 11:41 AM, Marcus Meissner wrote:
On Sat, Jun 05, 2010 at 09:58:03PM +0200, Jacek Caban wrote:
Hi all,
I'd like to share with you progress on gecko64. First of all, I think that it was never said in public, although I've been asked about it: there won't be gecko64 for 1.2 release. I think we will have Gecko release in the second half of this year it will support 64-bit, but it's not yet clear when exactly. We may try to do it near the next Firefox release, but time will show how it will work.
Any comments and suggestions are welcomed.
It wants MSVCP100.DLL here. Where do I get that :(
That's strange, it surely shouldn't, mingw doesn't use msvcp*.dll. I guess you're running my build on Windows? Please make sure you don't have any other instance of Firefox running. Jacek
On Mon, Jun 07, 2010 at 12:05:09PM +0200, Jacek Caban wrote:
On 6/7/10 11:41 AM, Marcus Meissner wrote:
On Sat, Jun 05, 2010 at 09:58:03PM +0200, Jacek Caban wrote:
Hi all,
I'd like to share with you progress on gecko64. First of all, I think that it was never said in public, although I've been asked about it: there won't be gecko64 for 1.2 release. I think we will have Gecko release in the second half of this year it will support 64-bit, but it's not yet clear when exactly. We may try to do it near the next Firefox release, but time will show how it will work.
Any comments and suggestions are welcomed. It wants MSVCP100.DLL here. Where do I get that :(
That's strange, it surely shouldn't, mingw doesn't use msvcp*.dll. I guess you're running my build on Windows? Please make sure you don't have any other instance of Firefox running.
I confused your build with the Mozilla.org Win64 build ... sorry. Ciao, Marcus
participants (6)
-
Jacek Caban -
Juan Lang -
Maarten Lankhorst -
Marcus Meissner -
Nikolay Sivov -
Octavian Voicu