Let’s assume that you have checked your system for damage and found none, and let’s also assume that what you are seeing is repeatable at-will after doing make distclean and so-forth.   (If that is not yet the case, this is step-one.)

I would start by examining the generated Makefile, then grepping the source tree (or the system’s include-directories) for that identifier.   (“grep -rilw foobar .” ... yup, I can do it in my sleep ...)

The next thing that I would grep is the various Configure control-files which determine exactly how that Makefile is to be built.   Perhaps there is an option that you need to specify in the configure step.   Perhaps there is a step that is not working properly.

When you run configure, capture the output to a file (if it isn’t being captured already) and grep or less that file.   Look specifically for any point where it appears to be making tests and decisions related to the problem area.   Look carefully for any error or warning indications.   It is extremely easy to let important clues “just breeze by.”

Or ... well, it’s damm unlikely but it’s possible ... maybe, gosh darn it, there’s a bug here.   If so, undoubtedly it has already been reported, so you would look at the ticket-list for this distribution.