After a recent macOS update, building Postgres produces warnings
that look like this:
ranlib: warning: 'libpgport_shlib.a(pg_cpu_x86.c.o)' has no symbols
ranlib: warning: 'libpgport_shlib.a(pg_popcount_x86.c.o)' has no symbols
To fix, add a dummy symbol to files that may otherwise have none.
Per project policy, this is a candidate for back-patching into
out-of-support branches: it suppresses annoying compiler warnings
but changes no behavior.
Reported-by: Zhang Mingli <zmlpostgres@gmail.com>
Reviewed-by: John Naylor <johncnaylorls@gmail.com>
Reviewed-by: Tom Lane <tgl@sss.pgh.pa.us>
Discussion: https://postgr.es/m/
229aaaf3-f529-44ed-8e50-
00cb6909af21%40Spark
Backpatch-through: 13
return 0;
}
+#else /* defined(USE_SSE2) || defined(__i386__) */
-#endif /* defined(USE_SSE2) || defined(__i386__) */
+/* prevent linker complaints about empty module */
+extern int pg_cpu_x86_dummy_variable;
+int pg_cpu_x86_dummy_variable = 0;
+
+#endif /* ! (USE_SSE2 || __i386__) */
return popcnt;
}
-#endif /* USE_NEON */
+#else /* USE_NEON */
+
+/* prevent linker complaints about empty module */
+extern int pg_popcount_aarch64_dummy_variable;
+int pg_popcount_aarch64_dummy_variable = 0;
+
+#endif /* ! USE_NEON */
return popcnt;
}
-#endif /* HAVE_X86_64_POPCNTQ */
+#else /* HAVE_X86_64_POPCNTQ */
+
+/* prevent linker complaints about empty module */
+extern int pg_popcount_x86_dummy_variable;
+int pg_popcount_x86_dummy_variable = 0;
+
+#endif /* ! HAVE_X86_64_POPCNTQ */