capturing the error log from rdma-core

capturing the error log from rdma-core

[Christoph Hellwig]

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 majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: capturing the error log from rdma-core

[Jason Gunthorpe]

On Mon, Oct 10, 2016 at 08:30:13AM -0700, Christoph Hellwig wrote:

> 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 majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: capturing the error log from rdma-core

[Christoph Hellwig]

On Mon, Oct 10, 2016 at 10:12:46AM -0600, Jason Gunthorpe wrote:
> On Mon, Oct 10, 2016 at 08:30:13AM -0700, Christoph Hellwig wrote:
> 
> > 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.

> 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 majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: capturing the error log from rdma-core

[Jason Gunthorpe]

On Mon, Oct 10, 2016 at 09:16:59AM -0700, Christoph Hellwig wrote:
> > 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 majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html