[Mingw-users] dllwrap related bug? (possibly OT)

[Paul G. <pga...@co...>]

I have been seeing some weird things going on when using dllwrap.  As I am aware dllwrap is being deprecated, I am 
hesitant to ask these questions as they may not have any bearing on anything related to Mingw.

Nevertheless I will push on...
[Using NT4 Wks -- SP6a, Mingw 3.0.0.1 under Msys (not using msysdvlpr)]

	Does dllwrap assign the preferred base address for .dlls or is that done by another agent such as ld?

	(Personally I had, in the past, and up until now, hypothesized that ld was responsible for actually "creating" a 
Mingw generated .dll/module -- is this an accurate hypothesis?).

	If dllwrap (or dlltool) is expected to assign a preferred base address for each .dll that ld eventually 
generates/creates, then how is it possible that an agent (one of three agents, dllwrap, dlltool, or ld) can assign the 
exact same preferred base address for two entirely different .dlls?

	If ld is responsible for assigning the preferred base addresses for each .dll that ld eventually creates, how is it 
possible for ld to not assign a different preferred base address for every single Mingw generated .dll?

	I would appreciate any feedback or discussion on this.

	Thanks,

		Paul G.