This is the mail archive of the cygwin@sourceware.cygnus.com mailing list for the Cygwin project.


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

Re: what can link.exe do that cygwin32-ld can't ?


Not that I can tell no, the only relocatable .dll that I have been
able to make since I switched to B18 is cygwin.dll.

Every other .dll that I have tried to link with cygwin.dll and with a .reloc section gives
unable to run XXX.exe

attached are GNUmakefiles for a project with a dll,
when linked using mingw32 and either 2pass or 3pass the .dll and .exe both work
correctly, when linked with -lcygwin the .exe always gives
an unable to run m:\path\demo.exe dialog box, the only difference
obviously is in the startup files, and the libc services provider.

The same project linked with a nonrelocateble dll will link/run
using either mingw32 or B18.

Also when linked with B17.1 using the 2pass method the dll and exe
both worked.

If anyone can tell me what I'm doing wrong I would appreciate
the comments, otherwise I would speculate that moving _reent_data
into cygwin.dll wasn't as good of an idea as was originally thought.

On Sun, 13 Jul 1997 20:26:49 -0700, you wrote:
>
>   and if so, does this fix makeing .reloc dll's & exe's
>   with B18?
>
>Doesn't that have more to do with running ld and dlltool multiple
>times?
>
>Ian

(*jeffdb@netzone.nospam.com)
Remove *&.nospam from the above to reply
         Mikey

GNUmakefile

GNUmakefile.2pass

GNUmakefile.3pass

cygwin32.mak


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