On Wed, Dec 11, 2013 at 11:14 AM, Allan McRae <[email protected]> wrote: > How about #5...
Remember: libalpm is a .so, and sizeof(off_t) is something the app writer is free to choose (on many systems). The problem is that the choice made by libalpm (by ./configure) gets baked into the .so ABI, and if the app writer chooses differently they get SEGVs. The macro approach works because the macro gets evaluated in the app compile context, so it sees what the app writer chose. Without knowing both what libalpm ./configure chose and what the app writer chose you can't detect when they differ.
