RE: global_symbol_pipe not picking up an initialized global variable with msvc

2009-08-17 Thread David Byron
> I tried to reproduce (but failed, so I think the symbol pipe is > definitely out of the loop): I agree. I was on the road to put this together when I found the broken UTL_EXPORT as the culprit. Thanks for going to the trouble to build a simple example. By bad for not doing this before I poste

Re: global_symbol_pipe not picking up an initialized global variable with msvc

2009-08-17 Thread Peter Rosin
Den 2009-08-15 21:41 skrev Peter Rosin: However, to be 100% certain and eliminate any doubt you can - if you wish - configure with NM=nm (instead of dumpbin -symbols) and see if that makes any difference. I tried to reproduce (but failed, so I think the symbol pipe is definitely out of the loop

Re: global_symbol_pipe not picking up an initialized global variable with msvc

2009-08-16 Thread Duft Markus
> Message: 1 > Date: Sat, 15 Aug 2009 21:41:26 +0200 > Subject: Re: global_symbol_pipe not picking up an initialized global > variable with msvc > Message-ID: <4a870f66.1080...@lysator.liu.se> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > De

Re: global_symbol_pipe not picking up an initialized global variable with msvc

2009-08-15 Thread Peter Rosin
Den 2009-08-14 23:41 skrev David Byron: I'm pretty sure I'm running into a pr-msvc-support-specific problem but I'm still learning about libtool so... I'm trying to get rid of unresolved externs when linked an executable against a libtool shared library compiled with msvc. The unresolved extern