https://sourceware.org/bugzilla/show_bug.cgi?id=25509
--- Comment #7 from Mark Wielaard <mark at klomp dot org> --- So there are two ideas here: - Split --disable-debuginfod which currently disables building debuginfod (the server), libdebuginfod (the library) and debuginfod-find (the helper binaries) in two: --disable-debuginfod to disable building of the server. --disable-libdebuginfod to disable building of the library and helper binary. - Introduce a dummy-libdebuginfod which has the same interface as libdebuginfod, so applications (during bootstrapping) can link to it. But which would not link against libcurl and all functions would simply fail. I assume that --disable-libdebuginfod would mean you cannot have --enable-debuginfod (because debuginfod links against libdebuginfod). And that --enable-dummy-libdebuginfod would imply --disable-libdebuginfod because they provide the same library. I assume that debuginfod-find would be build if either --enable-libdebuginfod or --enable-dummy-libdebuginfod is given (in the last case it would simply not do anything useful, but would show the dummy "works"). -- You are receiving this mail because: You are on the CC list for the bug.
