* [Buildroot] [PATCH 1/1] fs/common.mk: enable multithreaded xz compression
@ 2019-01-21 2:07 james.hilliard1 at gmail.com
2019-01-21 14:02 ` Matthew Weber
0 siblings, 1 reply; 14+ messages in thread
From: james.hilliard1 at gmail.com @ 2019-01-21 2:07 UTC (permalink / raw)
To: buildroot
From: James Hilliard <james.hilliard1@gmail.com>
xz help indicates only 1 thread is used unless we set threads:
-T, --threads=NUM use at most NUM threads; the default is 1; set to 0
to use as many threads as there are processor cores
Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
---
fs/common.mk | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/common.mk b/fs/common.mk
index a560417..6a57121 100644
--- a/fs/common.mk
+++ b/fs/common.mk
@@ -106,7 +106,7 @@ endif
ifeq ($$(BR2_TARGET_ROOTFS_$(2)_XZ),y)
ROOTFS_$(2)_DEPENDENCIES += host-xz
ROOTFS_$(2)_COMPRESS_EXT = .xz
-ROOTFS_$(2)_COMPRESS_CMD = xz -9 -C crc32 -c
+ROOTFS_$(2)_COMPRESS_CMD = xz -T 0 -9 -C crc32 -c
endif
$$(BINARIES_DIR)/$$(ROOTFS_$(2)_FINAL_IMAGE_NAME): ROOTFS=$(2)
--
2.7.4
^ permalink raw reply related [flat|nested] 14+ messages in thread
* [Buildroot] [PATCH 1/1] fs/common.mk: enable multithreaded xz compression
2019-01-21 2:07 [Buildroot] [PATCH 1/1] fs/common.mk: enable multithreaded xz compression james.hilliard1 at gmail.com
@ 2019-01-21 14:02 ` Matthew Weber
2019-01-21 14:05 ` James Hilliard
0 siblings, 1 reply; 14+ messages in thread
From: Matthew Weber @ 2019-01-21 14:02 UTC (permalink / raw)
To: buildroot
James,
On Sun, Jan 20, 2019 at 8:08 PM <james.hilliard1@gmail.com> wrote:
>
> From: James Hilliard <james.hilliard1@gmail.com>
>
> xz help indicates only 1 thread is used unless we set threads:
> -T, --threads=NUM use at most NUM threads; the default is 1; set to 0
> to use as many threads as there are processor cores
>
It's good to see xz now has support, but I assume there is a minimum
version? We ran into this outside of Builroot on a project where we
conditionally used the parallel "pxz" tool when available, as "xz"
didn't have the -T support consistently in distros yet.
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
> ---
> fs/common.mk | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/common.mk b/fs/common.mk
> index a560417..6a57121 100644
> --- a/fs/common.mk
> +++ b/fs/common.mk
> @@ -106,7 +106,7 @@ endif
> ifeq ($$(BR2_TARGET_ROOTFS_$(2)_XZ),y)
> ROOTFS_$(2)_DEPENDENCIES += host-xz
> ROOTFS_$(2)_COMPRESS_EXT = .xz
> -ROOTFS_$(2)_COMPRESS_CMD = xz -9 -C crc32 -c
> +ROOTFS_$(2)_COMPRESS_CMD = xz -T 0 -9 -C crc32 -c
> endif
>
> $$(BINARIES_DIR)/$$(ROOTFS_$(2)_FINAL_IMAGE_NAME): ROOTFS=$(2)
> --
> 2.7.4
>
Thanks for sending the patch!
Matt
^ permalink raw reply [flat|nested] 14+ messages in thread
* [Buildroot] [PATCH 1/1] fs/common.mk: enable multithreaded xz compression
2019-01-21 14:02 ` Matthew Weber
@ 2019-01-21 14:05 ` James Hilliard
2019-01-21 14:28 ` [Buildroot] [External] " Matthew Weber
2019-01-21 17:39 ` [Buildroot] " Peter Korsgaard
0 siblings, 2 replies; 14+ messages in thread
From: James Hilliard @ 2019-01-21 14:05 UTC (permalink / raw)
To: buildroot
On Mon, Jan 21, 2019 at 7:02 AM Matthew Weber <matthew.weber@collins.com> wrote:
>
> James,
>
>
> On Sun, Jan 20, 2019 at 8:08 PM <james.hilliard1@gmail.com> wrote:
> >
> > From: James Hilliard <james.hilliard1@gmail.com>
> >
> > xz help indicates only 1 thread is used unless we set threads:
> > -T, --threads=NUM use at most NUM threads; the default is 1; set to 0
> > to use as many threads as there are processor cores
> >
>
> It's good to see xz now has support, but I assume there is a minimum
> version? We ran into this outside of Builroot on a project where we
> conditionally used the parallel "pxz" tool when available, as "xz"
> didn't have the -T support consistently in distros yet.
I thought it was using the version compiled by buildroot.
Isn't that what host-xz is being used for?
>
> > Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
> > ---
> > fs/common.mk | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/fs/common.mk b/fs/common.mk
> > index a560417..6a57121 100644
> > --- a/fs/common.mk
> > +++ b/fs/common.mk
> > @@ -106,7 +106,7 @@ endif
> > ifeq ($$(BR2_TARGET_ROOTFS_$(2)_XZ),y)
> > ROOTFS_$(2)_DEPENDENCIES += host-xz
> > ROOTFS_$(2)_COMPRESS_EXT = .xz
> > -ROOTFS_$(2)_COMPRESS_CMD = xz -9 -C crc32 -c
> > +ROOTFS_$(2)_COMPRESS_CMD = xz -T 0 -9 -C crc32 -c
> > endif
> >
> > $$(BINARIES_DIR)/$$(ROOTFS_$(2)_FINAL_IMAGE_NAME): ROOTFS=$(2)
> > --
> > 2.7.4
> >
>
> Thanks for sending the patch!
> Matt
^ permalink raw reply [flat|nested] 14+ messages in thread
* [Buildroot] [External] Re: [PATCH 1/1] fs/common.mk: enable multithreaded xz compression
2019-01-21 14:05 ` James Hilliard
@ 2019-01-21 14:28 ` Matthew Weber
2019-01-21 17:39 ` [Buildroot] " Peter Korsgaard
1 sibling, 0 replies; 14+ messages in thread
From: Matthew Weber @ 2019-01-21 14:28 UTC (permalink / raw)
To: buildroot
On Mon, Jan 21, 2019 at 8:05 AM James Hilliard
<james.hilliard1@gmail.com> wrote:
>
> On Mon, Jan 21, 2019 at 7:02 AM Matthew Weber <matthew.weber@collins.com> wrote:
> >
> > James,
> >
> >
> > On Sun, Jan 20, 2019 at 8:08 PM <james.hilliard1@gmail.com> wrote:
> > >
> > > From: James Hilliard <james.hilliard1@gmail.com>
> > >
> > > xz help indicates only 1 thread is used unless we set threads:
> > > -T, --threads=NUM use at most NUM threads; the default is 1; set to 0
> > > to use as many threads as there are processor cores
> > >
> >
> > It's good to see xz now has support, but I assume there is a minimum
> > version? We ran into this outside of Builroot on a project where we
> > conditionally used the parallel "pxz" tool when available, as "xz"
> > didn't have the -T support consistently in distros yet.
> I thought it was using the version compiled by buildroot.
> Isn't that what host-xz is being used for?
Ah, true. I had glanced at the dependency checking scripts but we
always built it based on the fs/common.mk dependency on host-xz so
that is correct.
One other comment would be that "0" wouldn't be ideal on a shared
machine. Suggest limiting to $(PARALLEL_JOBS) which is used in other
filesystem creation (grep fs folder for an example in iso9660 or
squashfs).
Reviewed-by: Matthew Weber <matthew.weber@rockwellcollins.com>
^ permalink raw reply [flat|nested] 14+ messages in thread
* [Buildroot] [PATCH 1/1] fs/common.mk: enable multithreaded xz compression
2019-01-21 14:05 ` James Hilliard
2019-01-21 14:28 ` [Buildroot] [External] " Matthew Weber
@ 2019-01-21 17:39 ` Peter Korsgaard
2019-01-21 21:34 ` James Hilliard
2019-01-26 14:06 ` Thomas Petazzoni
1 sibling, 2 replies; 14+ messages in thread
From: Peter Korsgaard @ 2019-01-21 17:39 UTC (permalink / raw)
To: buildroot
>>>>> "James" == James Hilliard <james.hilliard1@gmail.com> writes:
> On Mon, Jan 21, 2019 at 7:02 AM Matthew Weber <matthew.weber@collins.com> wrote:
>>
>> James,
>>
>>
>> On Sun, Jan 20, 2019 at 8:08 PM <james.hilliard1@gmail.com> wrote:
>> >
>> > From: James Hilliard <james.hilliard1@gmail.com>
>> >
>> > xz help indicates only 1 thread is used unless we set threads:
>> > -T, --threads=NUM use at most NUM threads; the default is 1; set to 0
>> > to use as many threads as there are processor cores
>> >
>>
>> It's good to see xz now has support, but I assume there is a minimum
>> version? We ran into this outside of Builroot on a project where we
>> conditionally used the parallel "pxz" tool when available, as "xz"
>> didn't have the -T support consistently in distros yet.
> I thought it was using the version compiled by buildroot.
> Isn't that what host-xz is being used for?
Yes, correct. Do you know if the -T 0 option generates identical output
as -T 1? Otherwise we may want to disable it for reproducible builds.
--
Bye, Peter Korsgaard
^ permalink raw reply [flat|nested] 14+ messages in thread
* [Buildroot] [PATCH 1/1] fs/common.mk: enable multithreaded xz compression
2019-01-21 17:39 ` [Buildroot] " Peter Korsgaard
@ 2019-01-21 21:34 ` James Hilliard
2019-01-26 14:06 ` Thomas Petazzoni
1 sibling, 0 replies; 14+ messages in thread
From: James Hilliard @ 2019-01-21 21:34 UTC (permalink / raw)
To: buildroot
On Mon, Jan 21, 2019 at 10:39 AM Peter Korsgaard <peter@korsgaard.com> wrote:
>
> >>>>> "James" == James Hilliard <james.hilliard1@gmail.com> writes:
>
> > On Mon, Jan 21, 2019 at 7:02 AM Matthew Weber <matthew.weber@collins.com> wrote:
> >>
> >> James,
> >>
> >>
> >> On Sun, Jan 20, 2019 at 8:08 PM <james.hilliard1@gmail.com> wrote:
> >> >
> >> > From: James Hilliard <james.hilliard1@gmail.com>
> >> >
> >> > xz help indicates only 1 thread is used unless we set threads:
> >> > -T, --threads=NUM use at most NUM threads; the default is 1; set to 0
> >> > to use as many threads as there are processor cores
> >> >
> >>
> >> It's good to see xz now has support, but I assume there is a minimum
> >> version? We ran into this outside of Builroot on a project where we
> >> conditionally used the parallel "pxz" tool when available, as "xz"
> >> didn't have the -T support consistently in distros yet.
>
> > I thought it was using the version compiled by buildroot.
> > Isn't that what host-xz is being used for?
>
> Yes, correct. Do you know if the -T 0 option generates identical output
> as -T 1? Otherwise we may want to disable it for reproducible builds.
I think it doesn't generate identical output, I wonder if it would be
a good idea to make all these compression flags configurable.
One issue I'm running across is that my test builds take at least 5
minutes or so to compress, having a way to set different xz flags
between test and production builds would be handy.
>
> --
> Bye, Peter Korsgaard
^ permalink raw reply [flat|nested] 14+ messages in thread
* [Buildroot] [PATCH 1/1] fs/common.mk: enable multithreaded xz compression
2019-01-21 17:39 ` [Buildroot] " Peter Korsgaard
2019-01-21 21:34 ` James Hilliard
@ 2019-01-26 14:06 ` Thomas Petazzoni
2019-01-26 19:31 ` James Hilliard
2019-01-27 22:06 ` Peter Korsgaard
1 sibling, 2 replies; 14+ messages in thread
From: Thomas Petazzoni @ 2019-01-26 14:06 UTC (permalink / raw)
To: buildroot
Hello,
On Mon, 21 Jan 2019 18:39:24 +0100, Peter Korsgaard wrote:
> > I thought it was using the version compiled by buildroot.
> > Isn't that what host-xz is being used for?
>
> Yes, correct. Do you know if the -T 0 option generates identical output
> as -T 1? Otherwise we may want to disable it for reproducible builds.
Does it matter than the output of -T 0 and -T 1 are identical ?
What matters for BR2_REPRODUCIBLE=y is if the same input, with -T 0,
always provide the exact identical output.
Am I missing something here ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
^ permalink raw reply [flat|nested] 14+ messages in thread
* [Buildroot] [PATCH 1/1] fs/common.mk: enable multithreaded xz compression
2019-01-26 14:06 ` Thomas Petazzoni
@ 2019-01-26 19:31 ` James Hilliard
2019-01-27 22:06 ` Peter Korsgaard
1 sibling, 0 replies; 14+ messages in thread
From: James Hilliard @ 2019-01-26 19:31 UTC (permalink / raw)
To: buildroot
On Sat, Jan 26, 2019 at 7:06 AM Thomas Petazzoni
<thomas.petazzoni@bootlin.com> wrote:
>
> Hello,
>
> On Mon, 21 Jan 2019 18:39:24 +0100, Peter Korsgaard wrote:
>
> > > I thought it was using the version compiled by buildroot.
> > > Isn't that what host-xz is being used for?
> >
> > Yes, correct. Do you know if the -T 0 option generates identical output
> > as -T 1? Otherwise we may want to disable it for reproducible builds.
>
> Does it matter than the output of -T 0 and -T 1 are identical ?
>
> What matters for BR2_REPRODUCIBLE=y is if the same input, with -T 0,
> always provide the exact identical output.
My assumption is that -T 0 may be inconsistent due to the autodetection.
>
> Am I missing something here ?
>
> Best regards,
>
> Thomas
> --
> Thomas Petazzoni, CTO, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
^ permalink raw reply [flat|nested] 14+ messages in thread
* [Buildroot] [PATCH 1/1] fs/common.mk: enable multithreaded xz compression
2019-01-26 14:06 ` Thomas Petazzoni
2019-01-26 19:31 ` James Hilliard
@ 2019-01-27 22:06 ` Peter Korsgaard
2019-01-27 22:15 ` James Hilliard
` (2 more replies)
1 sibling, 3 replies; 14+ messages in thread
From: Peter Korsgaard @ 2019-01-27 22:06 UTC (permalink / raw)
To: buildroot
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:
> Hello,
> On Mon, 21 Jan 2019 18:39:24 +0100, Peter Korsgaard wrote:
>> > I thought it was using the version compiled by buildroot.
>> > Isn't that what host-xz is being used for?
>>
>> Yes, correct. Do you know if the -T 0 option generates identical output
>> as -T 1? Otherwise we may want to disable it for reproducible builds.
> Does it matter than the output of -T 0 and -T 1 are identical ?
It would cause an extra change in output between buildroot versions
using -T 0 and ones using -T 1 - But OK, probably that isn't really
important given all the other changes.
What I really meant was if the -T 1 option affected the output format,
and if so, if the difference involved any tradeoff (E.G. perhaps -T 1
compresses slightly worse than -T 0) and if repeated runs with -T 1
would generate the same output (on same machine or on another machine
with different number of threads).
> What matters for BR2_REPRODUCIBLE=y is if the same input, with -T 0,
> always provide the exact identical output.
With the new patch that only enables -T 1 for !reproducible builds,
that is correct.
--
Bye, Peter Korsgaard
^ permalink raw reply [flat|nested] 14+ messages in thread
* [Buildroot] [PATCH 1/1] fs/common.mk: enable multithreaded xz compression
2019-01-27 22:06 ` Peter Korsgaard
@ 2019-01-27 22:15 ` James Hilliard
2019-01-27 22:18 ` Peter Korsgaard
2019-01-28 8:23 ` Thomas Petazzoni
2 siblings, 0 replies; 14+ messages in thread
From: James Hilliard @ 2019-01-27 22:15 UTC (permalink / raw)
To: buildroot
On Sun, Jan 27, 2019 at 3:06 PM Peter Korsgaard <peter@korsgaard.com> wrote:
>
> >>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:
>
> > Hello,
> > On Mon, 21 Jan 2019 18:39:24 +0100, Peter Korsgaard wrote:
>
> >> > I thought it was using the version compiled by buildroot.
> >> > Isn't that what host-xz is being used for?
> >>
> >> Yes, correct. Do you know if the -T 0 option generates identical output
> >> as -T 1? Otherwise we may want to disable it for reproducible builds.
>
> > Does it matter than the output of -T 0 and -T 1 are identical ?
>
> It would cause an extra change in output between buildroot versions
> using -T 0 and ones using -T 1 - But OK, probably that isn't really
> important given all the other changes.
>
> What I really meant was if the -T 1 option affected the output format,
> and if so, if the difference involved any tradeoff (E.G. perhaps -T 1
> compresses slightly worse than -T 0) and if repeated runs with -T 1
> would generate the same output (on same machine or on another machine
> with different number of threads).
The single threaded -T 1 should produce the best compression quality,
although it's a negligible difference.
From my understanding that is because single threaded compression
doesn't need to split up the file being compressed into separate
blocks.
>
> > What matters for BR2_REPRODUCIBLE=y is if the same input, with -T 0,
> > always provide the exact identical output.
>
> With the new patch that only enables -T 1 for !reproducible builds,
> that is correct.
>
> --
> Bye, Peter Korsgaard
^ permalink raw reply [flat|nested] 14+ messages in thread
* [Buildroot] [PATCH 1/1] fs/common.mk: enable multithreaded xz compression
2019-01-27 22:06 ` Peter Korsgaard
2019-01-27 22:15 ` James Hilliard
@ 2019-01-27 22:18 ` Peter Korsgaard
2019-01-28 8:23 ` Thomas Petazzoni
2 siblings, 0 replies; 14+ messages in thread
From: Peter Korsgaard @ 2019-01-27 22:18 UTC (permalink / raw)
To: buildroot
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
>> Does it matter than the output of -T 0 and -T 1 are identical ?
> It would cause an extra change in output between buildroot versions
> using -T 0 and ones using -T 1 - But OK, probably that isn't really
> important given all the other changes.
> What I really meant was if the -T 1 option affected the output format,
> and if so, if the difference involved any tradeoff (E.G. perhaps -T 1
> compresses slightly worse than -T 0) and if repeated runs with -T 1
> would generate the same output (on same machine or on another machine
> with different number of threads).
Sorry, got -T 1 and -T 0 mixed up, I meant -T 0 here.
>> What matters for BR2_REPRODUCIBLE=y is if the same input, with -T 0,
>> always provide the exact identical output.
> With the new patch that only enables -T 1 for !reproducible builds,
> that is correct.
The assumption is that this is not true, especially between systems with
different number of CPUs.
--
Bye, Peter Korsgaard
^ permalink raw reply [flat|nested] 14+ messages in thread
* [Buildroot] [PATCH 1/1] fs/common.mk: enable multithreaded xz compression
2019-01-27 22:06 ` Peter Korsgaard
2019-01-27 22:15 ` James Hilliard
2019-01-27 22:18 ` Peter Korsgaard
@ 2019-01-28 8:23 ` Thomas Petazzoni
2019-01-28 8:25 ` James Hilliard
2019-01-28 8:57 ` Peter Korsgaard
2 siblings, 2 replies; 14+ messages in thread
From: Thomas Petazzoni @ 2019-01-28 8:23 UTC (permalink / raw)
To: buildroot
On Sun, 27 Jan 2019 23:06:14 +0100
Peter Korsgaard <peter@korsgaard.com> wrote:
> > Does it matter than the output of -T 0 and -T 1 are identical ?
>
> It would cause an extra change in output between buildroot versions
> using -T 0 and ones using -T 1 - But OK, probably that isn't really
> important given all the other changes.
Well, BR2_REPRODUCIBLE is definitely not about guaranteeing identical
output between Buildroot versions. How could this even work, since we
are bumping the version of dozens/hundreds of packages ?
BR2_REPRODUCIBLE is about given a fixed Buildroot version and
configuration, be able to generate a binary-identical result.
> > What matters for BR2_REPRODUCIBLE=y is if the same input, with -T 0,
> > always provide the exact identical output.
>
> With the new patch that only enables -T 1 for !reproducible builds,
> that is correct.
I thought -T 0 was the problematic thing as it enabled automatic
parallelization, while -T 1 explicitly disabled parallelization.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
^ permalink raw reply [flat|nested] 14+ messages in thread
* [Buildroot] [PATCH 1/1] fs/common.mk: enable multithreaded xz compression
2019-01-28 8:23 ` Thomas Petazzoni
@ 2019-01-28 8:25 ` James Hilliard
2019-01-28 8:57 ` Peter Korsgaard
1 sibling, 0 replies; 14+ messages in thread
From: James Hilliard @ 2019-01-28 8:25 UTC (permalink / raw)
To: buildroot
On Mon, Jan 28, 2019 at 1:23 AM Thomas Petazzoni
<thomas.petazzoni@bootlin.com> wrote:
>
> On Sun, 27 Jan 2019 23:06:14 +0100
> Peter Korsgaard <peter@korsgaard.com> wrote:
>
> > > Does it matter than the output of -T 0 and -T 1 are identical ?
> >
> > It would cause an extra change in output between buildroot versions
> > using -T 0 and ones using -T 1 - But OK, probably that isn't really
> > important given all the other changes.
>
> Well, BR2_REPRODUCIBLE is definitely not about guaranteeing identical
> output between Buildroot versions. How could this even work, since we
> are bumping the version of dozens/hundreds of packages ?
>
> BR2_REPRODUCIBLE is about given a fixed Buildroot version and
> configuration, be able to generate a binary-identical result.
>
> > > What matters for BR2_REPRODUCIBLE=y is if the same input, with -T 0,
> > > always provide the exact identical output.
> >
> > With the new patch that only enables -T 1 for !reproducible builds,
> > that is correct.
>
> I thought -T 0 was the problematic thing as it enabled automatic
> parallelization, while -T 1 explicitly disabled parallelization.
Right, -T 1 is the default.
>
> Thomas
> --
> Thomas Petazzoni, CTO, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
^ permalink raw reply [flat|nested] 14+ messages in thread
* [Buildroot] [PATCH 1/1] fs/common.mk: enable multithreaded xz compression
2019-01-28 8:23 ` Thomas Petazzoni
2019-01-28 8:25 ` James Hilliard
@ 2019-01-28 8:57 ` Peter Korsgaard
1 sibling, 0 replies; 14+ messages in thread
From: Peter Korsgaard @ 2019-01-28 8:57 UTC (permalink / raw)
To: buildroot
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:
> On Sun, 27 Jan 2019 23:06:14 +0100
> Peter Korsgaard <peter@korsgaard.com> wrote:
>> > Does it matter than the output of -T 0 and -T 1 are identical ?
>>
>> It would cause an extra change in output between buildroot versions
>> using -T 0 and ones using -T 1 - But OK, probably that isn't really
>> important given all the other changes.
> Well, BR2_REPRODUCIBLE is definitely not about guaranteeing identical
> output between Buildroot versions. How could this even work, since we
> are bumping the version of dozens/hundreds of packages ?
> BR2_REPRODUCIBLE is about given a fixed Buildroot version and
> configuration, be able to generate a binary-identical result.
Correct, hence my note "isn't really important".
>> > What matters for BR2_REPRODUCIBLE=y is if the same input, with -T 0,
>> > always provide the exact identical output.
>>
>> With the new patch that only enables -T 1 for !reproducible builds,
>> that is correct.
> I thought -T 0 was the problematic thing as it enabled automatic
> parallelization, while -T 1 explicitly disabled parallelization.
Sorry, I got T 0/1 mixed up in my mail, like I explained in the
followup.
--
Bye, Peter Korsgaard
^ permalink raw reply [flat|nested] 14+ messages in thread
end of thread, other threads:[~2019-01-28 8:57 UTC | newest]
Thread overview: 14+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-01-21 2:07 [Buildroot] [PATCH 1/1] fs/common.mk: enable multithreaded xz compression james.hilliard1 at gmail.com
2019-01-21 14:02 ` Matthew Weber
2019-01-21 14:05 ` James Hilliard
2019-01-21 14:28 ` [Buildroot] [External] " Matthew Weber
2019-01-21 17:39 ` [Buildroot] " Peter Korsgaard
2019-01-21 21:34 ` James Hilliard
2019-01-26 14:06 ` Thomas Petazzoni
2019-01-26 19:31 ` James Hilliard
2019-01-27 22:06 ` Peter Korsgaard
2019-01-27 22:15 ` James Hilliard
2019-01-27 22:18 ` Peter Korsgaard
2019-01-28 8:23 ` Thomas Petazzoni
2019-01-28 8:25 ` James Hilliard
2019-01-28 8:57 ` Peter Korsgaard
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.