gcc -print-prog-name=ld with mingw32 binaries

gcc -print-prog-name=ld with mingw32 binaries

[Richard Hickling]

'gcc -print-prog-name=ld' produces just 'ld' with
the mingw32 binaries (whereas with the cygwin
binaries the full path-name + .exe is produced).
I guess it should be consistent one way or the
other.


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

Re: gcc -print-prog-name=ld with mingw32 binaries

[Mumit Khan]

Richard Hickling <hicklinr@mcd.alcatel.be> writes:
> 'gcc -print-prog-name=ld' produces just 'ld' with
> the mingw32 binaries (whereas with the cygwin
> binaries the full path-name + .exe is produced).
> I guess it should be consistent one way or the
> other.

I on the other hand see no inconsistency. I have other systems, albeit 
without GNU as and GNU ld, where it does the same thing.

If you really want it that way for some reason, do the following at the
expense of disks space:
  
  $ cd /egcs-1.1.2/i386-mingw32
  $ mkdir bin
  $ cd bin
  $ cd /egcs-1.1.2/bin/{as,ld} .

Now it'll do what you want. I won't do this in the distributions; these
are large enough as it is.

Mumit


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

Re: gcc -print-prog-name=ld with mingw32 binaries

[Richard Hickling]

> Richard Hickling <hicklinr@mcd.alcatel.be> writes:
> > 'gcc -print-prog-name=ld' produces just 'ld' with
> > the mingw32 binaries (whereas with the cygwin
> > binaries the full path-name + .exe is produced).

> I on the other hand see no inconsistency. I have other systems, albeit
> without GNU as and GNU ld, where it does the same thing.
> If you really want it that way for some reason, do the following at the
> expense of disks space:
>   $ cd /egcs-1.1.2/i386-mingw32
>   $ mkdir bin
>   $ cd bin
>   $ cd /egcs-1.1.2/bin/{as,ld} .

cp of course, but ...

> Now it'll do what you want.

Obviously I'm missing something.  It behaves in the same way.

The mingw32 targeted compiler is version egcs-2.91.66 19990314, whereas the
cygwin targeted one is egcs-2.91.57 19980901 (the Cygwin release I see).
These were downloaded from
ftp://ftp.xraylith.wisc.edu/pub/khan/gnu-win32/cygwin/egcs-1.1.2/egcs-1.1.2-cygb20.tar.gz

and
ftp://ftp.xraylith.wisc.edu/pub/khan/gnu-win32/mingw32/egcs-1.1.2/egcs-1.1.2-mingw32.zip

today.

I prefer the behaviour of the 2.91.57 - since it gives more information,
but I'd like to use the most recent compiler.




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

Re: gcc -print-prog-name=ld with mingw32 binaries

[Mumit Khan]

Richard Hickling <hicklinr@mcd.alcatel.be> writes:
> >   $ cd /egcs-1.1.2/i386-mingw32
> >   $ mkdir bin
> >   $ cd bin
> >   $ cd /egcs-1.1.2/bin/{as,ld} .
        ^^

      $ cp /egcs-1.1.2/bin/{as,ld}.exe .
      (obvious typo).
> 
> cp of course, but ...
> 
> > Now it'll do what you want.
> 
> Obviously I'm missing something.  It behaves in the same way.

Really? Here's mine:

$ ls -l c:/egcs-1.1.2/i386-mingw32/bin/
total 618
-rwxrwxrwx   1 khan     Everyone   325120 May 11 18:41 as.exe
-rwxrwxrwx   1 khan     Everyone   308224 May 11 18:41 ld.exe
$ gcc -print-prog-name=as
c:\egcs-1.1.2\lib\gcc-lib\i386-mingw32\egcs-2.91.66\..\..\..\..\i386-mingw32\bin\as.exe

(don't be fooled by the '$' prompt; it's really an NT machine).

> The mingw32 targeted compiler is version egcs-2.91.66 19990314, whereas the
> cygwin targeted one is egcs-2.91.57 19980901 (the Cygwin release I see).
> These were downloaded from
> ftp://ftp.xraylith.wisc.edu/pub/khan/gnu-win32/cygwin/egcs-1.1.2/egcs-1.1.2-c
> ygb20.tar.gz
> 
> and
> ftp://ftp.xraylith.wisc.edu/pub/khan/gnu-win32/mingw32/egcs-1.1.2/egcs-1.1.2-
> mingw32.zip
> 
> today.
> 
> I prefer the behaviour of the 2.91.57 - since it gives more information,
> but I'd like to use the most recent compiler.
> 

What're you talking about? Both have the same version, egcs-2.91.66, which
translates to egcs-1.1.2.

Did you actually install both and run ``gcc -v'' and see what gives?

Also, keep in mind that the Cygwin and Mingw native compilers are two
different compilers for two different runtimes. I have no intention of
getting them to look alike, since they're not alike; my concern is to
get these compilers to do their job.

If you feel there are inconsistencies you'd like to see gone, please feel
free to send patches to solve them. 

Regards,
Mumit


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

Re: gcc -print-prog-name=ld with mingw32 binaries

[Mumit Khan]

Richard Hickling <hicklinr@mcd.alcatel.be> writes:
> 'gcc -print-prog-name=ld' produces just 'ld' with
> the mingw32 binaries (whereas with the cygwin
> binaries the full path-name + .exe is produced).
> I guess it should be consistent one way or the
> other.

I on the other hand see no inconsistency. I have other systems, albeit 
without GNU as and GNU ld, where it does the same thing.

If you really want it that way for some reason, do the following at the
expense of disks space:
  
  $ cd /egcs-1.1.2/i386-mingw32
  $ mkdir bin
  $ cd bin
  $ cd /egcs-1.1.2/bin/{as,ld} .

Now it'll do what you want. I won't do this in the distributions; these
are large enough as it is.

Mumit


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

Re: gcc -print-prog-name=ld with mingw32 binaries

[Mumit Khan]

Richard Hickling <hicklinr@mcd.alcatel.be> writes:
> >   $ cd /egcs-1.1.2/i386-mingw32
> >   $ mkdir bin
> >   $ cd bin
> >   $ cd /egcs-1.1.2/bin/{as,ld} .
        ^^

      $ cp /egcs-1.1.2/bin/{as,ld}.exe .
      (obvious typo).
> 
> cp of course, but ...
> 
> > Now it'll do what you want.
> 
> Obviously I'm missing something.  It behaves in the same way.

Really? Here's mine:

$ ls -l c:/egcs-1.1.2/i386-mingw32/bin/
total 618
-rwxrwxrwx   1 khan     Everyone   325120 May 11 18:41 as.exe
-rwxrwxrwx   1 khan     Everyone   308224 May 11 18:41 ld.exe
$ gcc -print-prog-name=as
c:\egcs-1.1.2\lib\gcc-lib\i386-mingw32\egcs-2.91.66\..\..\..\..\i386-mingw32\bin\as.exe

(don't be fooled by the '$' prompt; it's really an NT machine).

> The mingw32 targeted compiler is version egcs-2.91.66 19990314, whereas the
> cygwin targeted one is egcs-2.91.57 19980901 (the Cygwin release I see).
> These were downloaded from
> ftp://ftp.xraylith.wisc.edu/pub/khan/gnu-win32/cygwin/egcs-1.1.2/egcs-1.1.2-c
> ygb20.tar.gz
> 
> and
> ftp://ftp.xraylith.wisc.edu/pub/khan/gnu-win32/mingw32/egcs-1.1.2/egcs-1.1.2-
> mingw32.zip
> 
> today.
> 
> I prefer the behaviour of the 2.91.57 - since it gives more information,
> but I'd like to use the most recent compiler.
> 

What're you talking about? Both have the same version, egcs-2.91.66, which
translates to egcs-1.1.2.

Did you actually install both and run ``gcc -v'' and see what gives?

Also, keep in mind that the Cygwin and Mingw native compilers are two
different compilers for two different runtimes. I have no intention of
getting them to look alike, since they're not alike; my concern is to
get these compilers to do their job.

If you feel there are inconsistencies you'd like to see gone, please feel
free to send patches to solve them. 

Regards,
Mumit


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

Re: gcc -print-prog-name=ld with mingw32 binaries

[Richard Hickling]

> Richard Hickling <hicklinr@mcd.alcatel.be> writes:
> > 'gcc -print-prog-name=ld' produces just 'ld' with
> > the mingw32 binaries (whereas with the cygwin
> > binaries the full path-name + .exe is produced).

> I on the other hand see no inconsistency. I have other systems, albeit
> without GNU as and GNU ld, where it does the same thing.
> If you really want it that way for some reason, do the following at the
> expense of disks space:
>   $ cd /egcs-1.1.2/i386-mingw32
>   $ mkdir bin
>   $ cd bin
>   $ cd /egcs-1.1.2/bin/{as,ld} .

cp of course, but ...

> Now it'll do what you want.

Obviously I'm missing something.  It behaves in the same way.

The mingw32 targeted compiler is version egcs-2.91.66 19990314, whereas the
cygwin targeted one is egcs-2.91.57 19980901 (the Cygwin release I see).
These were downloaded from
ftp://ftp.xraylith.wisc.edu/pub/khan/gnu-win32/cygwin/egcs-1.1.2/egcs-1.1.2-cygb20.tar.gz

and
ftp://ftp.xraylith.wisc.edu/pub/khan/gnu-win32/mingw32/egcs-1.1.2/egcs-1.1.2-mingw32.zip

today.

I prefer the behaviour of the 2.91.57 - since it gives more information,
but I'd like to use the most recent compiler.




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

gcc -print-prog-name=ld with mingw32 binaries

[Richard Hickling]

'gcc -print-prog-name=ld' produces just 'ld' with
the mingw32 binaries (whereas with the cygwin
binaries the full path-name + .exe is produced).
I guess it should be consistent one way or the
other.


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