https://issues.apache.org/bugzilla/show_bug.cgi?id=55789
--- Comment #8 from Dennis Clarke <[email protected]> --- I have located a number of header files in /usr/local/include that are being looked at first in the build process and they are from Apache 2.4.4 and thus not correct for 2.4.6. I have renamed them to /usr/local/include/foobar_2.4.4.h and then I try a rebuild of 2.4.6 until I hit another snag. Then I locate the next offending header file and rename it and do this loop over and over. HOWEVERR this reaises the concern in my mind that there may be a subtle code change in a header between 2.4.4 and 2.4.6 such that the build of 2.4.6 does continue however I do NOT have the correct header being used because the wrong header is in /usr/local/include and I could not detect it. This is a concern as the only way forward for me would be to do a full build of 2.4.6, assuming that I get there using my hunt and peck loop above, and then install and then rebuild 2.4.6 again. After a second or possibly third build loop I would have all the correct header versions in /usr/local/ and then no problem. This is akin to the three stage GCC bootstrap process. dc -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
