Raffi Khatchadourian <[EMAIL PROTECTED]> writes:

> gcc: unrecognized option `-rdynamic'

Please ignore this error.  ELinks can benefit from -rdynamic but
does not yet require it.  The configure script tries to check
whether the compiler supports -rdynamic, but GCC exits with
success regardless of this error.  I suppose the script could be
changed to run the compiler with LC_ALL=POSIX and grep stderr for
"unrecognized option [`']-rdynamic'".  (The message differs
between GCC 3.4 and 4.0.)

Related comments from elinks-0.12/configure.in:

dnl Check for -rdynamic
dnl
dnl gcc -rdynamic calls ld -export-dynamic, which adds all symbols of
dnl the executable to its dynamic symbol table.  ELinks uses this for
dnl two purposes:
dnl
dnl 1. If ELinks detects a bug, it can try to display a backtrace by
dnl    calling backtrace_symbols_fd() in the GNU libc.  The glibc-2.3.6
dnl    manual states users of GNU ld must pass -rdynamic to make the
dnl    symbols available to the program.
dnl
dnl 2. It would eventually be nice to dynamically load shared
dnl    libraries as plugins (bug 73).  The plugins must be able to
dnl    call ELinks functions.  This can be implemented either by
dnl    registering all callable functions in ELinks-specific data
dnl    structures, or by letting the dynamic linker handle them.
dnl    The latter way requires something equivalent to -rdynamic.
dnl
dnl Because backtraces are not needed for correct operation, and bug
dnl 73 is not yet being fixed, the configure script and makefiles
dnl should not complain to the user if they find that -rdynamic does
dnl not work.  Besides, it was reported at elinks-users on 2006-09-12
dnl that gcc-3.4.2 with "ld: Software Generation Utilities - Solaris
dnl Link Editors: 5.8-1.284" on Sun Solaris 8 Sparc does not support
dnl -rdynamic but does something equivalent automatically.  (This was
dnl tested with "nm -D elinks | grep redraw_from_window".)
dnl
dnl FIXME: This check doesn't work. Something to do with the compiler
dnl happily ignoring it and stderr not being checked for error messages.

By the way, if ELinks 0.11.3 works OK on SunOS, could you post a
success report?  The elinks(1) manpage lists quite a few
platforms where ELinks is "known to work", and some of them
(e.g. OS/2) probably do not actually work any more.  I'm thinking
we could set up a table of the most recent ELinks versions tested
on each platform, with references to important platform-specific
bugs.
_______________________________________________
elinks-users mailing list
[email protected]
http://linuxfromscratch.org/mailman/listinfo/elinks-users

Reply via email to