[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug ld/6744] --export-dynamic does nothing for Cygwin .exe's

From: dave dot korn dot cygwin at gmail dot com
Subject: [Bug ld/6744] --export-dynamic does nothing for Cygwin .exe's
Date: 24 Mar 2009 04:07:50 -0000

------- Additional Comments From dave dot korn dot cygwin at gmail dot com  
2009-03-24 04:07 -------
(In reply to comment #3)
> (In reply to comment #2)
> > --export-dynamic is an ELF format option, and --export-all-symbols is the PE
> > equivalent.
> Dave, thanks for looking at this.  The ld texinfo docs say nothing about
> --export-dynamic being ELF-specific, so if this is indeed the case, that 
> should
> be made clear.

  Well it's strongly implied by the wording "When creating a dynamically linked
executable ..." that it's not going to apply to platforms that don't support
dynamically linked executables.  This may also imply that the scope is slightly
wider than my assumption of "just Elf", which means the docs maybe are OK as
they are.

  I'm a little (only a little) concerned that if we make it a synonym on PE For
--export-all-symbols, it might confuse people into thinking that other linker
options related to dynamic objects would also function as expected, but they
seem to all be clearly documented as to which platforsm they support.  It would
certainly be technically correct if libtool chose to use --e-a-s rather than
--e-d when linking for a cygwin target, since it's the target-specific 

  Why not post an RFC on the binutils list asking if anyone can see a downside
of making --e-d a synonym for --e-a-s?



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]