This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: conflict include file names found in gcc-3.4.1


>>>>> "James" == James E Wilson <wilson@specifixinc.com> writes:

    James> If you look at the FSF gcc Makefile, you will see that
    James> -I. is the first directory in the include path.  Look at
    James> the INCLUDES rule.

    >> Not always.

    James> You didn't read what I wrote.  I clearly said Makefile and
    James> INCLUDES.  If you actually bothered to look at the
    James> Makefile, you would see that I am right.

    >> There is no local modification, there are extra parameters
    >> added to configure that cause this to happen.

    James> This is the vital clue that you left out of your earlier
    James> bug report.

    >> I believe the handling of --with-libiconv-prefix parameter is
    >> not correct.

    James> Yes.  Note that this configure option does not modify
    James> INCLUDES.  It modifies CPPFLAGS which is wrong.

    James> Now that you have enough info for a proper bug report,
    James> please file one into our bugzilla database.  We do not
    James> track bug reported to the gcc-bugs mailing list.  We only
    James> track bugs filed into our bug database.  See
    James> http://gcc.gnu.org/bugs.html for more info on reporting
    James> bugs.

Will do, thanks for confirming the problem.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]