the problem comes from usage of -flto that converts warnings to errors..

Yeah, that was clear. Sorry I should be more specific. As git grep "flto" yields no results in the codebase but it is clearly showing up in the logs with -flto=auto I'm not sure what controls this and what is the preferred method of dealing with it in the dev team's mind.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/pull/1906#issuecomment-1430185933", "url": "https://github.com/xrootd/xrootd/pull/1906#issuecomment-1430185933", "name": "View Pull Request" }, "description": "View this Pull Request on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

Use REPLY-ALL to reply to list

To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1