Re: [ptxdist] systemd 232

[Clemens Gruber]

Hi,

On Tue, Nov 29, 2016 at 09:46:14AM +0100, Michael Olbrich wrote:
> Hi,
> 
> On Mon, Nov 28, 2016 at 06:02:51PM +0100, Clemens Gruber wrote:
> > did you already start working on updating systemd to version 232?
> 
> I've started with it. But new systemd versions require more testing than
> most packages.

I just tried the ptxdist master version of systemd 232.

Looking good except for one problem:
rc-once.service: Main process exited, code=killed, status=15/TERM
rc-once.service: Unit entered failed state.
rc-once.service: failed with result 'signal'.

Because I am not doing anything different in /etc/rc.once.d/*, I assume
this has something to do with the update from 231 to 232.

Can you reproduce this?

For the record, in rc.once.d I have: ldconfig, machine-id and openssh.

Is there something in /lib/systemd/systemd-rc-once which could cause
this on systemd 232?

Thanks,
Clemens

___
ptxdist mailing list
ptxdist@pengutronix.de

[ptxdist] [PATCH] latrace: provide demangling support

[Juergen Borleis]

To support demangeling, latrace requires libiberty. Demangeling is requiered
for C++ only (AFAIR), so let it be an option.

Signed-off-by: Juergen Borleis 
---
 rules/latrace.in | 17 +++--
 1 file changed, 15 insertions(+), 2 deletions(-)

diff --git a/rules/latrace.in b/rules/latrace.in
index 8aa6ae9..4ee5265 100644
--- a/rules/latrace.in
+++ b/rules/latrace.in
@@ -1,8 +1,21 @@
 ## SECTION=debug_tools
 
-config LATRACE
+menuconfig LATRACE
tristate
-   prompt "latrace"
+   prompt "latrace   "
+   select BINUTILS if LATRACE_DEMANGLE
help
  A tool to trace library calls and get their statistics in a
  manner similar to the strace utility
+
+if LATRACE
+
+config LATRACE_DEMANGLE
+   bool
+   prompt "demangle supprt"
+   default y
+   help
+ Enable support for the demangle feature, required to trace C++ 
libraries
+ for example.
+
+endif
-- 
2.10.2


___
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] Antwort: Re: [PATCH] openvpn: version bump 2.3.11 -> 2.3.13

[Alexander Dahl]

Hei hei,

On Thu, Dec 01, 2016 at 11:11:43AM +0100, Michael Olbrich wrote:
> > are patches in attachments accepted on this mailing list?
> 
> I prefer patches sent with 'git send-email' because I can apply them
> directly from my mail client. I accept attachments as well, but it may take
> longer, because it's more work for me.

FWIW: There are some helpful hints on e-mail clients in the Linux
kernel documentation:

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/email-clients.txt

The patch we are talking about was sent with Lotus according to mail
headers. Lotus was the default in my company as well for years and it
really sucks at e-mail. So what I did was pushing my stuff to my
personal public git clone [1], pull it at home and send it with my
personal mail account. ¯\_(ツ)_/¯

HTH & Greets
Alex

[1] https://github.com/LeSpocky/ptxdist

-- 
»With the first link, the chain is forged. The first speech censured, 
the first thought forbidden, the first freedom denied, chains us all 
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: C28E E6B9 0263 95CF 8FAF  08FA 34AD CD00 7221 5CC6 ***


pgpq8RtvUiKGJ.pgp
Description: PGP signature
___
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] help broken again since 2016.10.0

[Michael Olbrich]

Hi,

On Wed, Nov 23, 2016 at 09:48:39AM +0100, Alexander Dahl wrote:
> while searching how to build the new documentation (btw: I could not
> find out) I stumbled over the broken help. Results from different
> ptxdist versions:
> 
[...]
> 
> The file ptxdist.1.gz is only available in the folders of 2016.08.0 and
> 2016.09.0 and missing in all the others. I usually install like this:
> 
> * go to ptxdist src folder (git clone)
> * git co ptxdist-201?-??-?
> * git clean -dxf
> * ./autogen.sh
> * ./configure
> * make
> * sudo make install
> 
> In the current master no man page is created with a simple `make`, I
> would have to call `make man`, not sure if it gets installed, though,
> didn't test it.

This was a deliberate change and I'm not quite sure how to improve the
situation.
I did not want to make rst2man a hard requirement for ptxdist. So all
tarball releases contain the man-page.

I suppose we could create the man page under certain circumstances during
'make'. What should the condition be? If rst2man is found? When working
with a ptxdist git checkout?

Regards,
Michael

-- 
Pengutronix e.K.   | |
Industrial Linux Solutions | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0|
Amtsgericht Hildesheim, HRA 2686   | Fax:   +49-5121-206917- |

___
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] help broken again since 2016.10.0

[Uwe Kleine-König]

On Thu, Dec 01, 2016 at 11:02:45AM +0100, Michael Olbrich wrote:
> Hi,
> 
> On Wed, Nov 23, 2016 at 09:48:39AM +0100, Alexander Dahl wrote:
> > while searching how to build the new documentation (btw: I could not
> > find out) I stumbled over the broken help. Results from different
> > ptxdist versions:
> > 
> [...]
> > 
> > The file ptxdist.1.gz is only available in the folders of 2016.08.0 and
> > 2016.09.0 and missing in all the others. I usually install like this:
> > 
> > * go to ptxdist src folder (git clone)
> > * git co ptxdist-201?-??-?
> > * git clean -dxf
> > * ./autogen.sh
> > * ./configure
> > * make
> > * sudo make install
> > 
> > In the current master no man page is created with a simple `make`, I
> > would have to call `make man`, not sure if it gets installed, though,
> > didn't test it.
> 
> This was a deliberate change and I'm not quite sure how to improve the
> situation.
> I did not want to make rst2man a hard requirement for ptxdist. So all
> tarball releases contain the man-page.
> 
> I suppose we could create the man page under certain circumstances during
> 'make'. What should the condition be? If rst2man is found? When working
> with a ptxdist git checkout?

Isn't this what --enable-maintainer-mode is supposed to do? I.e. in
maintainer-mode regerate everything, and otherwise use shipped files.

Best regards
Uwe

-- 
Pengutronix e.K.   | Uwe Kleine-König|
Industrial Linux Solutions | http://www.pengutronix.de/  |

___
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] ptxdist compile redirects stderr to stdout

[Michael Olbrich]

Hi,

On Wed, Nov 30, 2016 at 03:46:14AM -0500, Jon Ringle wrote:
> I discovered after updating to a new version of ptxdist that all of my
> compile output including errors/warnings are now all going to stdout
> instead of having the errors/warning going to stderr.
> 
> This is causing some problem when I use qtcreator as my IDE because
> qtcreator will only filter stderr for errors/warnings to put into the
> Issues tab, where one can simply click on the error/warning and be taken  
> right to the source line where the error/warning is found. 
>  
> I create a small program to demonstrate the problem:
> $ cat local_src/testprog/testprog.c
> #include 
> #include 
> 
> #error An error here
> int main(int argc, char *argv[])
> {
> printf("Hello World, I'm testprog!\n");
> 
> exit(EXIT_SUCCESS);
> }
> 
> $ ptxdist-2016.10.0 --force targetinstall testprog >/dev/null
> make: ***
> [/home/jringle-admin/code/gpec/ec1k-rootfs/platform-EC1C/state/testprog.compile]
> Error 2
> 
> $ ptxdist-2015.08.0 --force targetinstall testprog >/dev/null
> testprog.c:4:2: error: #error An error here
>  #error An error here
>   ^
> make[1]: *** [testprog] Error 1
> make: ***
> [/home/jringle-admin/code/gpec/ec1k-rootfs/platform-EC1C/state/testprog.compile]
> Error 2
> 
> I found that this is being caused by commit
> 30b9267e35eea1c2edb4da0231a428bfa25b6766
> 
> Is there a way that the stderr to stdout redirect could be implemented
> conditionally so that I can still have stderr segregated if I want to?

Yes. It's really only necessary if output synchronization is enabled. So,
we could set some variable in setup_parallel() to '1' or '2' depending on
PTXDIST_OUTPUT_SYNC and then use it instead of '2>&1'.

Michael

-- 
Pengutronix e.K.   | |
Industrial Linux Solutions | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0|
Amtsgericht Hildesheim, HRA 2686   | Fax:   +49-5121-206917- |

___
ptxdist mailing list
ptxdist@pengutronix.de