<p></p>
<p>NAK for littering the source with #ifdef's around every #pragma we may ever add.</p>
<p>The job of a configure script is to figure out a way how to make the software run on a system and bail out if it can't, but automatically disabling OpenMP is only when it's not explicitly enabled with --enable-openmp.<br>
I just don't think fiddling with the configure logic to get it <em>just so</em> with all possible cases is worth anybody's time...</p>
<p>It's quite clear people expect to build the latest rpm in all manner of strange configurations that we're not necessarily prepared to support. Having to manually disable something intentionally sends a certain message - openmp might be optional for now but might not always be that way.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/rpm-software-management/rpm/pull/1433#issuecomment-726053611">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ADLPZUY5PKQVC2G22HCOOXTSPPJVBANCNFSM4TR2SSQA">unsubscribe</a>.<img src="https://github.com/notifications/beacon/ADLPZU5RWN7MUSADLCT3AITSPPJVBA5CNFSM4TR2SSQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOFNDLF2Y.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/rpm-software-management/rpm/pull/1433#issuecomment-726053611",
"url": "https://github.com/rpm-software-management/rpm/pull/1433#issuecomment-726053611",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>