Re: Failure building firefox-65.0

[Chavdar Ivanov <ci4ic4%gmail.com@localhost>]

It's not that bad. My build host is an HP EliteBook laptop with a
broken display and FireGL graphics card, I have to disable radeon* to
get it to boot; it has one 120GB SSD, 32GB eMMC and 250 GB hard disk,
the latter only holds GPT slices for Xen DOMus, a couple of slices for
distfiles and packages/All etc. It builds -current several times a
week, followed by immediate inplace update. About once a week I update
/usr/pkgsrc and /usr/pkgsrc/wip, followed by 'pkg_rolling-replace';
doing it often keeps the runs shorter. The packages built on this
machine are served to the other NetBSD -current hosts on my network
over ftp using pkgin. I've never done a bulk build, no need for it.
Rust takes indeed an inordinate amount of time to build and I have
seen quite a few cargo hungs, but what I can gather from people using
it is that it is apparently an excellent systems programming language.

On Fri, 1 Feb 2019 at 22:51, bch <brad.harder%gmail.com@localhost> wrote:
>
>
>
> On Fri, Feb 1, 2019 at 23:17 Chavdar Ivanov <ci4ic4%gmail.com@localhost> wrote:
>>
>> Eventually completed and working fine. First attempt had cargo hung, I
>> waited for parhaps an hour, there was no activity, so I interrupted
>> and restarted make (without cleaning, I've had that previously).
>
>
> This build (because of rust) is so crazy. It’s nearly at the place where it alone needs a dedicated build/storage infrastructure.
>
> Is there already (or interest in) a build for we on nbsd -current and pkgsrc -current? If there’s something available, I’d love to know because it’s at least a multi-day process for me if I’m lucky.
>
> -bch
>
>
>>
>> On Fri, 1 Feb 2019 at 17:29, Chavdar Ivanov <ci4ic4%gmail.com@localhost> wrote:
>> >
>> > I had a look at this report and tried to figure out how to apply the
>> > suggested workaround, but the pointed out file was missing from this
>> > version. Anyway, Ryo@ has updated firefox to 65.0nb1 and now 'make
>> > configure' succeeds. I am waiting for the build to complete now.
>> >
>> > On Fri, 1 Feb 2019 at 16:52, Jan Beich <jbeich%freebsd.org@localhost> wrote:
>> > >
>> > > Chavdar Ivanov <ci4ic4%gmail.com@localhost> writes:
>> > >
>> > > > Hi,
>> > > >
>> > > > I got:
>> > > > ..........
>> > > >   File "/usr/pkg/.wrkobjdir/www/firefox/work/firefox-65.0/configure.py",
>> > > > line 118, in config_status
>> > > >                     [0/1910]
>> > > >     return config_status(args=[], **encode(sanitized_config, encoding))
>> > > >   File "/usr/pkg/.wrkobjdir/www/firefox/work/firefox-65.0/python/mozbuild/mozbuild/config_status.py",
>> > > > line 143, in config_status
>> > > >     definitions = list(definitions)
>> > > >   File "/usr/pkg/.wrkobjdir/www/firefox/work/firefox-65.0/python/mozbuild/mozbuild/frontend/emitter.py",
>> > > > line 172, in emit
>> > > >     for out in output:
>> > > >   File "/usr/pkg/.wrkobjdir/www/firefox/work/firefox-65.0/python/mozbuild/mozbuild/frontend/reader.py",
>> > > > line 880, in read_topsrcdir
>> > > >     for r in self.read_mozbuild(path, self.config):
>> > > >   File "/usr/pkg/.wrkobjdir/www/firefox/work/firefox-65.0/python/mozbuild/mozbuild/frontend/reader.py",
>> > > > line 1047, in read_mozbuild
>> > > >     raise bre
>> > > > mozbuild.frontend.reader.BuildReaderError:
>> > > > ==============================
>> > > > FATAL ERROR PROCESSING MOZBUILD FILE
>> > > > ==============================
>> > > >
>> > > > The error occurred while processing the following file:
>> > > >
>> > > >     /usr/pkg/.wrkobjdir/www/firefox/work/firefox-65.0/mozglue/misc/moz.build
>> > > >
>> > > > A moz.build file called the error() function.
>> > > >
>> > > > The error it encountered is:
>> > > >
>> > > >     No TimeStamp implementation on this platform.  Build will not succeed
>> > > >
>> > > > Correct the error condition and try again.
>> > > > .......
>> > > >
>> > > > I have PYTHON_VERSION_DEFAULT=37, if this is relevant. The platform is
>> > > > amd64, -current from yestrday.
>> > >
>> > > Are you using LLD linker? If so FreeBSD has similar issue.
>> > > https://bugzilla.mozilla.org/show_bug.cgi?id=1516830
>> > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233707
>> >
>> >
>> >
>> > --
>> > ----
>>
>>
>>
>> --
>> ----



-- 
----