capturing the error log from rdma-core
Hi Jason,
what's the best way to generate a log of the compiler errors with the shiny new rdma-core build system? With make I'd do make 2>err.log but with the new build system the verbose build output and the errors are mixed in the same stream, so this isn't possible anymore.
With the fairly large number of warnings from sparse this is rather annoying.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 4 lines · Christoph Hellwig
what's the best way to generate a log of the compiler errors with the shiny new rdma-core build system? With make I'd do make 2>err.log but with the new build system the verbose build output and the errors are mixed in the same stream, so this isn't possible anymore.
If I understand you, you want to split STDOUT and STDERR because sparse puts differentiated output on each FD?
There is a thread on the ninja list about fixing this, and here is a proposed patch
https://github.com/dendy/ninja/commit/62564251afdafd9926fde363035807fb482ab0b9
But looks like it is not in main line.
I think the simplest approach for you will be to use make when doing this kind of work:
$ mkdir build-make $ cd build-make $ CC=cgcc cmake $ make 1> a 2> b
Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
A message that is not in the archive (sent off-list or not yet received): 20161010161246.GB26805-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org
Quoted 9 lines · Jason Gunthorpe
Quoted 4 lines · Christoph Hellwig
what's the best way to generate a log of the compiler errors with the shiny new rdma-core build system? With make I'd do make 2>err.log but with the new build system the verbose build output and the errors are mixed in the same stream, so this isn't possible anymore.
If I understand you, you want to split STDOUT and STDERR because sparse puts differentiated output on each FD?
No, sparse only outputs to SDTERR. But for some reason the rdma-core build system multiplexes this back into STDOUT.
Quoted 7 lines
I think the simplest approach for you will be to use make when doing this kind of work:
$ mkdir build-make $ cd build-make $ CC=cgcc cmake $ make 1> a 2> b
Ok..
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 5 lines · Christoph Hellwig
Quoted 2 lines
If I understand you, you want to split STDOUT and STDERR because sparse puts differentiated output on each FD?
No, sparse only outputs to SDTERR. But for some reason the rdma-core build system multiplexes this back into STDOUT.
Right, ninja puts everything onto STDOUT as part of 'output-sync' operation. That is usually not a problem..
If you are asking for the 'quietest' build then this hack will do it:
$ ninja | grep -v "^\["
Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html