Solution to DLLWRAP problem in Cygwin v1.0 CD

Solution to DLLWRAP problem in Cygwin v1.0 CD

[Mumit Khan]

Someone had mentioned a problem with not being able to create DLLs with
dllwrap in Cygwin v1.0 CD (commercial version of Cygwin). Looks like
the Cygwin v1.0 sources were frozen quite some time ago, and it doesn't
have some of the fixes that went in before cygwin b20.1. The particular
change in question was when Cygwin's name changed from "cygwin32" to
"cygwin", there was a corresponding change in dllwrap, which checks for
the target name to figure out what to do. 

Solution? Add the --target=i686-cygwin32 option to dllwrap (the name
was changed to i686-cygwin, and the corresponding change in dllwrap
was missed in v1.0). Actually, just --target=cygwin32 will work as
well, since dllwrap just checks for "cygwin32" in target name.
  
  $ dllwrap --target=cygwin32 [rest of option]

If you're using any of my makefiles, just add --target=cygwin32 to
DLLWRAP_FLAGS variable.

Sorry it took so long. Thanks to Cygnus, I now have a v1.0 CD so
I can debug these problems.

Regards,
Mumit



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Solution to DLLWRAP problem in Cygwin v1.0 CD

[Chris Faylor]

On Tue, Nov 23, 1999 at 01:19:51AM -0600, Mumit Khan wrote:
>Someone had mentioned a problem with not being able to create DLLs with
>dllwrap in Cygwin v1.0 CD (commercial version of Cygwin). Looks like
>the Cygwin v1.0 sources were frozen quite some time ago, and it doesn't
>have some of the fixes that went in before cygwin b20.1. The particular
>change in question was when Cygwin's name changed from "cygwin32" to
>"cygwin", there was a corresponding change in dllwrap, which checks for
>the target name to figure out what to do. 

Hmm.  The stuff on the CD should have been cut at least six months after
B20.1.  The change logs seem to indicate that it has some cygwin32 ->
cygwin changes.

However, our master sources also check for "cygwin32" rather than
cygwin, so I guess this is why.  Geoff checked in some changes back in
October but they didn't specifically change the string which searched
for cygwin32.

Is there something different in the external binutils repository?

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Solution to DLLWRAP problem in Cygwin v1.0 CD

[Mumit Khan]

On Tue, 23 Nov 1999, Chris Faylor wrote:

> Hmm.  The stuff on the CD should have been cut at least six months after
> B20.1.  The change logs seem to indicate that it has some cygwin32 ->
> cygwin changes.
>
> However, our master sources also check for "cygwin32" rather than
> cygwin, so I guess this is why.  Geoff checked in some changes back in
> October but they didn't specifically change the string which searched
> for cygwin32.

> Is there something different in the external binutils repository?

The problem is there as well. The reason v1.0 exposes this problem is 
by changing the target name from i586-cygwin32, used by b20.1 even 
though internal names were changed from cygwin32 to cygwin, to 
i686-cygwin used by v1.0.

I'll submit a change to binutils. May be a good time to grep for all
occurrances of "cygwin32" in all the development tools and see what
we come up with.

Regards,
Mumit



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Solution to DLLWRAP problem in Cygwin v1.0 CD

[Chris Faylor]

On Tue, Nov 23, 1999 at 03:47:24PM -0600, Mumit Khan wrote:
>On Tue, 23 Nov 1999, Chris Faylor wrote:
>
>> Hmm.  The stuff on the CD should have been cut at least six months after
>> B20.1.  The change logs seem to indicate that it has some cygwin32 ->
>> cygwin changes.
>>
>> However, our master sources also check for "cygwin32" rather than
>> cygwin, so I guess this is why.  Geoff checked in some changes back in
>> October but they didn't specifically change the string which searched
>> for cygwin32.
>
>> Is there something different in the external binutils repository?
>
>I'll submit a change to binutils. May be a good time to grep for all
>occurrances of "cygwin32" in all the development tools and see what
>we come up with.

Actually, I thought I'd done that already.  There was obviously a flaw
in my search.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Solution to DLLWRAP problem in Cygwin v1.0 CD

[Geoffrey Noer]

On Tue, Nov 23, 1999, Chris Faylor wrote:
[...]
> >I'll submit a change to binutils. May be a good time to grep for all
> >occurrances of "cygwin32" in all the development tools and see what
> >we come up with.
> 
> Actually, I thought I'd done that already.  There was obviously a flaw
> in my search.

And I had thought I had been pretty thorough as well.  Guess we missed
something.  *sigh*

-- 
Geoffrey Noer		Email: noer@cygnus.com
Cygnus Solutions

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Solution to DLLWRAP problem in Cygwin v1.0 CD

[Chris Faylor]

On Tue, Nov 23, 1999 at 01:19:51AM -0600, Mumit Khan wrote:
>Someone had mentioned a problem with not being able to create DLLs with
>dllwrap in Cygwin v1.0 CD (commercial version of Cygwin). Looks like
>the Cygwin v1.0 sources were frozen quite some time ago, and it doesn't
>have some of the fixes that went in before cygwin b20.1. The particular
>change in question was when Cygwin's name changed from "cygwin32" to
>"cygwin", there was a corresponding change in dllwrap, which checks for
>the target name to figure out what to do. 

Hmm.  The stuff on the CD should have been cut at least six months after
B20.1.  The change logs seem to indicate that it has some cygwin32 ->
cygwin changes.

However, our master sources also check for "cygwin32" rather than
cygwin, so I guess this is why.  Geoff checked in some changes back in
October but they didn't specifically change the string which searched
for cygwin32.

Is there something different in the external binutils repository?

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Solution to DLLWRAP problem in Cygwin v1.0 CD

[Geoffrey Noer]

On Tue, Nov 23, 1999, Chris Faylor wrote:
[...]
> >I'll submit a change to binutils. May be a good time to grep for all
> >occurrances of "cygwin32" in all the development tools and see what
> >we come up with.
> 
> Actually, I thought I'd done that already.  There was obviously a flaw
> in my search.

And I had thought I had been pretty thorough as well.  Guess we missed
something.  *sigh*

-- 
Geoffrey Noer		Email: noer@cygnus.com
Cygnus Solutions

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Solution to DLLWRAP problem in Cygwin v1.0 CD

[Chris Faylor]

On Tue, Nov 23, 1999 at 03:47:24PM -0600, Mumit Khan wrote:
>On Tue, 23 Nov 1999, Chris Faylor wrote:
>
>> Hmm.  The stuff on the CD should have been cut at least six months after
>> B20.1.  The change logs seem to indicate that it has some cygwin32 ->
>> cygwin changes.
>>
>> However, our master sources also check for "cygwin32" rather than
>> cygwin, so I guess this is why.  Geoff checked in some changes back in
>> October but they didn't specifically change the string which searched
>> for cygwin32.
>
>> Is there something different in the external binutils repository?
>
>I'll submit a change to binutils. May be a good time to grep for all
>occurrances of "cygwin32" in all the development tools and see what
>we come up with.

Actually, I thought I'd done that already.  There was obviously a flaw
in my search.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Solution to DLLWRAP problem in Cygwin v1.0 CD

[Mumit Khan]

On Tue, 23 Nov 1999, Chris Faylor wrote:

> Hmm.  The stuff on the CD should have been cut at least six months after
> B20.1.  The change logs seem to indicate that it has some cygwin32 ->
> cygwin changes.
>
> However, our master sources also check for "cygwin32" rather than
> cygwin, so I guess this is why.  Geoff checked in some changes back in
> October but they didn't specifically change the string which searched
> for cygwin32.

> Is there something different in the external binutils repository?

The problem is there as well. The reason v1.0 exposes this problem is 
by changing the target name from i586-cygwin32, used by b20.1 even 
though internal names were changed from cygwin32 to cygwin, to 
i686-cygwin used by v1.0.

I'll submit a change to binutils. May be a good time to grep for all
occurrances of "cygwin32" in all the development tools and see what
we come up with.

Regards,
Mumit



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Solution to DLLWRAP problem in Cygwin v1.0 CD

[Mumit Khan]

Someone had mentioned a problem with not being able to create DLLs with
dllwrap in Cygwin v1.0 CD (commercial version of Cygwin). Looks like
the Cygwin v1.0 sources were frozen quite some time ago, and it doesn't
have some of the fixes that went in before cygwin b20.1. The particular
change in question was when Cygwin's name changed from "cygwin32" to
"cygwin", there was a corresponding change in dllwrap, which checks for
the target name to figure out what to do. 

Solution? Add the --target=i686-cygwin32 option to dllwrap (the name
was changed to i686-cygwin, and the corresponding change in dllwrap
was missed in v1.0). Actually, just --target=cygwin32 will work as
well, since dllwrap just checks for "cygwin32" in target name.
  
  $ dllwrap --target=cygwin32 [rest of option]

If you're using any of my makefiles, just add --target=cygwin32 to
DLLWRAP_FLAGS variable.

Sorry it took so long. Thanks to Cygnus, I now have a v1.0 CD so
I can debug these problems.

Regards,
Mumit



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com