This is the mail archive of the mailing list for the binutils project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Dynamically wrap non dynamic symbol

Reposting on the mailing list too. (sorry about that)

On 21 September 2017 at 20:21, Andreas Schwab <> wrote:
> On Sep 21 2017, Christian Gagneraud <> wrote:
>> main() uses Bar and Bar inherits Foo. When the compiler is run on any
>> of these files, it has no clue where other's unit symbol are/will be
>> located, it has even no clue if it's a dynamic symbol or not (it is
>> only aware of the class declaration).
> A non-default visibility attribute can change the picture.
> Andreas.
> --
> Andreas Schwab, SUSE Labs,
> GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
> "And now for something completely different."

Yes, interesting...

But i would like to find a non-intrusive method (ideally).
At first the requirement was: you cannot require the executable to be
compile/linked with special options.

I then gave up, and tried to only request a bit of magic in the final LDFLAGS.
Now, i don't want to ask the user to mark individually the symbol
visibility (like you have to do on Windows when building a dll).

Anyway, it's an interesting idea, maybe i can leverage on the linker
script, or the export file, i saw it does accept wild card pattern...

Will have to dig further, thanks for the tip! ;)


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]