Re: Firefox 38.8.0 Beta 7 released

On 2016-06-03 03:40:40 +0000, Dave Yeo said:

> OK, I'll note that by having the configure options in a mozconfig means
> just running ../configure rather then passing the options and exports
> can also be added.

Yes, but that's arguable since these options are build site specific, 
not OS/2-specific. I.e. if you don't do a "canonical" build, you don't 
have to use all these options at all. And if you do, you should use 
.spec (as this is where the "canonical" build originates from).

>  Less chance of a typo and easier instructions for others.
> I see your still targeting i486. I'm targeting i686 and tuning for
> generic, which may benefit AMD more.

Yes, but again, this will be solved automatically once we switch to RPM 
for Firefox (our build bot produces i686 and pentium4 packages 
automatically for everything that we build at BWW). However, if you 
provide your mozconfig patches that do some "generic" OS/2 build, I 
will consider applying them in our repo.
> 
> I note that Fedora's RPM spec file creates a mozconfig and then uses
> client.mk to build. Another advantage of client.mk is it takes care of
> all the autoconf213 configures, of which there is 4 when building SM or
> TB. The spec also uses mach to run the tests.

I will note that too when I do it. May be I will switch to 
mozconfig/mach as well then :) Another reason I don't use mach is that 
I was lazy to find out on how to do out-of-tree builds with it.

> Client.mk seems to work fine here, mach clobber is good for cleaning the
> object directory while mach build just calls client.mk.

I guess I don't need this with out-of-tree builds.
> 
> Things have improved, Comm-centrals configure basically just calls
> Mozilla's configure now instead of mostly duplicating it along with
> simplifying CCs build and config directories. The duplication is mostly
> in the individual app directories.

I see. Already something.

> The TB and SM maintainers were trying to get Comm-Central merged into
> Mozilla-Central but that was rejected along with a blanket statement
> that Mozilla developers can't spend _any_ paid time on Comm-Central and
> basically have orphaned Thunderbird (and SeaMonkey) so right now they
> seem to have forked Mozilla-Central, which if the OS/2 fork of Mozilla
> survives past 45ESR could be a problem.

Hmmm. I see. Not good.

> Past 45ESR, they're making Rust a requirement, which sounds like a bitch
> to bootstrap as most versions, including point releases can only build
> from the previous version, something like 31 steps required to bring it
> up to date, and that's after porting LLVM.
> They're also finally ripping out autoconf so lots of build changes after
> 45esr.

Thanks for this info. But we will eventually sort it out once (and if) 
we are there :) There had been more difficult problems in the past :)


-- 
Kind regards,
Dmitriy Kuminov
CPO of bww bitwise works GmbH