Out of the box build failure

Users and developers helping users with generic and technical Pale Moon issues on all operating systems.

Moderator: trava90

Forum rules
This board is for technical/general usage questions and troubleshooting for the Pale Moon browser only.
Technical issues and questions not related to the Pale Moon browser should be posted in other boards!
Please keep off-topic and general discussion out of this board, thank you!
Pelican
Fanatic
Fanatic
Posts: 220
Joined: 2018-02-23, 06:51

Out of the box build failure

Unread post by Pelican » 2018-02-24, 08:56

I will eventually be passing this project onto our developer, but in the meantime I have a problem building out-of-the-box.

After I discovered that docs recommending using VS 2012 was for earlier builds and that the latest build requires VS 2013 I got underway and after 60 minutes of build time arrived at this error...

Image

How to fix this error?
Last edited by Pelican on 2018-02-24, 08:57, edited 2 times in total.

Fedor2

Re: Out of the box build failure

Unread post by Fedor2 » 2018-02-24, 09:41

Screen with error endings is irrelevant , you put it with the begining of the error.
In the output directory, that log file was been written with all screen data, find it then find inside it the error encounter.

Pelican
Fanatic
Fanatic
Posts: 220
Joined: 2018-02-23, 06:51

Re: Out of the box build failure

Unread post by Pelican » 2018-02-24, 09:47

Where can I find the log file?

Fedor2

Re: Out of the box build failure

Unread post by Fedor2 » 2018-02-24, 09:57

It inside the top three directories of the output directory, something like mozbuild, do not recall actually, i shall reach my job machine only on monday to see exact. Suppose you know where to look the output directory.
Last edited by Fedor2 on 2018-02-24, 09:59, edited 1 time in total.

Pelican
Fanatic
Fanatic
Posts: 220
Joined: 2018-02-23, 06:51

Re: Out of the box build failure

Unread post by Pelican » 2018-02-24, 10:01

Nope, no idea. There is nothing like an output folder.

Fedor2

Re: Out of the box build failure

Unread post by Fedor2 » 2018-02-24, 12:30

It is named object directory
may be helping
https://firefox-source-docs.mozilla.org ... -directory
search there for *log*.*json*

Pelican
Fanatic
Fanatic
Posts: 220
Joined: 2018-02-23, 06:51

Re: Out of the box build failure

Unread post by Pelican » 2018-02-24, 20:23

At C:\palemoon-source\obj-x86_64-pc-mingw32\.mozbuild\warnings.json ???

But there are 3,695 lines of warnings.

Aha! Just noticed the "latest" build instructions recommending MozBuild 2.1 (had been using 1.10) and will see if that makes a difference.
Last edited by Pelican on 2018-02-24, 21:03, edited 2 times in total.

Pelican
Fanatic
Fanatic
Posts: 220
Joined: 2018-02-23, 06:51

Re: Out of the box build failure

Unread post by Pelican » 2018-02-24, 21:49

Success :clap:

But why 437 compiler warnings?
Last edited by Pelican on 2018-02-24, 21:50, edited 1 time in total.

User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 35647
Joined: 2011-08-28, 17:27
Location: Motala, SE

Re: Out of the box build failure

Unread post by Moonchild » 2018-02-26, 04:54

WilliamK wrote:But why 437 compiler warnings?
Simply put: because you're compiling 15 million lines of cross-platform/cross-compiler code. Many of the warnings are not in any way critical, are deprecation warnings, code style warnings or other trivial things like macro redefinitions etc.
"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