On Mon, Apr 06, 2009 at 01:47:41PM +0100, Nicholas Clark wrote:
> On Sun, Apr 05, 2009 at 10:29:38PM +0300, Niko Tyni wrote:
> > sub inc_dirs
> > {
> > my $from_gcc = `LC_ALL=C $Config{cc} -v 2>&1`;
> > @@ -755,7 +755,7 @@ sub inc_dirs
> > $from_gcc = '';
> > };
> > };
> > - length($from_gcc) ? ($from_gcc, $Config{usrinc}) : ($Config{usrinc});
> > + length($from_gcc) ? ($from_gcc, $from_gcc . "-fixed", $Config{usrinc})
> > : ($Config{usrinc});
> Does every version of gcc that ends up in the "gcc-4+" block know about the
> '-fixed' command line flag? It's not clear to me from the thread you link to.
> If not, then they're going to choke on it.
It's not a gcc command line flag, it's duplicating the gcc internal
include directory name with the string "-fixed" appended.
Currently @inc_dirs gets set here to
("/usr/lib/gcc/x86_64-linux-gnu/4.3.2/include", "/usr/include")
and the patch makes it
("/usr/lib/gcc/x86_64-linux-gnu/4.3.2/include",
"/usr/lib/gcc/x86_64-linux-gnu/4.3.2/include-fixed",
"/usr/include")
Hope that clarifies, sorry for not being clear enough.
--
Niko Tyni nt...@debian.org
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
