Re: [ptxdist] How to generate license report?

Hi, On Mon, Mar 26, 2018 at 09:44:17AM +0200, Roland Hieber wrote: > On 22.03.2018 10:51, Alexander Dahl wrote: > > from the Git repository and some hints in the ptxdist source code I assume > > ptxdist can generate some kind of license report, based on the FOO_LICENSE > > variables in each

Re: [ptxdist] [PATCH] lsuio: Add license information

On Mon, Mar 26, 2018 at 08:19:26AM +0200, Alexander Dahl wrote: > Signed-off-by: Alexander Dahl > --- > rules/lsuio.make | 16 +--- > 1 file changed, 9 insertions(+), 7 deletions(-) > > diff --git a/rules/lsuio.make b/rules/lsuio.make > index f6d4aa3f80..f8bd970db9

Re: [ptxdist] How to generate license report?

Hi, On Tue, Mar 27, 2018 at 09:43:35AM +0200, Michael Olbrich wrote: > > > Is it possible to generate such a report? How? > > > > This should probably be documented. You can get it via > > > >$ ptxdist make license-report > > That's currently the way to do this. It's not documented because

Re: [ptxdist] Including valgrind in the configuration doesn't trigger an un-optimized build of glibc.

Hi, On Mon, Mar 26, 2018 at 07:03:21AM -0500, Crim, Jason wrote: > I'd tried moving over the root-debug versions of the referenced files, and > was still hitting the error. That's when I'd found the post referencing > the optimization levels. I'll take a look at getting the nfs-root running >

Re: [ptxdist] [PATCH] lsuio: Add license information

Hello, On Tue, Mar 27, 2018 at 09:01:58AM +0200, Michael Olbrich wrote: > > +LSUIO_VERSION := 0.2.0 > > +LSUIO_MD5 := 8da82b681c24e6c5b3518c99e7f961d7 > > +LSUIO := lsuio-$(LSUIO_VERSION) > > +LSUIO_SUFFIX := tar.gz > > +LSUIO_URL

Re: [ptxdist] How to generate license report?

Hello, On Tue, Mar 27, 2018 at 09:43:35AM +0200, Michael Olbrich wrote: > I want to move this stuff out of rules/post/ and do something similar to > the image rules. And then hook up these new packages these packages > somewhere. I'm not sure 'world' is the correct place, so a new command >

Re: [ptxdist] Including valgrind in the configuration doesn't trigger an un-optimized build of glibc.

Michael, It looks like the toolchain is configured as OSELAS.Toolchain-2014.12. I've recently been added to a team which had this existing ptxdist setup, so I've been trying to learn my way around ptxdist while trying to get valgrind enabled to test an issue. The initial run of valgrind

[ptxdist] [PATCH] iptables: fix typo

Signed-off-by: Ulrich Ölmann --- rules/iptables.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rules/iptables.in b/rules/iptables.in index 3cad506d09c2..846e5334a1d9 100644 --- a/rules/iptables.in +++ b/rules/iptables.in @@ -78,6 +78,6 @@ config

[ptxdist] [PATCH v2] lsuio: Add license information

Signed-off-by: Alexander Dahl --- Notes: v1 -> v2: Fix whitespace rules/lsuio.make | 2 ++ 1 file changed, 2 insertions(+) diff --git a/rules/lsuio.make b/rules/lsuio.make index f6d4aa3f80..91678ea4fb 100644 --- a/rules/lsuio.make +++ b/rules/lsuio.make @@ -23,6 +23,8 @@