[ccache] Should 3.1.7 contain commit 469267b2be49d6acdca5058e3e744a508ce3da5d ?
joel at rosdahl.net
Mon Mar 5 14:49:50 MST 2012
If I remember correctly, 469267b was not made to fix exactly the problem
you describe, but yes, it sounds like it should be ported to a maintenance
release. Will do that. It will show up in 3.1.8 or 3.2, whichever comes
On 5 March 2012 22:28, Gerard Snitselaar <dev at snitselaar.org> wrote:
> I ran into an issue while doing a build of the Factor programming
> language. They
> do a test in their build script to see if some libraries are available by
> a quick build attempt and link with that library and then check status to
> if it failed. Because they didn't want messages on the console from this,
> closed stderr. This caused a segfault with ccache. steup_uncached_err() was
> failing the dup() of stderr, and calling failed(), which then called
> which dies because args hadn't been allocated at that point.
> Commit 469267b2be49d6acdca5058e3e744a508ce3da5d looks like it fixes this
> was added last July, but the tree with tag 3.1.7 does not appear to have
> this change.
> I am on Fedora 16, and they pulled in 3.1.7 to their ccache package.
> Should this change
> be visible in 3.1.7 ?
> ccache mailing list
> ccache at lists.samba.org
More information about the ccache