From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] ptxdist compile redirects stderr to stdout
Date: Thu, 1 Dec 2016 11:29:08 +0100 [thread overview]
Message-ID: <20161201102908.i2vplcm7y6vmiusz@pengutronix.de> (raw)
In-Reply-To: <alpine.DEB.2.10.1611300345090.9012@jring-w510-7m3g.gridpoint.com>
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 <stdio.h>
> #include <stdlib.h>
>
> #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-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2016-12-01 10:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 8:46 Jon Ringle
2016-12-01 10:29 ` Michael Olbrich [this message]
2016-12-02 17:25 ` Jon Ringle
2016-12-05 9:03 ` Michael Olbrich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161201102908.i2vplcm7y6vmiusz@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox