I add the tech-toolchain list because of Noriyuki Soda's request.
However, I'm not subscribing the tech-toolchain list.
For tech-toolchain subscribers, see also:
http://mail-index.netbsd.org/tech-userlevel/2000/02/23/0000.html


From: Jason Thorpe <thorpej@nas.nasa.gov>
Subject: Re: dl* functions on ELF platforms 
Date: Wed, 23 Feb 2000 10:28:21 -0800
Message-ID: <200002231828.KAA24266@lestat.nas.nasa.gov>

> Why don't we add --export-dynamic to the building of our crt0.o?  Would
> that help?

It has three problems:

  - crt0.o is not shared library nor shared executable but relocatable
    object.  And, "ld" cannot accept both -r and -shared option at the
    same time.  Thus, crt0.o cannot have .dyamic section and
    --export-dynamic is invalid.

  - --export-dynamic is probably not automatically inherited to
    the executables which are linked with crt0.o, even if "ld" could
    accept both -r and -shared option at the same time. (But, I don't know
    that such feature is adapted to the ELF specification.)
    We need to specify the --export-dynamic at the link time of any shared
    executable.

  - It cannot affect any old executables.
    If we could not keep binary compatibility, it is not problem...

Therefore, it seems difficult to solve this problem by using --export-dynamic
option.


--
Takuya SHIOZAKI - Chair of IMOU.
The I18n/M17n project On Unix environments (IMOU), Japan.