So did anyone even bother to think about the reality that --export-dynamic has been _ignored_ in the past and there have been no consequences.
I just included it in my patch with the comment, because I assume you know what you are doing and eg. it might have been there for some other silly compilers.
"GCC now has stricter checks for invalid command-line options. In particular, when gcc was called to link object files rather than compile source code, it would previously accept and ignore all options starting with --, including linker options such as --as-needed and --export-dynamic, although such options would result in errors if any source code was compiled. Such options, if unknown to the compiler, are now rejected in all cases; if the intent was to pass them to the linker, options such as -Wl,--as-needed should be used."
So did anyone even bother to think about the reality that --export-dynamic has been _ignored_ in the past and there have been no consequences.
I just included it in my patch with the comment, because I assume you know what you are doing and eg. it might have been there for some other silly compilers.
from http:// gcc.gnu. org/gcc- 4.6/changes. html
"GCC now has stricter checks for invalid command-line options. In particular, when gcc was called to link object files rather than compile source code, it would previously accept and ignore all options starting with --, including linker options such as --as-needed and --export-dynamic, although such options would result in errors if any source code was compiled. Such options, if unknown to the compiler, are now rejected in all cases; if the intent was to pass them to the linker, options such as -Wl,--as-needed should be used."