[nohat]

First: Yep, there's not much available about compiling gfortran for osx. The link does show an example of gfortran requiring glibc - which is the point you were disagreeing with.

Second: just another example (by descending order of googleableness) of the main gcc requiring glibc.

Quite possibly there is an osx (or other bsd) specific c library that can substitute for glibc, but I did not find it, and gfortran will complain without it.

'what is it that makes you think using glibc would solve a glibc problem?' Eh? I used glibc to solve a 'missing glibc' problem. I then had other problems with glibc which I attempted to solve.

[nknight]

You're not understanding. The first example "requires glibc" because the binaries were linked against glibc, just like they'd be linked against OS X's libc if they'd been built for OS X.

The second example is, again, an issue of gcc being built against glibc. You can build it against any libc you want, but when built against glibc, the resulting binaries are obviously going to use glibc.

You appear to have a fundamental misunderstanding of the difference between the requirements of source code, and the requirements of the binaries built from them. The latter are not the same as the former, and will vary depending on how you built the source code.

And when I just built gfortran, it didn't complain about the lack of glibc at all. If yours was complaining, I think you must have configured something incorrectly, though it escapes me what that could be.