On Fri, Jul 25, 2014 at 11:08 PM, Joe Prostko <joe.pros...@gmail.com> wrote: > Using the handy `fossil bisect`, I found that this revision is causing > me problems while compiling Fossil from within Haiku.
I did some more digging, and the problem seems to be that the assert.h included from within config.h is causing problems when sqlite3.c includes config.h due to _HAVE_SQLITE_CONFIG_H being defined. I did a dirty workaround of copying config.h to jpconfig.h, and then commenting out the include line for assert.h on line 55 of jpconfig.h. I then edited sqlite3.c to include jpconfig.h instead of config.h on line 7635. All other files that include config.h build just fine, as the only file that has problems with config.h in its original form is sqlite3.c. Things compile and run just fine when jpconfig.h is included by sqlite3.c instead of config.h. I played around a bit to try to get some sort of clever header guard in place, but ultimately it didn't work...or wasn't clever enough. ;) If somebody more familiar with all of the code has any ideas, that would be appreciated. I'm sure I'm overlooking something obvious to fix this, all without negatively affecting other platforms. I thought I could find the answer by looking at the SQLite codebase, but well, it generates its config.h during configure, and it looks nothing like the config.h included with Fossil, that's for sure. Also, in case it's useful, here's the assert.h that is used by Haiku. http://cgit.haiku-os.org/haiku/tree/headers/posix/assert.h I'll probably look at this all again tomorrow if nobody has any ideas, but wanted to share my latest findings. - joe _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
