Build with VS2010
Forum rules
This is a self-serve support board for our community. The development team can't provide any support for Windows XP (and compatible versions of Pale Moon for it) any longer.
This is a self-serve support board for our community. The development team can't provide any support for Windows XP (and compatible versions of Pale Moon for it) any longer.
Build with VS2010
Hi guys, greetings
I want to build latest palemoon source, but VS2010 is latest VS supported in XP. Im running XP x64
Anyone success build with VS2010?
I ask because is a big download (slow connection here) and i want to know if i download VS2010 it will compile without much problems, or better i found a PC with Windows 7 and download VS2012
For a 600+mb download, it can take for me 2 days or more
Thanks
I want to build latest palemoon source, but VS2010 is latest VS supported in XP. Im running XP x64
Anyone success build with VS2010?
I ask because is a big download (slow connection here) and i want to know if i download VS2010 it will compile without much problems, or better i found a PC with Windows 7 and download VS2012
For a 600+mb download, it can take for me 2 days or more
Thanks
Re: Build with VS2010
It is currently unknown if the current codebase will build successfully with VS2010.. It MIGHT. VS2012 is the version we currently support and can offer assistance for. The build system still supports 2010 but if the code will compile is another story.
Your best bet is to use Windows 7 and VS2012. However, there are other issues to work out for NT 5.1 and NT 5.2 for x86 and x64 beyond the version of the compiler used.
Your best bet is to use Windows 7 and VS2012. However, there are other issues to work out for NT 5.1 and NT 5.2 for x86 and x64 beyond the version of the compiler used.
Re: Build with VS2010
EDIT: Sorry one question, to build a 64bits palemoon, is possible in windows 7 32bits?
In gcc is easy to do different target, but i dont have any idea about VS, last i use was ver6 in late 90s
Thank good im still using XP, not in a crazy OS like 7+
When i finish i will build, i get a Pentium 4 PC and installed Windows 7 SP1. I will came back if i have problems, thanks for help
In gcc is easy to do different target, but i dont have any idea about VS, last i use was ver6 in late 90s
thanks for reply... this is a non sense... i downloaded VS2012, now the SDK (400mb!) and now a update 4, that is 2.4GB?¿ i will finish downloading in a week...Matt A Tobin wrote:It is currently unknown if the current codebase will build successfully with VS2010.. It MIGHT. VS2012 is the version we currently support and can offer assistance for. The build system still supports 2010 but if the code will compile is another story.
Your best bet is to use Windows 7 and VS2012. However, there are other issues to work out for NT 5.1 and NT 5.2 for x86 and x64 beyond the version of the compiler used.
Thank good im still using XP, not in a crazy OS like 7+
When i finish i will build, i get a Pentium 4 PC and installed Windows 7 SP1. I will came back if i have problems, thanks for help
-
- Pale Moon guru
- Posts: 35650
- Joined: 2011-08-28, 17:27
- Location: Motala, SE
Re: Build with VS2010
It is possible to cross-compile a 64-bit target, but you'll have to make sure to initialize the right toolset (32-bit cross-compiler).
The build system, however, will also have to be told you are cross-compiling or it will try to build some tools as 64-bit and then erroneously try to use them. to get that to work is hacky at best; I did this in the past with the first 64-bit builds on VS2008(? i think...), but i don't recall off-hand exactly the steps I used. You'll have to do some research.
The build system, however, will also have to be told you are cross-compiling or it will try to build some tools as 64-bit and then erroneously try to use them. to get that to work is hacky at best; I did this in the past with the first 64-bit builds on VS2008(? i think...), but i don't recall off-hand exactly the steps I used. You'll have to do some research.
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
-
- Lunatic
- Posts: 400
- Joined: 2015-06-22, 19:48
- Location: USA (North Springfield, Vermont)
Re: Build with VS2010
Moderator note: superfluous full-post quote removed.
Off-topic:
I like that OS, too! I dunno. I hate what can be interpreted as a sabotage by Microsoft to change the x64 program format!
Where XP x64 rejects them as corrupted!
I like that OS, too! I dunno. I hate what can be interpreted as a sabotage by Microsoft to change the x64 program format!
Where XP x64 rejects them as corrupted!
Re: Build with VS2010
Moonchild wrote:It is possible to cross-compile a 64-bit target, but you'll have to make sure to initialize the right toolset (32-bit cross-compiler).
The build system, however, will also have to be told you are cross-compiling or it will try to build some tools as 64-bit and then erroneously try to use them. to get that to work is hacky at best; I did this in the past with the first 64-bit builds on VS2008(? i think...), but i don't recall off-hand exactly the steps I used. You'll have to do some research.
Thanks dont worry, i found the way
Finally i installed windows 7, and looks everything works well, im still compiling
The PC is a little old, with 512mb of ram, it will take a while i think
I will update, if i have problems or success... for sure i will face problems, since my target is XP
Re: Build with VS2010
512 megs of ram is not nearly enough.. You should have about 6gbs of ram.. (4 minimum).. It will fail on linking libxul.
-
- Pale Moon guru
- Posts: 35650
- Joined: 2011-08-28, 17:27
- Location: Motala, SE
Re: Build with VS2010
Yeah I'm afraid anything less than at the very least 3GB will fail to properly link the xul library, even if you're not using LTCG.
Also, if your build target is XP (I assume you're trying to build for XP x64) then you need to make sure to use the correct target windows subsystem versions (5.x) or the resulting binaries won't run on XP.
Tobin, can you dig up the diff from PM4XPx64 that you used for this, maybe?
Also, if your build target is XP (I assume you're trying to build for XP x64) then you need to make sure to use the correct target windows subsystem versions (5.x) or the resulting binaries won't run on XP.
Tobin, can you dig up the diff from PM4XPx64 that you used for this, maybe?
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
Re: Build with VS2010
Sadly, the motherboard have one SIMM slot dead, plus, over 512mb simm, is unstable. Right now, im in holiday in a friend country house, now I have 2 PCs right now: this Pentium 4 I build for VS2012, and a my Pentium 2 laptopMatt A Tobin wrote:512 megs of ram is not nearly enough.. You should have about 6gbs of ram.. (4 minimum).. It will fail on linking libxul.
I just used my best option .... Pentium 4 vs Pentium 2
In my house I have a Pentium 4 with 2Gb RAM and XP x64. This is my main PC, but until next week i will not come back home. My idea is to use my free time now, and try to build a recent palemoon
I will take care about libxul if fail, at least i will know why thanks!
Moonchild wrote:Yeah I'm afraid anything less than at the very least 3GB will fail to properly link the xul library, even if you're not using LTCG.
Also, if your build target is XP (I assume you're trying to build for XP x64) then you need to make sure to use the correct target windows subsystem versions (5.x) or the resulting binaries won't run on XP.
Tobin, can you dig up the diff from PM4XPx64 that you used for this, maybe?
Hi, my idea was made a first build, without touch nothing, and if everything works well, start working on compile for XP
Any help, obviusly will be helpfull, but until i finish compiling, i dont wanna ask much help yet thanks a lot for your time
Re: Build with VS2010
https://github.com/binoc-software/palemoon-contrib/commit/88e729d7a1c470ebb11aecafddb3ea249db5cc67
https://github.com/binoc-software/palemoon-contrib/commit/da10684952f70e0241616ae0cb28ba4651b61f26
https://github.com/binoc-software/palemoon-contrib/commit/8e17d91507661688a303fe1d24be46baa8e8d860
https://github.com/binoc-software/palemoon-contrib/commit/25ff7f4bf2a1a30a2fecb61dd04c1d68c918d39d
https://github.com/binoc-software/palemoon-contrib/commit/a4f80e1fc4d9fe94996bf794f4eaf2847baebe77
https://github.com/binoc-software/palemoon-contrib/commit/f074411dda12648de9bd4c854edb6a6038cf7808
I may be missing one or two.. But that should give you a good idea..
https://github.com/binoc-software/palemoon-contrib/commit/da10684952f70e0241616ae0cb28ba4651b61f26
https://github.com/binoc-software/palemoon-contrib/commit/8e17d91507661688a303fe1d24be46baa8e8d860
https://github.com/binoc-software/palemoon-contrib/commit/25ff7f4bf2a1a30a2fecb61dd04c1d68c918d39d
https://github.com/binoc-software/palemoon-contrib/commit/a4f80e1fc4d9fe94996bf794f4eaf2847baebe77
https://github.com/binoc-software/palemoon-contrib/commit/f074411dda12648de9bd4c854edb6a6038cf7808
I may be missing one or two.. But that should give you a good idea..
Re: Build with VS2010
Matt A Tobin wrote:https://github.com/binoc-software/palemoon-contrib/commit/88e729d7a1c470ebb11aecafddb3ea249db5cc67
https://github.com/binoc-software/palemoon-contrib/commit/da10684952f70e0241616ae0cb28ba4651b61f26
https://github.com/binoc-software/palemoon-contrib/commit/8e17d91507661688a303fe1d24be46baa8e8d860
https://github.com/binoc-software/palemoon-contrib/commit/25ff7f4bf2a1a30a2fecb61dd04c1d68c918d39d
https://github.com/binoc-software/palemoon-contrib/commit/a4f80e1fc4d9fe94996bf794f4eaf2847baebe77
https://github.com/binoc-software/palemoon-contrib/commit/f074411dda12648de9bd4c854edb6a6038cf7808
I may be missing one or two.. But that should give you a good idea..
Very kind for your help, thanks a lot. Yes, after take a look at the source changes, i have a good idea about what to change. I was looking similar stuff too
I will finish (or hope so) a normal building, and after im sure all is OK, i will do the changes for a XP build
Thanks again for all help, nice forum here
Re: Build with VS2010
Ok guys sorry double post
My PC finish something... but i dont know what......
After tiping "./mach package" i get two small files in obj. Thats all
palemoon-25.8.1.en-US.win64-x86_64.json
palemoon-25.8.1.en-US.win64-x86_64.txt
the json file, content this
My PC finish something... but i dont know what......
After tiping "./mach package" i get two small files in obj. Thats all
palemoon-25.8.1.en-US.win64-x86_64.json
palemoon-25.8.1.en-US.win64-x86_64.txt
the json file, content this
But not zip or exe...{
"as": "ml64.exe",
"buildid": "20151130162236",
"cc": "cl",
"cxx": "cl",
"host_alias": "x86_64-pc-mingw32",
"host_cpu": "x86_64",
"host_os": "mingw32",
"host_vendor": "pc",
"ld": "link",
"moz_app_id": "{8de7fcbb-c55c-4fbe-bfc5-fc555c87dbc4}",
"moz_app_maxversion": "25.*",
"moz_app_name": "palemoon",
"moz_app_vendor": "Moonchild",
"moz_app_version": "25.8.1",
"moz_pkg_platform": "win64-x86_64",
"moz_source_repo": "",
"moz_source_stamp": "",
"moz_update_channel": "default",
"target_alias": "x86_64-pc-mingw32",
"target_cpu": "x86_64",
"target_os": "mingw32",
"target_vendor": "pc"
}
-
- Pale Moon guru
- Posts: 35650
- Joined: 2011-08-28, 17:27
- Location: Motala, SE
Re: Build with VS2010
Please post more of the build log, as text, to see the full error there.
If building worked otherwise and packaging is what failed, then you're pretty close to completing the build -- no telling how stable it is if it had to use swap to link, though.
If building worked otherwise and packaging is what failed, then you're pretty close to completing the build -- no telling how stable it is if it had to use swap to link, though.
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
Re: Build with VS2010
Greetings, this is helpful?
Code: Select all
0:03.81 C:/mozilla-build/msys/bin/sh.exe -c c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/make.py -f client.mk -s
0:23.12 Adding client.mk options from e:/palemoon-source/.mozconfig:
0:23.12 MOZ_CO_PROJECT=browser
0:23.73 TEST-PASS | check-sync-dirs.py | e:\palemoon-source\js\src\config <= e:\palemoon-source\config
0:36.64 export_tier_base
0:48.94 libs_tier_base
1:00.14 tools_tier_base
1:09.81 export_tier_nspr
1:15.87 libs_tier_nspr
1:25.66 tools_tier_nspr
1:30.53 export_tier_nss
4:46.17 cd include; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py private_export
4:46.19 cd mangle; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py private_export
4:49.49 There are no private exports.
4:52.74 There are no private exports.
4:52.74 There are no private exports.
4:52.99 There are no private exports.
4:52.99 cd legacydb; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py private_export
4:53.24 cd builtins; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py private_export
4:56.33 cd include; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py private_export
4:59.39 There are no private exports.
5:02.44 There are no private exports.
5:02.44 There are no private exports.
5:02.70 Creating e:/palemoon-source/obj-i686-pc-mingw32/dist/private/nss
5:02.72 Creating e:/palemoon-source/obj-i686-pc-mingw32/dist/private/nss
8:07.53 There are no private exports.
8:07.55 There are no private exports.
8:07.77 There are no private exports.
8:07.78 Creating e:/palemoon-source/obj-i686-pc-mingw32/dist/private/dbm
8:12.16 There are no private exports.
8:12.53 Creating e:/palemoon-source/obj-i686-pc-mingw32/dist/include/nss
8:12.97 There are no private exports.
8:13.49 There are no private exports.
8:21.86 There are no private exports.
8:22.08 There are no private exports.
8:22.30 There are no private exports.
8:22.55 There are no private exports.
8:22.75 There are no private exports.
8:22.78 There are no private exports.
8:23.00 There are no private exports.
8:23.22 There are no private exports.
8:23.24 There are no private exports.
8:23.45 There are no private exports.
8:23.49 There are no private exports.
8:23.69 There are no private exports.
8:23.70 There are no private exports.
8:23.89 There are no private exports.
8:23.95 There are no private exports.
8:24.14 There are no private exports.
8:24.19 There are no private exports.
8:24.38 There are no private exports.
8:24.60 There are no private exports.
8:24.64 There are no private exports.
8:25.11 There are no private exports.
8:25.31 cd pkix; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py private_export
8:25.33 cd src; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py private_export
8:34.61 There are no private exports.
8:37.31 There are no private exports.
8:37.38 cd mangle; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py export
8:37.66 cd legacydb; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py export
8:40.81 cd legacydb; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py private_export
8:43.91 cd certsel; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py private_export
8:46.92 cd builtins; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py export
8:50.06 There are no private exports.
8:53.06 cd builtins; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py private_export
8:56.49 There are no private exports.
8:56.64 There are no private exports.
8:56.69 There are no private exports.
8:57.14 There are no private exports.
9:00.30 There are no private exports.
9:01.24 There are no private exports.
9:01.30 cd crlsel; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py private_export
9:04.66 cd include; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py export
9:07.92 Creating e:/palemoon-source/obj-i686-pc-mingw32/dist/include/dbm
9:08.16 There are no private exports.
9:09.22 cd checker; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py private_export
9:12.55 cd src; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py export
9:16.31 cd params; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py private_export
9:20.52 cd results; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py private_export
9:24.27 cd store; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py private_export
9:28.02 cd top; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py private_export
9:31.85 cd util; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py private_export
9:35.60 There are no private exports.
9:35.89 cd pkix_pl_nss; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py private_export
9:39.06 cd pki; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py private_export
9:42.85 cd system; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py private_export
9:46.78 cd module; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py private_export
9:50.74 There are no private exports.
9:51.03 There are no private exports.
9:54.22 cd include; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py export
9:54.24 cd include; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py private_export
9:57.42 There are no private exports.
10:00.50 There are no private exports.
10:00.67 cd pkix; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py export
10:03.97 cd certsel; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py export
10:03.97 cd pkix; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py private_export
10:07.16 cd certsel; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py private_export
10:10.27 cd certsel; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py private_export
10:13.30 There are no private exports.
10:16.31 There are no private exports.
10:16.31 There are no private exports.
10:16.72 cd crlsel; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py export
10:16.72 cd crlsel; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py private_export
10:23.06 There are no private exports.
10:23.06 cd crlsel; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py private_export
10:26.22 There are no private exports.
10:26.45 cd checker; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py private_export
10:26.69 cd checker; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py export
10:29.86 There are no private exports.
10:32.80 There are no private exports.
10:33.03 cd checker; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py private_export
10:33.25 cd params; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py private_export
10:36.33 There are no private exports.
10:39.36 There are no private exports.
10:39.56 cd params; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py export
10:39.58 There are no private exports.
10:42.99 cd params; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py private_export
10:43.00 cd results; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py private_export
10:46.33 There are no private exports.
10:49.35 There are no private exports.
10:49.58 cd results; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py export
10:49.80 cd results; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py private_export
10:52.89 There are no private exports.
10:55.91 There are no private exports.
10:56.14 cd store; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py private_export
10:56.39 There are no private exports.
10:59.38 cd store; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py export
10:59.61 cd store; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py private_export
11:02.77 There are no private exports.
11:05.78 There are no private exports.
11:06.02 cd top; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py private_export
11:06.35 cd top; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py export
11:09.35 There are no private exports.
11:12.41 There are no private exports.
11:12.64 cd top; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py private_export
11:12.85 cd util; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py private_export
11:15.99 There are no private exports.
11:19.08 There are no private exports.
11:19.11 There are no private exports.
11:19.63 cd util; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py export
11:19.64 There are no private exports.
11:23.00 There are no private exports.
11:23.16 cd util; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py private_export
11:26.38 There are no private exports.
11:26.60 cd pkix_pl_nss; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py export
11:26.86 There are no private exports.
11:29.91 cd pki; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py private_export
11:29.92 cd pki; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py export
11:36.27 cd pkix_pl_nss; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py private_export
11:36.27 There are no private exports.
11:39.45 There are no private exports.
11:39.67 cd system; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py private_export
11:39.95 cd system; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py export
11:43.05 cd pki; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py private_export
11:46.14 There are no private exports.
11:49.14 There are no private exports.
11:49.35 cd module; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py private_export
11:52.50 There are no private exports.
11:52.50 cd module; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py export
11:55.61 There are no private exports.
11:55.81 cd system; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py private_export
11:55.81 There are no private exports.
11:59.16 There are no private exports.
11:59.16 There are no private exports.
11:59.52 cd module; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py private_export
12:02.64 There are no private exports.
12:02.92 There are no private exports.
12:03.20 There are no private exports.
12:05.14 libs_tier_nss
13:31.85 cd include; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py libs
13:59.19 mkdir: cannot create directory `e:/palemoon-source/obj-i686-pc-mingw32/security/nss/lib/freebl': File exists
13:59.35 cd src; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py libs
14:07.19 cd builtins; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py libs
14:11.20 cd mangle; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py libs
14:20.72 cd legacydb; c:/mozilla-build/python/python.exe e:/palemoon-source/build/pymake/pymake/../make.py libs
14:27.30 tools_tier_nss
14:39.70 Making all in include
14:40.85 Making all in testsuite
14:41.83 Making all in man
14:59.00 export_tier_platform
15:00.58 Generating LALR tables
17:57.22 WARNING:pymake.data:test_taskbar_progress.xul disabled due to regression, see bug 605813
17:57.28 WARNING:pymake.data:test_taskbar_progress.xul disabled due to regression, see bug 605813
17:57.30 WARNING:pymake.data:test_taskbar_progress.xul disabled due to regression, see bug 605813
19:17.77 libs_tier_platform
19:48.33 processing e:/palemoon-source/intl/uconv/src/jar.mn
19:56.06 processing e:/palemoon-source/netwerk/locales/jar.mn
20:56.28 e:/palemoon-source/testing/specialpowers/chrome.manifest: WARNING: no preprocessor directives found
20:56.31 processing e:/palemoon-source/testing/specialpowers/jar.mn
20:57.03 specialpowers/
20:57.03 specialpowers/chrome/
20:57.03 specialpowers/chrome/.mkdir.done
20:57.03 specialpowers/chrome/specialpowers/
20:57.03 specialpowers/chrome/specialpowers/content/
20:57.03 specialpowers/chrome/specialpowers/content/MozillaLogger.js
20:57.03 specialpowers/chrome/specialpowers/content/specialpowers.js
20:57.03 specialpowers/chrome/specialpowers/content/specialpowersAPI.js
20:57.19 specialpowers/chrome/specialpowers/content/SpecialPowersObserverAPI.js
20:57.19 specialpowers/chrome/specialpowers/modules/
20:57.19 specialpowers/chrome/specialpowers/modules/MockFilePicker.jsm
20:57.19 specialpowers/chrome/specialpowers/modules/MockPermissionPrompt.jsm
20:57.20 specialpowers/chrome.manifest
20:57.20 specialpowers/components/
20:57.20 specialpowers/components/SpecialPowersObserver.js
20:57.22 specialpowers/install.rdf
21:15.08 Microsoft (R) File Expansion Utility Version 6.1.7600.16385
21:15.08 Copyright (c) Microsoft Corporation. All rights reserved.
21:15.08
21:15.08 Adding ../../dist/bin\D3DCompiler_43.dll to Extraction Queue
21:15.25
21:15.25 Expanding Files ....
21:15.25
21:15.25 Expanding Files Complete ...
21:15.88 No rule to make target 'C:/Program' needed by ['<command-line>', 'C:/Program']
21:15.88 No rule to make target 'Files' needed by ['<command-line>', 'Files']
21:15.89 No rule to make target '(x86)/Microsoft' needed by ['<command-line>', '(x86)/Microsoft']
21:15.89 No rule to make target 'DirectX' needed by ['<command-line>', 'DirectX']
21:15.89 No rule to make target 'SDK' needed by ['<command-line>', 'SDK']
21:15.89 No rule to make target '(June' needed by ['<command-line>', '(June']
21:15.89 No rule to make target '2010)/lib/x64/d3d9.lib' needed by ['<command-line>', '2010)/lib/x64/d3d9.lib']
21:15.91 No rule to make target '2010)/lib/x64/dxguid.lib' needed by ['<command-line>', '2010)/lib/x64/dxguid.lib']
21:16.31 libGLESv2.dll
21:23.19 Creando biblioteca libGLESv2.lib y objeto libGLESv2.exp
21:23.19
21:23.86 No rule to make target 'C:/Program' needed by ['<command-line>', 'C:/Program']
21:23.86 No rule to make target 'Files' needed by ['<command-line>', 'Files']
21:23.88 No rule to make target '(x86)/Microsoft' needed by ['<command-line>', '(x86)/Microsoft']
21:23.88 No rule to make target 'DirectX' needed by ['<command-line>', 'DirectX']
21:23.88 No rule to make target 'SDK' needed by ['<command-line>', 'SDK']
21:23.88 No rule to make target '(June' needed by ['<command-line>', '(June']
21:23.88 No rule to make target '2010)/lib/x64/d3d9.lib' needed by ['<command-line>', '2010)/lib/x64/d3d9.lib']
21:23.91 libEGL.dll
21:25.17 Creando biblioteca libEGL.lib y objeto libEGL.exp
21:25.17
22:13.94 Traceback (most recent call last):
22:13.94 File "e:/palemoon-source/build/pymake/make.py", line 28, in <module>
22:13.94 pymake.process.ParallelContext.spin()
22:13.94 File "e:\palemoon-source\build\pymake\pymake\process.py", line 527, in spin
22:13.94 c.run()
22:13.94 File "e:\palemoon-source\build\pymake\pymake\process.py", line 457, in run
22:13.94 cb(*args, **kwargs)
22:13.94 File "e:\palemoon-source\build\pymake\pymake\data.py", line 850, in _startdepparallel
22:13.94 dep.make(self.makefile, self.targetstack, weak and self._weakdepfinishedparallel or self._depfinishedparallel)
22:13.94 File "e:\palemoon-source\build\pymake\pymake\data.py", line 1261, in make
22:13.95 cb(error=self.error, didanything=self.didanything)
22:13.95 File "e:\palemoon-source\build\pymake\pymake\data.py", line 868, in _depfinishedparallel
22:13.95 self.resolvecb(error=self.error, didanything=self.didanything)
22:13.95 File "e:\palemoon-source\build\pymake\pymake\data.py", line 762, in resolvecb
22:13.95 self.runnext()
22:13.95 File "e:\palemoon-source\build\pymake\pymake\data.py", line 782, in runnext
22:13.95 self.rlist.pop(0).runcommands(self.indent, self.commandscb)
22:13.95 File "e:\palemoon-source\build\pymake\pymake\data.py", line 952, in runcommands
22:13.97 self._commandcb(False)
22:13.97 File "e:\palemoon-source\build\pymake\pymake\data.py", line 889, in _commandcb
22:13.97 self.commands.pop(0)(self._commandcb)
22:13.97 File "e:\palemoon-source\build\pymake\pymake\data.py", line 1401, in __call__
22:13.97 process.call(self.cline, loc=self.loc, cb=self._cb, context=self.context, **self.kwargs)
22:13.97 File "e:\palemoon-source\build\pymake\pymake\process.py", line 253, in call
22:13.97 cb(res=0)
22:13.97 File "e:\palemoon-source\build\pymake\pymake\data.py", line 1397, in _cb
22:13.99 self.usercb(error=False)
22:13.99 File "e:\palemoon-source\build\pymake\pymake\data.py", line 889, in _commandcb
22:13.99 self.commands.pop(0)(self._commandcb)
22:13.99 File "e:\palemoon-source\build\pymake\pymake\data.py", line 1401, in __call__
22:13.99 process.call(self.cline, loc=self.loc, cb=self._cb, context=self.context, **self.kwargs)
22:13.99 File "e:\palemoon-source\build\pymake\pymake\process.py", line 262, in call
22:13.99 command.main(argv[2:], env, cwd, cb)
22:13.99 File "e:\palemoon-source\build\pymake\pymake\command.py", line 271, in main
22:13.99 _MakeContext(makeflags, makelevel, workdir, context, env, targets, options, ostmts, overrides, cb)
22:13.99 File "e:\palemoon-source\build\pymake\pymake\command.py", line 94, in __init__
22:14.00 self.remakecb(True)
22:14.00 File "e:\palemoon-source\build\pymake\pymake\command.py", line 124, in remakecb
22:14.00 self.makefile.include(f)
22:14.00 File "e:\palemoon-source\build\pymake\pymake\data.py", line 1768, in include
22:14.00 stmts.execute(self, weak=weak)
22:14.00 File "e:\palemoon-source\build\pymake\pymake\parserdata.py", line 988, in execute
22:14.00 s.execute(makefile, context)
22:14.00 File "e:\palemoon-source\build\pymake\pymake\parserdata.py", line 794, in execute
22:14.02 makefile.include(f, self.required, loc=self.exp.loc, weak=self.weak)
22:14.02 File "e:\palemoon-source\build\pymake\pymake\data.py", line 1768, in include
22:14.02 stmts.execute(self, weak=weak)
22:14.02 File "e:\palemoon-source\build\pymake\pymake\parserdata.py", line 988, in execute
22:14.02 s.execute(makefile, context)
22:14.02 File "e:\palemoon-source\build\pymake\pymake\parserdata.py", line 649, in execute
22:14.03 statements.execute(makefile, context)
22:14.03 File "e:\palemoon-source\build\pymake\pymake\parserdata.py", line 988, in execute
22:14.03 s.execute(makefile, context)
22:14.03 File "e:\palemoon-source\build\pymake\pymake\parserdata.py", line 649, in execute
22:14.03 statements.execute(makefile, context)
22:14.03 File "e:\palemoon-source\build\pymake\pymake\parserdata.py", line 988, in execute
22:14.03 s.execute(makefile, context)
22:14.03 File "e:\palemoon-source\build\pymake\pymake\parserdata.py", line 649, in execute
22:14.05 statements.execute(makefile, context)
22:14.05 File "e:\palemoon-source\build\pymake\pymake\parserdata.py", line 988, in execute
22:14.05 s.execute(makefile, context)
22:14.05 File "e:\palemoon-source\build\pymake\pymake\parserdata.py", line 794, in execute
22:14.05 makefile.include(f, self.required, loc=self.exp.loc, weak=self.weak)
22:14.05 File "e:\palemoon-source\build\pymake\pymake\data.py", line 1764, in include
22:14.06 stmts = parser.parsedepfile(fspath)
22:14.06 File "e:\palemoon-source\build\pymake\pymake\parser.py", line 397, in parsedepfile
22:14.06 target, deps = line.split(":", 1)
22:14.06 ValueError: need more than 1 value to unpack
Single process terminated successfully
22:15.25 0 compiler warnings present.
-
- Pale Moon guru
- Posts: 35650
- Joined: 2011-08-28, 17:27
- Location: Motala, SE
Re: Build with VS2010
The problem seems to be here:
Sorry to say but you're not even close to finishing the build at that point.
Did you set up your build environment correctly? e.g. following viewtopic.php?f=19&t=4166
Did you use the correct batch file to launch your build environment?
Code: Select all
21:23.86 No rule to make target 'C:/Program' needed by ['<command-line>', 'C:/Program']
21:23.86 No rule to make target 'Files' needed by ['<command-line>', 'Files']
21:23.88 No rule to make target '(x86)/Microsoft' needed by ['<command-line>', '(x86)/Microsoft']
21:23.88 No rule to make target 'DirectX' needed by ['<command-line>', 'DirectX']
21:23.88 No rule to make target 'SDK' needed by ['<command-line>', 'SDK']
21:23.88 No rule to make target '(June' needed by ['<command-line>', '(June']
21:23.88 No rule to make target '2010)/lib/x64/d3d9.lib' needed by ['<command-line>', '2010)/lib/x64/d3d9.lib']
Did you set up your build environment correctly? e.g. following viewtopic.php?f=19&t=4166
Did you use the correct batch file to launch your build environment?
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
Re: Build with VS2010
That is like the ONE non-breaking "No rule to make target" error in the entire build procedure. I get this.. never really found out why.. I think it because where ever it is it isn't quoted properly given the way it is totally split up. Likely it corrects its self with a proper quoted one which is why it doesn't actually cause a build failure.
Moonchild is however correct.. That is happening around libEGL which is quite early in the process.. The Python error is what i am most concerned with.. I am not sure if it IS actually happening because of something attached libEGL or just AFTER it. Or what is causing it.
What I can tell you is the DX lib is non-fatal and likely NOT the cause.
EDIT: from config.status
The var's value is indeed unquoted for some reason. Still it remains non-fatal. Something else is going on.
Moonchild is however correct.. That is happening around libEGL which is quite early in the process.. The Python error is what i am most concerned with.. I am not sure if it IS actually happening because of something attached libEGL or just AFTER it. Or what is causing it.
What I can tell you is the DX lib is non-fatal and likely NOT the cause.
EDIT: from config.status
Code: Select all
(''' MOZ_DIRECTX_SDK_PATH ''', r''' C:/Program Files (x86)/Microsoft DirectX SDK (June 2010) '''),
Re: Build with VS2010
Hi, thanks for reply
This is the steps i made
1 - Install Windows 7 x64 (lucky me, is a Pentium 4 775)
2 - Install Windows 7 SP1
3 - Install Visual Studio 2012 express
4 - Install the update 4
5 - Install June 2010 DirectX SDK
6 - Install the MozillaBuild 1.10 in c:\mozilla-build
7 - Download latest palemoon source
8 - Unpack in e:\palemoon-source
9 - Create a file .mozconfig (i create in a terminal, "copy con .mozconfig") and add the text
10 - Run start-shell-msvc2012-x64.bat
11 - "cd /e/palemoon-source" "./mach build"
If i mistake in one step, for sure his is the problem
Matt A Tobin thanks for the tip, I check for all config.status files, and add quotes to long file name Program File, but same problem. Maybe i forget one config.status or something, tomorrow i will check again
Thanks
This is the steps i made
1 - Install Windows 7 x64 (lucky me, is a Pentium 4 775)
2 - Install Windows 7 SP1
3 - Install Visual Studio 2012 express
4 - Install the update 4
5 - Install June 2010 DirectX SDK
6 - Install the MozillaBuild 1.10 in c:\mozilla-build
7 - Download latest palemoon source
8 - Unpack in e:\palemoon-source
9 - Create a file .mozconfig (i create in a terminal, "copy con .mozconfig") and add the text
Code: Select all
ac_add_options --target=x86_64-pc-mingw32
ac_add_options --host=x86_64-pc-mingw32
mk_add_options MOZ_CO_PROJECT=browser
ac_add_options --enable-application=browser
ac_add_options --enable-optimize="-O2"
ac_add_options --enable-jemalloc
ac_add_options --enable-shared-js
WIN32_REDIST_DIR=$VCINSTALLDIR/redist/x64/Microsoft.VC110.CRT
11 - "cd /e/palemoon-source" "./mach build"
If i mistake in one step, for sure his is the problem
Matt A Tobin thanks for the tip, I check for all config.status files, and add quotes to long file name Program File, but same problem. Maybe i forget one config.status or something, tomorrow i will check again
Thanks
Re: Build with VS2010
One.. You can't alter config.status it will be overwritten. You should NEVER attempt to change any generated obj-dir file.
Two.. You have insufficient memory for a successful compile operation.
Three.. Your .mozconfig is insufficient.
Two.. You have insufficient memory for a successful compile operation.
Three.. Your .mozconfig is insufficient.
-
- Pale Moon guru
- Posts: 35650
- Joined: 2011-08-28, 17:27
- Location: Motala, SE
Re: Build with VS2010
Try adding the following to your mozconfig; I think it borks on the tests (you don't want to build those on an underpowered machine to begin with unless you have a week to spare ;P )
Code: Select all
ac_add_options --disable-debug
ac_add_options --disable-tests
ac_add_options --disable-mochitests
ac_add_options --enable-strip
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite