GNOME Bugzilla – Bug 640834
readlink in configure faulty in Mac OS X
Last modified: 2018-02-15 14:58:51 UTC
From configure run: checking whether to disable memory pools... no readlink: illegal option -- f usage: readlink [-n] [file ...] checking whether we are using the GNU C++ compiler... yes In Mac OS X /usr/bin/readlink is *not* the complete GNU/FSF variant but that from NetBSD and it only understands the -n option.
With glib-2.30.2.tar.xz it happens again or still: checking whether to disable memory pools... no readlink: illegal option -- f usage: readlink [-n] [file ...] checking whether we are using the GNU C++ compiler... yes
The same happens on Mac OS X 10.5.8, Leopard.
And on OS X 10.6.8 Snow Leopard, and presumably every other version of OS X past, present and future. I'm the maintainer of glib in MacPorts; this problem has always bugged me, since I don't know what glib is trying to check using readlink and what the implications are of it completely failing like this. Presumably not terrible, since glib has been in MacPorts for ten years already with this problem. But it should still be fixed; usage messages displayed during a configure run are unsettling.
Related Bug #606872 (note, still same configure code-block as of glib-2.36.1)
This was resolved in glib 2.47.6 which no longer uses readlink -f in the configure script.
Yup, by commit 8c263008bbd9c1ce221276229e548d7b15dcb0d0. ⇒ FIXED