What's the deal with ld and cygwin32??

What's the deal with ld and cygwin32??

[Fernando D. Mato Mira]

Hello,

  `configure' of binutils takes a HUGE time because everytime it goes
`checking for ld used by GCC' it takes a LONG time just to figure out
`ld is not GNU ld' (??!!). But at least it works. When I configure gdb,
it just refuses to use it. Any ideas?

bash-2.02$ echo $PATH
/cygnus/CYGWIN~1/H-I586~1/bin:/usr/local/i686-pc-cygwin32/bin:/usr/local/i586-pc
-cygwin32/bin:/usr/local/bin:/WINNT/system32:/WINNT:/programfiles/devstudio/shar
edide/bin/ide:/programfiles/devstudio/sharedide/bin:/programfiles/devstudio/vc/b
in:/Program Files/XEmacs/XEmacs-21.0-b62/i386-pc-win32://F/matomira/win/RogueWav
e/workspaces/WINNT4/MSVC50/15s/lib

Thanks in advance,

Fernando D. Mato Mira                                                        
Real-Time SW Engineering & Networking
Advanced Systems Engineering Division                                                               
CSEM - Centre Suisse d'Electronique et de Microtechnique 
Jaquet-Droz 1                                                                    Email:   matomira AT acm DOT org
CH-2007 Neuchatel                                                            Phone:    +41 (32) 720-5152
Switzerland                                                                       FAX:        +41 (32) 720-5720

http://www.csem.ch/         http://www.vrai.com/          http://ligwww.epfl.ch/matomira.html

Re: What's the deal with ld and cygwin32??

[Mumit Khan]

On Mon, 15 Feb 1999, Fernando D. Mato Mira wrote:

>   `configure' of binutils takes a HUGE time because everytime it goes
> `checking for ld used by GCC' it takes a LONG time just to figure out
> `ld is not GNU ld' (??!!). But at least it works. When I configure gdb,
> it just refuses to use it. Any ideas?

It's being looked at. For now,
  
  $ env LD=/path/to/ld configure [options]

I and others build egcs/binutils/gdb/etc in a single tree, and never run
into this problem/bug.

You may want to subscribe to cygwin mailing list where these issues are
discussed. See http://sourceware.cygnus.com/cygwin/ for info on joining
the list.

fyi, you should really configure Cygwin egcs as i586-cygwin32 for variety
of reasons.

Regards,
Mumit

Re: What's the deal with ld and cygwin32??

[Gary V. Vaughan]

Mumit Khan wrote:
> 
> On Mon, 15 Feb 1999, Fernando D. Mato Mira wrote:
> 
> >   `configure' of binutils takes a HUGE time because everytime it
> > goes `checking for ld used by GCC' it takes a LONG time just to
> > figure out `ld is not GNU ld' (??!!). But at least it works. When I
> > configure gdb, it just refuses to use it. Any ideas?
> 
> It's being looked at. For now,
> 
>   $ env LD=/path/to/ld configure [options]
> 
> I and others build egcs/binutils/gdb/etc in a single tree, and never
> run into this problem/bug.

libtool-1.2b and earlier had a problem with backslash path separators
which bash would treat as escape meta-chars causing ld to be not found
at all!  I suspect that you are using an ltconfig generated by
libtool-1.2b or earlier.

Ever since 1.2d libtool now converts `gcc --print-prog-name=ld` to a UNC
path which cygwin b19 and b20 can understand.  I need to fix this
*again* for libtool-1.3, because the latest cygwin snapshots don't grok
UNC paths anymore =(O|

Cheers,
	Gary.

What's the deal with ld and cygwin32??

[Fernando D. Mato Mira]

Hello,

  `configure' of binutils takes a HUGE time because everytime it goes
`checking for ld used by GCC' it takes a LONG time just to figure out
`ld is not GNU ld' (??!!). But at least it works. When I configure gdb,
it just refuses to use it. Any ideas?

bash-2.02$ echo $PATH
/cygnus/CYGWIN~1/H-I586~1/bin:/usr/local/i686-pc-cygwin32/bin:/usr/local/i586-pc
-cygwin32/bin:/usr/local/bin:/WINNT/system32:/WINNT:/programfiles/devstudio/shar
edide/bin/ide:/programfiles/devstudio/sharedide/bin:/programfiles/devstudio/vc/b
in:/Program Files/XEmacs/XEmacs-21.0-b62/i386-pc-win32://F/matomira/win/RogueWav
e/workspaces/WINNT4/MSVC50/15s/lib

Thanks in advance,

Fernando D. Mato Mira                                                        
Real-Time SW Engineering & Networking
Advanced Systems Engineering Division                                                               
CSEM - Centre Suisse d'Electronique et de Microtechnique 
Jaquet-Droz 1                                                                    Email:   matomira AT acm DOT org
CH-2007 Neuchatel                                                            Phone:    +41 (32) 720-5152
Switzerland                                                                       FAX:        +41 (32) 720-5720

http://www.csem.ch/         http://www.vrai.com/          http://ligwww.epfl.ch/matomira.html

Re: What's the deal with ld and cygwin32??

[Mumit Khan]

On Mon, 15 Feb 1999, Fernando D. Mato Mira wrote:

>   `configure' of binutils takes a HUGE time because everytime it goes
> `checking for ld used by GCC' it takes a LONG time just to figure out
> `ld is not GNU ld' (??!!). But at least it works. When I configure gdb,
> it just refuses to use it. Any ideas?

It's being looked at. For now,
  
  $ env LD=/path/to/ld configure [options]

I and others build egcs/binutils/gdb/etc in a single tree, and never run
into this problem/bug.

You may want to subscribe to cygwin mailing list where these issues are
discussed. See http://sourceware.cygnus.com/cygwin/ for info on joining
the list.

fyi, you should really configure Cygwin egcs as i586-cygwin32 for variety
of reasons.

Regards,
Mumit

Re: What's the deal with ld and cygwin32??

[Gary V. Vaughan]

Mumit Khan wrote:
> 
> On Mon, 15 Feb 1999, Fernando D. Mato Mira wrote:
> 
> >   `configure' of binutils takes a HUGE time because everytime it
> > goes `checking for ld used by GCC' it takes a LONG time just to
> > figure out `ld is not GNU ld' (??!!). But at least it works. When I
> > configure gdb, it just refuses to use it. Any ideas?
> 
> It's being looked at. For now,
> 
>   $ env LD=/path/to/ld configure [options]
> 
> I and others build egcs/binutils/gdb/etc in a single tree, and never
> run into this problem/bug.

libtool-1.2b and earlier had a problem with backslash path separators
which bash would treat as escape meta-chars causing ld to be not found
at all!  I suspect that you are using an ltconfig generated by
libtool-1.2b or earlier.

Ever since 1.2d libtool now converts `gcc --print-prog-name=ld` to a UNC
path which cygwin b19 and b20 can understand.  I need to fix this
*again* for libtool-1.3, because the latest cygwin snapshots don't grok
UNC paths anymore =(O|

Cheers,
	Gary.

Re: What's the deal with ld and cygwin32??

[Fernando D. Mato Mira]

At 04:01 PM 2/15/99 +0100, I wrote:
> `configure' of binutils takes a HUGE time because everytime it goes 
>`checking for ld used by GCC' it takes a LONG time just to figure out 
>`ld is not GNU ld' (??!!). But at least it works. When I configure gdb, 
>it just refuses to use it. Any ideas?

Well, it is ltconfig's fault. ltconfig looks for `ld', not `ld.exe'. 
Setting LD to the proper absolute path bypasses the above problem.


Fernando D. Mato Mira                                                        
Real-Time SW Engineering & Networking
Advanced Systems Engineering Division                                                               
CSEM - Centre Suisse d'Electronique et de Microtechnique 
Jaquet-Droz 1                                                                    Email:   matomira AT acm DOT org
CH-2007 Neuchatel                                                            Phone:    +41 (32) 720-5152
Switzerland                                                                       FAX:        +41 (32) 720-5720

http://www.csem.ch/         http://www.vrai.com/          http://ligwww.epfl.ch/matomira.html

Re: What's the deal with ld and cygwin32??

[Fernando D. Mato Mira]

At 04:01 PM 2/15/99 +0100, I wrote:
> `configure' of binutils takes a HUGE time because everytime it goes 
>`checking for ld used by GCC' it takes a LONG time just to figure out 
>`ld is not GNU ld' (??!!). But at least it works. When I configure gdb, 
>it just refuses to use it. Any ideas?

Well, it is ltconfig's fault. ltconfig looks for `ld', not `ld.exe'. 
Setting LD to the proper absolute path bypasses the above problem.


Fernando D. Mato Mira                                                        
Real-Time SW Engineering & Networking
Advanced Systems Engineering Division                                                               
CSEM - Centre Suisse d'Electronique et de Microtechnique 
Jaquet-Droz 1                                                                    Email:   matomira AT acm DOT org
CH-2007 Neuchatel                                                            Phone:    +41 (32) 720-5152
Switzerland                                                                       FAX:        +41 (32) 720-5720

http://www.csem.ch/         http://www.vrai.com/          http://ligwww.epfl.ch/matomira.html