http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50342
Jack Howarth <howarth at nitro dot med.uc.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |howarth at nitro dot
| |med.uc.edu
--- Comment #1 from Jack Howarth <howarth at nitro dot med.uc.edu> 2011-09-09
14:04:06 UTC ---
Apple's macports developers had similar comments in their recommendations for
porting to Lion...
http://lists.macosforge.org/pipermail/macports-dev/2011-July/015263.html
5) Building with a compiler that doesn't support newer __builtins
If your port uses MacPorts compilers rather than the default compiler, you may
run into trouble with string functions. You'll see errors at link time about
undefined __builtin_* functions. If this happens, you may want to compile with
-D_FORTIFY_SOURCE=0 to tell the headers to use unfortified versions which do
not use compiler builtins.
