This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug gcov-profile/61889] [5 Regression] gcov-tool.c uses nftw, ftw.h


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61889

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #22 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
So, can you just check for nftw with the arguments you want to use in a compile
test in configure and if that fail, perhaps for now don't do that at all?
The next step would be to provide in libiberty a nftw implementation for some
or all targets that don't have it.  mingw surely isn't the only problematic
target.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]