[distcc] Re: Distcc & GDB (fix)

[Alexandre Oliva]

On May  9, 2003, Thomas Walker <Thomas.Walker at morganstanley.com> wrote:

> Alexandre, you had mentioned that you had, at some point, passed a patch
> to fix this behaviour (I'm assuming it caused cpp to always include the
> full path to source in the .i files, which makes sense because cpp is
> the only part of the compiler that is guarenteed to actually know where
> they are) but that the preprocessor guys had been reluctant to include
> it (or admit it as a bug).  Do you happen to still have a copy of this
> patch lying around?

Here it is.  At some point around the dates in the diff, it even
worked :-)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: distcc-preproc-directory.patch
Type: text/x-patch
Size: 10442 bytes
Desc: not available
Url : http://lists.samba.org/archive/distcc/attachments/20030509/4050571c/distcc-preproc-directory.bin
-------------- next part --------------

> I recently brought the issue to the attention of
> our Enterprise Support rep at Redhat and he seemed to think that he
> could help with getting the patch pushed through (it helps being a
> really big client I guess :)

'fraid there's not much the rep can do, other than getting the patch
included in the GCC that Red Hat ships to you, but in general we try
to minimize divergence from the FSF-released GCC.

The thing is that the maintainers of the preprocessor in GCC for the
FSF, none of which are Red Hat associates, don't agree that the
current behavior is wrong.  And, even if they were Red Hat associates,
their judgment on whether a patch is appropriate for FSF GCC shouldn't
be affected by this, since maintainers of FSF projects, while wearing
their maintainer hats, are working for the FSF, not for whatever
company happens to employ them.  Even if the maintainer hats happen to
be red :-) :-)

Of course, anyone may be willing to support a toolchain with a custom
patch, and your Red Hat rep might end up finding that this could be a
solution to solve your problem.  But it's far beyond Red Hat's powers
to force any patch into GCC or any other FSF project, no matter how
important the feature is for Red Hat's customers.

If you'd like to get me involved in this issue, please send me (in
private, to aoliva at redhat.com) the enterprise support request number,
and the e-mail address of your rep, and I'll figure out how to get
involved.

Thank you,

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                 aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist                Professional serial bug killer