>
> On 2019-Jan-1, at 10:21, bob prohaska wrote:
>
> > On Tue, Dec 18, 2018 at 09:49:03AM -0800, bob prohaska wrote:
> >>
> >> Setting MAKE_JOBS_NUMBER_LIMIT=2 allowed www/chromium to compile
> >> successfully over
> >> several days. The -DBATCH option was used, in hopes it'd fetch the right
On Tue, Jan 01, 2019 at 03:14:26PM -0800, Mark Millard wrote:
>
>
> On 2019-Jan-1, at 10:21, bob prohaska wrote:
>
> > On Tue, Dec 18, 2018 at 09:49:03AM -0800, bob prohaska wrote:
> >
> >
> > As a further test, I'ved added two additional USB flash swap devices and am
> > re-running
> > the
On 2019-Jan-1, at 10:21, bob prohaska wrote:
> On Tue, Dec 18, 2018 at 09:49:03AM -0800, bob prohaska wrote:
>>
>> Setting MAKE_JOBS_NUMBER_LIMIT=2 allowed www/chromium to compile
>> successfully over
>> several days. The -DBATCH option was used, in hopes it'd fetch the right
>> options.
On Tue, Dec 18, 2018 at 09:49:03AM -0800, bob prohaska wrote:
>
> Setting MAKE_JOBS_NUMBER_LIMIT=2 allowed www/chromium to compile successfully
> over
> several days. The -DBATCH option was used, in hopes it'd fetch the right
> options.
>
Just for fun I added a mechanical hard disk with a 4
On Wed, Dec 19, 2018 at 05:14:07PM +1100, Brian Scott wrote:
>
> I believe the problem now is that support for builtin sound on the RPI3
> is still a work in progress (it goes through the HDMI subsystem and I
> think it was a 32 vs. 64 bit issue but is a mystery to me beyond that).
>
I infer
bob prohaska writes:
> On Tue, Dec 18, 2018 at 11:41:44PM +, Jamie Landeg-Jones wrote:
>
>> bob prohaska wrote:
>>
>> > Setting MAKE_JOBS_NUMBER_LIMIT=2 allowed www/chromium to compile
>> > successfully over
>> > several days. The -DBATCH option was used, in hopes it'd fetch the right
>>
On Tue, Dec 18, 2018 at 11:41:44PM +, Jamie Landeg-Jones wrote:
> bob prohaska wrote:
>
> > Setting MAKE_JOBS_NUMBER_LIMIT=2 allowed www/chromium to compile
> > successfully over
> > several days. The -DBATCH option was used, in hopes it'd fetch the right
> > options.
>
> Use "make
bob prohaska wrote:
> Setting MAKE_JOBS_NUMBER_LIMIT=2 allowed www/chromium to compile successfully
> over
> several days. The -DBATCH option was used, in hopes it'd fetch the right
> options.
Use "make config-recursive" before you start. It will present to you upfront all
the option screens
On Fri, Dec 14, 2018 at 05:59:21AM +0100, Jan Beich wrote:
>
> MAKE_JOBS_NUMBER_LIMIT is a user variable, so you can either set in
> make.conf or Makefile.local e.g.,
>
> $ cat <<\. >>${__MAKE_CONF:-/etc/make.conf}
> .if ${.CURDIR:M*/www/chromium}
> MAKE_JOBS_NUMBER_LIMIT=2
> .endif
Setting
bob prohaska writes:
> On Wed, Dec 12, 2018 at 09:25:04PM +0100, Christoph Moench-Tegeder wrote:
>
>> ## bob prohaska (f...@www.zefox.net):
>>
>> > > See bsd.ports.mk: DISABLE_MAKE_JOBS (as in "make -DDISABLE_MAKE_JOBS").
>> > >
>> > Thank you, I think that's the information needed. Come to
On Wed, Dec 12, 2018 at 09:25:04PM +0100, Christoph Moench-Tegeder wrote:
> ## bob prohaska (f...@www.zefox.net):
>
> > > See bsd.ports.mk: DISABLE_MAKE_JOBS (as in "make -DDISABLE_MAKE_JOBS").
> > >
> > Thank you, I think that's the information needed. Come to think of it,
> > will the -j
## Ian Lepore (i...@freebsd.org):
> That's a bit of a harsh tone to take with a user who has questions.
Sorry, the day is getting long (and it doesn't sound that harsh in german,
it definitively wasn't meant that harsh).
> If
> Bob was an aspiring ports developer, maybe a response like that
Kurt Jaeger wrote on 2018/12/12 19:46:
Hi!
The system in question is an RPI3 running r341643.
That will hurt. A regular chromium build takes about 16 CPU-hours on
my fairly modern i7 CPU, SSDs and large RAM. Parallel compilation helps
a lot, keeping 16 CPU threads busy and my feet warm
## bob prohaska (f...@www.zefox.net):
> > See bsd.ports.mk: DISABLE_MAKE_JOBS (as in "make -DDISABLE_MAKE_JOBS").
> >
> Thank you, I think that's the information needed. Come to think of it,
> will the -j option, such as -j2, work in this situation also? Two threads
> are much better than one
On Wed, Dec 12, 2018 at 07:41:49PM +0100, Christoph Moench-Tegeder wrote:
> ## bob prohaska (f...@www.zefox.net):
>
> > How much memory should be required for
> > make -DBATCH
> > in www/chromium?
>
> Quite a lot, multiple GBs.
>
>
> I'm not even sure if your SD card will survive that :)
>
## Kurt Jaeger (p...@freebsd.org):
> How can this parallel compilation be configured for chromium in poudriere ?
Look for ALLOW_MAKE_JOBS and/or ALLOW_MAKE_JOBS_PACKAGES in poudriere.conf.
That's what does the trick for my poudriere :)
Regards,
Christoph
--
Spare Space.
Hi!
> > The system in question is an RPI3 running r341643.
>
> That will hurt. A regular chromium build takes about 16 CPU-hours on
> my fairly modern i7 CPU, SSDs and large RAM. Parallel compilation helps
> a lot, keeping 16 CPU threads busy and my feet warm (building chromium
> alone takes 1
## bob prohaska (f...@www.zefox.net):
> How much memory should be required for
> make -DBATCH
> in www/chromium?
Quite a lot, multiple GBs.
> The system in question is an RPI3 running r341643.
That will hurt. A regular chromium build takes about 16 CPU-hours on
my fairly modern i7 CPU, SSDs
How much memory should be required for
make -DBATCH
in www/chromium?
Make issues warnings about disk space required, but I don't recall seeing
anything about RAM or swap.
The system in question is an RPI3 running r341643. Make reached part
[18416/30819], at which point it seems to have
19 matches
Mail list logo
