On Mon, May 20, 2013 at 10:07 AM, Alexander Monakov <amona...@ispras.ru> wrote: > I now realize that a less intrusive approach is available: just provide > replacement filenames.h, dwarf2.h in a separate directory and pick up those > headers for a standalone build. In replacement dwarf2.h, include system > dwarf.h, #define potentially missing enum values and provide dummy enum tags. > The downside is that GCC complains about using variables of dummy enum types > in comparisons and switch statements, necessitating -Wno-switch and > -Wno-enum-compare. > > Build system dependencies are a bigger problem that is beyond "scratching my > own itch" at the moment (I have to provide a CMake build script anyhow). > > The below is what I submitted to import libbacktrace in the APITrace project. > I'm not sure whether it makes sense to commit it in GCC: it's not particularly > useful without the standalone CMake build script.
To be clear: are you withdrawing your earlier patch? I agree that your proposal seems like a reasonable approach, and I agree that it doesn't need to be in GCC. It could be in a standalone copy of libbacktrace if anybody creates one. Ian
