Handle ENOATTR and ENODATA separately

Some platforms define both of them, some define only one of them.

Author: netheril96

sources/fuse_high_level_ops_base.cpp

@@ -287,10 +287,17 @@ int FuseHighLevelOpsBase::static_getxattr(
             }
             catch (const ExceptionBase& e)
             {
-#if defined(ENOATTR) && defined(ENODATA)
-                // This happens so frequently that we don't want to log it.
                 auto err = e.error_number();
-                if (err == ENOATTR || err == ENODATA)
+#ifdef ENOATTR
+                // This happens so frequently that we don't want to log it.
+                if (err == ENOATTR)
+                {
+                    return -err;
+                }
+#endif
+#ifdef ENODATA
+                // This happens so frequently that we don't want to log it.
+                if (err == ENODATA)
                 {
                     return -err;
                 }