> On 1 Dec 2025, at 15:11, Ranjan Maitra via users > <[email protected]> wrote: > > So, this is perplexing to me. I see: > > std::ostream& operator<<( std::ostream& os, const PAM::Exception& e); > > in PAM.h > > and that is being called in app.h and PAM.h in the BUILD directory. > > Is this not enough? Strangely, the 1.4.0 build has no problems with this, as > well as building it outside the RPM environment being created with the SPEC > file.
So long as that line in PAM.h is processed you would be ok. When debugging this sort of thing I edit the file with the definition and add a `#error` line on the line after the definition. If that PAM.h is processed as your expect you will see the #error line being reported as the error and you the know that things are working. But if you do not see the #error line reported something is #ifdef'ing that line out of the file. Barry
-- _______________________________________________ users mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
