On Sat, 7 Apr 2012, Daniel Jacobowitz wrote:

> On Fri, Apr 6, 2012 at 8:36 AM, Jan Kratochvil
> <jan.kratochvil@redhat.com> wrote:
> > I do not see any problem with it, compilation directory is not known in such
> > case.  I do not see any testcase in this patch which would show which GCC
> > versions under which conditions produced such buggy output.  These GCC
> > versions produce correct output, that is:
> 
> I'm sure it was the current stable GCC at the time.  That would be
> 4.1/4.2.  I'd try to find the fix, but picking out a patch by Joseph
> is like hunting for a needle in a haystack :-)

It may have been 
<http://gcc.gnu.org/ml/gcc-patches/2007-07/msg00404.html>.  The case of 
absolute paths to the source file and headers found by a relative -I path 
would probably have appeared when building glibc.

-- 
Joseph S. Myers
joseph@codesourcery.com