public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
* [ANN] EGCS-1.1.2 binaries for Cygwin b20.1 available
@ 1999-03-16 12:10 Mumit Khan
       [not found] ` < 199903162010.OAA04606@modi.xraylith.wisc.edu >
  1999-03-31 19:45 ` Mumit Khan
  0 siblings, 2 replies; 14+ messages in thread
From: Mumit Khan @ 1999-03-16 12:10 UTC (permalink / raw)
  To: cygwin

EGCS 1.1.2 for Cygwin b20.1+ (i586-cygwin32) -- Release information
===================================================================

Release date: Mar 16, 1998.

I'd like to announce egcs-1.1.2 for Cygwin B20.x (i586-cygwin32).  These 
are meant to replace the b20.1 compiler, so the pathnames are compatible 
with b20.1. This has only been tested with Cygwin B20.1, and will NOT
work previous releases such as Cygwin B20.

What's in this package?
  
  egcs-1.1.2: The compilers for C, C++, ObjC and F77 plus runtime
    libraries. Also provides a working info viewer (info.exe).

  egcs-1.1.2-docs: Provides the documentation in GNU info format.

What's not in this package?
  
  libg++: Sorry, but it's about time I acted on my long-standing threat 
    to remove this deprecated library.

Where?
  
  Web: http://www.xraylith.wisc.edu/~khan/software/gnu-win32/
  FTP: ftp://ftp.xraylith.wisc.edu/pub/khan/gnu-win32/cygwin/egcs-1.1.2/

  Please visit the web page before you attempt to download/install. It
  may address problems you might run into.

Installation? 

  Just unpack into the existing Cygnus installation tree and you're set 
  to go. See the INSTALL file for more info.

Disk space?
   
  About 12M, give or take a few.

Where to report bugs?

  Report configuration and Win32 specific bugs to me, GCC specific bugs 
  egcs-bugs, and always copy Cygwin mailing list so others can see it
  as well. If you send me email, please do have patience, since I usually 
  do not have the time to respond to each email right away.

Regards,
Mumit -- khan@xraylith.wisc.edu
http://www.xraylith.wisc.edu/~khan/


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

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [ANN] EGCS-1.1.2 binaries for Cygwin b20.1 available
       [not found] ` < 199903162010.OAA04606@modi.xraylith.wisc.edu >
@ 1999-03-16 21:37   ` Theodore Jump
       [not found]     ` < 36ef3b5d.2548875@smtp.tertius.com >
  1999-03-31 19:45     ` Theodore Jump
  0 siblings, 2 replies; 14+ messages in thread
From: Theodore Jump @ 1999-03-16 21:37 UTC (permalink / raw)
  To: Mumit Khan; +Cc: cygwin

Mumit,

I want to thank you for your work, but I've a quirk I can't quite figure out
preventing me from using the new release for Cygwin code builds.

Basically, it appears that 'as' is being called with an incomplete command line
in that it's not being fed a proper file name (it's being fed a ^M as the file
name), thus the build of even a trivial file fails, e.g.: g++ test.cc

I tried this altering the state of my CYGWIN env-var, removing either and both
of 'tty' and 'binmode' but this did not change the behavior at all.

Building either a C or CPP file results in build failure, I have not tested
other types.  The same build error occurs if I'm trying to generate an .o file
or a .exe file.

The error reported is:

    Assembler messages:
     for reading.open
    : No such file or directory

... and occurs with or without the '-save-temps' option.

I'm including my test case source, 'gcc -v' output, and 'cygcheck -s' output in
the hopes that you can shed some light on this.

I hope I don't seem like a total putz for not figuring out what's causing this.

TIA,
-Ted

PS: The Mingw32 variant compiles and links my test case fine, it's just the
Cygwin variant (using in BASH or CMD) that's problematical for me.

-----------------------------------------------------------------------------
--- sample source -----------------------------------------------------------
-----------------------------------------------------------------------------

#include <iostream>

using namespace std;

int main(int,char**)
{
	cout << "hello" << endl;
	return 0;
}

-----------------------------------------------------------------------------
--- gcc -v output -----------------------------------------------------------
-----------------------------------------------------------------------------

Reading specs from
e:/gnu/Cygwin-B20/h-i586-cygwin32/bin/../lib/gcc-lib/i586-cygwin32/egcs-2.91.66/specs
gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release)

e:/gnu/Cygwin-B20/h-i586-cygwin32/bin/../lib/gcc-lib/i586-cygwin32/egcs-2.91.66/cpp.exe
-lang-c++ -v -iprefix
e:/gnu/Cygwin-B20/h-i586-cygwin32/bin/../lib/gcc-lib/i586-cygwin32/egcs-2.91.66/
-undef -D__GNUC__=2 -D__GNUG__=2 -D__cplusplus -D__GNUC_MINOR__=91 -Di386
-D_WIN32 -DWINNT -D_X86_=1 -D__STDC__=1
-D__stdcall=__attribute__((__stdcall__)) -D__cdecl=__attribute__((__cdecl__))
-D__declspec(x)=__attribute__((x)) -D__i386__ -D_WIN32 -D__WINNT__ -D_X86_=1
-D__STDC__=1 -D__stdcall=__attribute__((__stdcall__))
-D__cdecl=__attribute__((__cdecl__)) -D__declspec(x)=__attribute__((x))
-D__i386 -D__WINNT -Asystem(winnt) -Acpu(i386) -Amachine(i386) -D__EXCEPTIONS
-remap -D__CYGWIN32__ -D__CYGWIN__ test.cc /tmp/ccrG3iFV.ii
GNU CPP version egcs-2.91.66 19990314 (egcs-1.1.2 release) (80386, BSD syntax)
#include "..." search starts here:
#include <...> search starts here:

e:/gnu/Cygwin-B20/h-i586-cygwin32/bin/../lib/gcc-lib/i586-cygwin32/egcs-2.91.66/../../../../../include/g++

e:/gnu/Cygwin-B20/h-i586-cygwin32/bin/../lib/gcc-lib/i586-cygwin32/egcs-2.91.66/../../../../../include

e:/gnu/Cygwin-B20/h-i586-cygwin32/bin/../lib/gcc-lib/i586-cygwin32/egcs-2.91.66/../../../../i586-cygwin32/include

e:/gnu/Cygwin-B20/h-i586-cygwin32/bin/../lib/gcc-lib/i586-cygwin32/egcs-2.91.66/include
End of search list.

e:/gnu/Cygwin-B20/h-i586-cygwin32/bin/../lib/gcc-lib/i586-cygwin32/egcs-2.91.66/cc1plus.exe
/tmp/ccrG3iFV.ii -quiet -dumpbase test.cc -version -o /tmp/ccEkg9AL.s
GNU C++ version egcs-2.91.66 19990314 (egcs-1.1.2 release) (i586-cygwin32)
compiled by GNU C version egcs-2.91.66 19990314 (egcs-1.1.2 release).

e:/gnu/Cygwin-B20/h-i586-cygwin32/bin/../lib/gcc-lib/i586-cygwin32/egcs-2.91.66/../../../../i586-cygwin32/bin/as.exe
^M
Assembler messages:
Error: Can't open ^M for reading.
^M: No such file or directory

-----------------------------------------------------------------------------
--- cygcheck -s output ------------------------------------------------------
-----------------------------------------------------------------------------

Cygnus Win95/NT Configuration Diagnostics
Current System Time: Tue Mar 16 23:24:01 1999

WinNT Ver 4.0 build 1381 Service Pack 4

Path:	.
	/usr/local/bin
	/bin
	/usr/X11R6.4/bin

SysDir: E:\WINNT\System32
WinDir: E:\WINNT

CYGWIN = `tty binmode glob title strip_title'
HOME = `/home'
LIBRARY_PATH = `/usr/local/lib:/usr/X11/lib:/Cygwin-B20/H-i586-cygwin32/lib'
MAKE_MODE = `unix'
PWD = `/src'
TCL_LIBRARY = `/Cygwin-B20/share/tcl8.0'

Use `-r' to scan registry

a:\ fd  FAT        1Mb 100% CP    UN           MARVINROID
b:\ fd           N/A    N/A                    
c:\ hd  FAT      352Mb   2% CP    UN           BOOTSTRAP
d:\ hd  FAT      274Mb  94% CP    UN           PAGEFILE
e:\ hd  NTFS    4000Mb  52% CP CS UN PA FC     SystemNT
f:\ hd  NTFS    3859Mb  54% CP CS UN PA FC     Workspace
g:\ hd  FAT32    998Mb  44% CP    UN           SYSTEM9X
r:\ cd           N/A    N/A                    
z:\ fd  FAT     1020Mb  78% CP    UN           BLANK

e:\gnu                                               /               native
text=binary
e:\gnu\Cygwin-B20\h-i586-cygwin32\bin                /bin            native
text=binary
e:\gnu\usr\dev                                       /dev            native
text=binary
\\.\a:                                               /dev/fd0        native
text=binary
\\.\b:                                               /dev/fd1        native
text=binary
\\.\LPT1                                             /dev/lp         native
text=binary
\\.\NUL                                              /dev/nul        native
text=binary
\\.\NUL                                              /dev/null       native
text=binary
\\.\LPT1                                             /dev/parallel1  native
text=binary
\\.\COM1                                             /dev/serial1    native
text=binary
\\.\COM2                                             /dev/serial2    native
text=binary
e:\gnu\usr\etc                                       /etc            native
text=binary
f:\home                                              /home           native
text=binary
e:\gnu\Cygwin-B20\H-i586-cygwin32\i586-cygwin32\lib  /lib            native
text=binary
f:\src                                               /src            native
text=binary
c:\temp                                              /tmp            native
text=binary
f:\udl                                               /udl            native
text=binary

Found: e:\gnu\Cygwin-B20\h-i586-cygwin32\bin\bash.exe
Found: e:\gnu\Cygwin-B20\h-i586-cygwin32\bin\cat.exe
Not Found: cpp (good!)
Found: e:\gnu\Cygwin-B20\h-i586-cygwin32\bin\find.exe
Found: e:\gnu\Cygwin-B20\h-i586-cygwin32\bin\gcc.exe
Found: e:\gnu\Cygwin-B20\h-i586-cygwin32\bin\gdb.exe
Found: e:\gnu\Cygwin-B20\h-i586-cygwin32\bin\ld.exe
Found: e:\gnu\Cygwin-B20\h-i586-cygwin32\bin\ls.exe
Found: e:\gnu\usr\local\bin\make.exe
Found: e:\gnu\Cygwin-B20\h-i586-cygwin32\bin\make.exe
Found: e:\gnu\Cygwin-B20\h-i586-cygwin32\bin\sh.exe

  371k 1998/12/01 e:\gnu\Cygwin-B20\h-i586-cygwin32\bin\cygtcl80.dll
    5k 1998/12/01 e:\gnu\Cygwin-B20\h-i586-cygwin32\bin\cygtclpip80.dll
   10k 1998/12/01 e:\gnu\Cygwin-B20\h-i586-cygwin32\bin\cygtclreg80.dll
  600k 1998/12/01 e:\gnu\Cygwin-B20\h-i586-cygwin32\bin\cygtk80.dll
  446k 1998/12/04 e:\gnu\Cygwin-B20\h-i586-cygwin32\bin\cygwin1.dll
Use -h to see help about each section


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

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [ANN] EGCS-1.1.2 binaries for Cygwin b20.1 available
       [not found]     ` < 36ef3b5d.2548875@smtp.tertius.com >
@ 1999-03-16 22:20       ` Mumit Khan
       [not found]         ` < 199903170620.AAA05167@modi.xraylith.wisc.edu >
  1999-03-31 19:45         ` Mumit Khan
  0 siblings, 2 replies; 14+ messages in thread
From: Mumit Khan @ 1999-03-16 22:20 UTC (permalink / raw)
  To: tjump; +Cc: cygwin

tjump@tertius.com (Theodore Jump) writes:
> 
> Mumit,
> 
> I want to thank you for your work, but I've a quirk I can't quite figure out
> preventing me from using the new release for Cygwin code builds.
> 
> Basically, it appears that 'as' is being called with an incomplete command li
> ne
> in that it's not being fed a proper file name (it's being fed a ^M as the fil
> e
> name), thus the build of even a trivial file fails, e.g.: g++ test.cc
> 
> I tried this altering the state of my CYGWIN env-var, removing either and bot
> h
> of 'tty' and 'binmode' but this did not change the behavior at all.
> 
> Building either a C or CPP file results in build failure, I have not tested
> other types.  The same build error occurs if I'm trying to generate an .o fil
> e
> or a .exe file.
> 
> The error reported is:
> 
>     Assembler messages:
>      for reading.open
>     : No such file or directory
> 
> ... and occurs with or without the '-save-temps' option.

Yikes! I have no idea what may be causing this! I'm travelling until
Sunday and have no way to checking/fixing, but will do as soon as I
return.

When you added/removed the CYGWIN values (binmode, tty, etc), did you
restart bash? All this should work irrespective of mount types, so even 
if it does, there's still a nasty bug in there somewhere. And it should
also work correctly from CMD shell. 

And I was hoping that this was going to be the best tested release yet. 
Sigh. This is also the first released built natively, so I'll try my
usual canadian-cross build and see if that solves your problem or not.

Regards,
Mumit


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

^ permalink raw reply	[flat|nested] 14+ messages in thread

* gdb under EMACS - only works on drive C:
       [not found]         ` < 199903170620.AAA05167@modi.xraylith.wisc.edu >
@ 1999-03-16 22:31           ` Richard Stanton
  1999-03-17  9:24             ` Anders Norlander
  1999-03-31 19:45             ` Richard Stanton
  1999-03-17  5:33           ` [ANN] EGCS-1.1.2 binaries for Cygwin b20.1 available Theodore Jump
  1 sibling, 2 replies; 14+ messages in thread
From: Richard Stanton @ 1999-03-16 22:31 UTC (permalink / raw)
  To: cygwin

I've been using gcc + gdb under EMACS for a long time with no trouble, but
have just noticed a problem. I can't debug a program that's on a drive other
than drive C: (I've never tried this before). Here's what happens when I try
running d:\scratch\amput.exe:

*gud-amput.exe* window:

Current directory is d:/scratch/
GNU gdb 4.17.1
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i586-cygwin32"...
(gdb) break main
Breakpoint 1 at 0x401077: file amput.c, line 31.
(gdb) run
Starting program: //D/scratch/amput.exe
bff30000:/WINDOWS/SYSTEM/GDI32.DLL
bff60000:/WINDOWS/SYSTEM/USER32.DLL
bff70000:/WINDOWS/SYSTEM/KERNEL32.DLL
bfed0000:/WINDOWS/SYSTEM/ADVAPI32.DLL
61000000:/CYGNUS/CYGWIN-B20/H-I586-CYGWIN32/BIN/CYGWIN1.DLL

Breakpoint 1, main (argc=1, argv=0x2590f40) at amput.c:31
(gdb)

So far so good, except that in the source window, a NEW file amput.c is
created and displayed. Emacs seems to think it's called
d:/D/scratch/amput.c.

Any idea what's going wrong?

Richard Stanton


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

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [ANN] EGCS-1.1.2 binaries for Cygwin b20.1 available
       [not found]         ` < 199903170620.AAA05167@modi.xraylith.wisc.edu >
  1999-03-16 22:31           ` gdb under EMACS - only works on drive C: Richard Stanton
@ 1999-03-17  5:33           ` Theodore Jump
  1999-03-31 19:45             ` Theodore Jump
  1 sibling, 1 reply; 14+ messages in thread
From: Theodore Jump @ 1999-03-17  5:33 UTC (permalink / raw)
  To: Mumit Khan; +Cc: cygwin

>When you added/removed the CYGWIN values (binmode, tty, etc), did you
>restart bash?

you bet.

>And I was hoping that this was going to be the best tested release yet. 

Sorry, don't like being the harbinger of bad news. ;^(

I'll watch the list, or you can email me directly. I'd hoped it was something
simpler related to my setup that I was missing but I guess not.  In the mean
time I've rolled back to 1.1.1 so it's not holding me up ...

TIA,
-Ted

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

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: gdb under EMACS - only works on drive C:
  1999-03-16 22:31           ` gdb under EMACS - only works on drive C: Richard Stanton
@ 1999-03-17  9:24             ` Anders Norlander
  1999-03-31 19:45               ` Anders Norlander
  1999-03-31 19:45             ` Richard Stanton
  1 sibling, 1 reply; 14+ messages in thread
From: Anders Norlander @ 1999-03-17  9:24 UTC (permalink / raw)
  To: Richard Stanton; +Cc: cygwin

Richard Stanton wrote:
> 
> I've been using gcc + gdb under EMACS for a long time with no trouble, but
> have just noticed a problem. I can't debug a program that's on a drive other
> than drive C: (I've never tried this before). Here's what happens when I try
> running d:\scratch\amput.exe:
[snip]
> This GDB was configured as "i586-cygwin32"...
> (gdb) break main
> Breakpoint 1 at 0x401077: file amput.c, line 31.
> (gdb) run
> Starting program: //D/scratch/amput.exe
		    ^^^^ cygwin path
[snip]
> So far so good, except that in the source window, a NEW file amput.c is
> created and displayed. Emacs seems to think it's called
> d:/D/scratch/amput.c.
> 
> Any idea what's going wrong?
You are using NT emacs, right? NT emacs is not a cygwin program (it
could
possibly be compiled with cygwin tools. Anybody tried this?) and
therefore
doesn't recognize cygwin style paths with a specified drive or paths
containing "mounted" directories. As you see emacs strips the first
leading '/' and thinks the rest is a valid windows path, which it is
not!

Regards,
Anders

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

^ permalink raw reply	[flat|nested] 14+ messages in thread

* gdb under EMACS - only works on drive C:
  1999-03-16 22:31           ` gdb under EMACS - only works on drive C: Richard Stanton
  1999-03-17  9:24             ` Anders Norlander
@ 1999-03-31 19:45             ` Richard Stanton
  1 sibling, 0 replies; 14+ messages in thread
From: Richard Stanton @ 1999-03-31 19:45 UTC (permalink / raw)
  To: cygwin

I've been using gcc + gdb under EMACS for a long time with no trouble, but
have just noticed a problem. I can't debug a program that's on a drive other
than drive C: (I've never tried this before). Here's what happens when I try
running d:\scratch\amput.exe:

*gud-amput.exe* window:

Current directory is d:/scratch/
GNU gdb 4.17.1
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i586-cygwin32"...
(gdb) break main
Breakpoint 1 at 0x401077: file amput.c, line 31.
(gdb) run
Starting program: //D/scratch/amput.exe
bff30000:/WINDOWS/SYSTEM/GDI32.DLL
bff60000:/WINDOWS/SYSTEM/USER32.DLL
bff70000:/WINDOWS/SYSTEM/KERNEL32.DLL
bfed0000:/WINDOWS/SYSTEM/ADVAPI32.DLL
61000000:/CYGNUS/CYGWIN-B20/H-I586-CYGWIN32/BIN/CYGWIN1.DLL

Breakpoint 1, main (argc=1, argv=0x2590f40) at amput.c:31
(gdb)

So far so good, except that in the source window, a NEW file amput.c is
created and displayed. Emacs seems to think it's called
d:/D/scratch/amput.c.

Any idea what's going wrong?

Richard Stanton


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


^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [ANN] EGCS-1.1.2 binaries for Cygwin b20.1 available
  1999-03-17  5:33           ` [ANN] EGCS-1.1.2 binaries for Cygwin b20.1 available Theodore Jump
@ 1999-03-31 19:45             ` Theodore Jump
  0 siblings, 0 replies; 14+ messages in thread
From: Theodore Jump @ 1999-03-31 19:45 UTC (permalink / raw)
  To: Mumit Khan; +Cc: cygwin

>When you added/removed the CYGWIN values (binmode, tty, etc), did you
>restart bash?

you bet.

>And I was hoping that this was going to be the best tested release yet. 

Sorry, don't like being the harbinger of bad news. ;^(

I'll watch the list, or you can email me directly. I'd hoped it was something
simpler related to my setup that I was missing but I guess not.  In the mean
time I've rolled back to 1.1.1 so it's not holding me up ...

TIA,
-Ted

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


^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [ANN] EGCS-1.1.2 binaries for Cygwin b20.1 available
  1999-03-16 21:37   ` Theodore Jump
       [not found]     ` < 36ef3b5d.2548875@smtp.tertius.com >
@ 1999-03-31 19:45     ` Theodore Jump
  1 sibling, 0 replies; 14+ messages in thread
From: Theodore Jump @ 1999-03-31 19:45 UTC (permalink / raw)
  To: Mumit Khan; +Cc: cygwin

Mumit,

I want to thank you for your work, but I've a quirk I can't quite figure out
preventing me from using the new release for Cygwin code builds.

Basically, it appears that 'as' is being called with an incomplete command line
in that it's not being fed a proper file name (it's being fed a ^M as the file
name), thus the build of even a trivial file fails, e.g.: g++ test.cc

I tried this altering the state of my CYGWIN env-var, removing either and both
of 'tty' and 'binmode' but this did not change the behavior at all.

Building either a C or CPP file results in build failure, I have not tested
other types.  The same build error occurs if I'm trying to generate an .o file
or a .exe file.

The error reported is:

    Assembler messages:
     for reading.open
    : No such file or directory

... and occurs with or without the '-save-temps' option.

I'm including my test case source, 'gcc -v' output, and 'cygcheck -s' output in
the hopes that you can shed some light on this.

I hope I don't seem like a total putz for not figuring out what's causing this.

TIA,
-Ted

PS: The Mingw32 variant compiles and links my test case fine, it's just the
Cygwin variant (using in BASH or CMD) that's problematical for me.

-----------------------------------------------------------------------------
--- sample source -----------------------------------------------------------
-----------------------------------------------------------------------------

#include <iostream>

using namespace std;

int main(int,char**)
{
	cout << "hello" << endl;
	return 0;
}

-----------------------------------------------------------------------------
--- gcc -v output -----------------------------------------------------------
-----------------------------------------------------------------------------

Reading specs from
e:/gnu/Cygwin-B20/h-i586-cygwin32/bin/../lib/gcc-lib/i586-cygwin32/egcs-2.91.66/specs
gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release)

e:/gnu/Cygwin-B20/h-i586-cygwin32/bin/../lib/gcc-lib/i586-cygwin32/egcs-2.91.66/cpp.exe
-lang-c++ -v -iprefix
e:/gnu/Cygwin-B20/h-i586-cygwin32/bin/../lib/gcc-lib/i586-cygwin32/egcs-2.91.66/
-undef -D__GNUC__=2 -D__GNUG__=2 -D__cplusplus -D__GNUC_MINOR__=91 -Di386
-D_WIN32 -DWINNT -D_X86_=1 -D__STDC__=1
-D__stdcall=__attribute__((__stdcall__)) -D__cdecl=__attribute__((__cdecl__))
-D__declspec(x)=__attribute__((x)) -D__i386__ -D_WIN32 -D__WINNT__ -D_X86_=1
-D__STDC__=1 -D__stdcall=__attribute__((__stdcall__))
-D__cdecl=__attribute__((__cdecl__)) -D__declspec(x)=__attribute__((x))
-D__i386 -D__WINNT -Asystem(winnt) -Acpu(i386) -Amachine(i386) -D__EXCEPTIONS
-remap -D__CYGWIN32__ -D__CYGWIN__ test.cc /tmp/ccrG3iFV.ii
GNU CPP version egcs-2.91.66 19990314 (egcs-1.1.2 release) (80386, BSD syntax)
#include "..." search starts here:
#include <...> search starts here:

e:/gnu/Cygwin-B20/h-i586-cygwin32/bin/../lib/gcc-lib/i586-cygwin32/egcs-2.91.66/../../../../../include/g++

e:/gnu/Cygwin-B20/h-i586-cygwin32/bin/../lib/gcc-lib/i586-cygwin32/egcs-2.91.66/../../../../../include

e:/gnu/Cygwin-B20/h-i586-cygwin32/bin/../lib/gcc-lib/i586-cygwin32/egcs-2.91.66/../../../../i586-cygwin32/include

e:/gnu/Cygwin-B20/h-i586-cygwin32/bin/../lib/gcc-lib/i586-cygwin32/egcs-2.91.66/include
End of search list.

e:/gnu/Cygwin-B20/h-i586-cygwin32/bin/../lib/gcc-lib/i586-cygwin32/egcs-2.91.66/cc1plus.exe
/tmp/ccrG3iFV.ii -quiet -dumpbase test.cc -version -o /tmp/ccEkg9AL.s
GNU C++ version egcs-2.91.66 19990314 (egcs-1.1.2 release) (i586-cygwin32)
compiled by GNU C version egcs-2.91.66 19990314 (egcs-1.1.2 release).

e:/gnu/Cygwin-B20/h-i586-cygwin32/bin/../lib/gcc-lib/i586-cygwin32/egcs-2.91.66/../../../../i586-cygwin32/bin/as.exe
^M
Assembler messages:
Error: Can't open ^M for reading.
^M: No such file or directory

-----------------------------------------------------------------------------
--- cygcheck -s output ------------------------------------------------------
-----------------------------------------------------------------------------

Cygnus Win95/NT Configuration Diagnostics
Current System Time: Tue Mar 16 23:24:01 1999

WinNT Ver 4.0 build 1381 Service Pack 4

Path:	.
	/usr/local/bin
	/bin
	/usr/X11R6.4/bin

SysDir: E:\WINNT\System32
WinDir: E:\WINNT

CYGWIN = `tty binmode glob title strip_title'
HOME = `/home'
LIBRARY_PATH = `/usr/local/lib:/usr/X11/lib:/Cygwin-B20/H-i586-cygwin32/lib'
MAKE_MODE = `unix'
PWD = `/src'
TCL_LIBRARY = `/Cygwin-B20/share/tcl8.0'

Use `-r' to scan registry

a:\ fd  FAT        1Mb 100% CP    UN           MARVINROID
b:\ fd           N/A    N/A                    
c:\ hd  FAT      352Mb   2% CP    UN           BOOTSTRAP
d:\ hd  FAT      274Mb  94% CP    UN           PAGEFILE
e:\ hd  NTFS    4000Mb  52% CP CS UN PA FC     SystemNT
f:\ hd  NTFS    3859Mb  54% CP CS UN PA FC     Workspace
g:\ hd  FAT32    998Mb  44% CP    UN           SYSTEM9X
r:\ cd           N/A    N/A                    
z:\ fd  FAT     1020Mb  78% CP    UN           BLANK

e:\gnu                                               /               native
text=binary
e:\gnu\Cygwin-B20\h-i586-cygwin32\bin                /bin            native
text=binary
e:\gnu\usr\dev                                       /dev            native
text=binary
\\.\a:                                               /dev/fd0        native
text=binary
\\.\b:                                               /dev/fd1        native
text=binary
\\.\LPT1                                             /dev/lp         native
text=binary
\\.\NUL                                              /dev/nul        native
text=binary
\\.\NUL                                              /dev/null       native
text=binary
\\.\LPT1                                             /dev/parallel1  native
text=binary
\\.\COM1                                             /dev/serial1    native
text=binary
\\.\COM2                                             /dev/serial2    native
text=binary
e:\gnu\usr\etc                                       /etc            native
text=binary
f:\home                                              /home           native
text=binary
e:\gnu\Cygwin-B20\H-i586-cygwin32\i586-cygwin32\lib  /lib            native
text=binary
f:\src                                               /src            native
text=binary
c:\temp                                              /tmp            native
text=binary
f:\udl                                               /udl            native
text=binary

Found: e:\gnu\Cygwin-B20\h-i586-cygwin32\bin\bash.exe
Found: e:\gnu\Cygwin-B20\h-i586-cygwin32\bin\cat.exe
Not Found: cpp (good!)
Found: e:\gnu\Cygwin-B20\h-i586-cygwin32\bin\find.exe
Found: e:\gnu\Cygwin-B20\h-i586-cygwin32\bin\gcc.exe
Found: e:\gnu\Cygwin-B20\h-i586-cygwin32\bin\gdb.exe
Found: e:\gnu\Cygwin-B20\h-i586-cygwin32\bin\ld.exe
Found: e:\gnu\Cygwin-B20\h-i586-cygwin32\bin\ls.exe
Found: e:\gnu\usr\local\bin\make.exe
Found: e:\gnu\Cygwin-B20\h-i586-cygwin32\bin\make.exe
Found: e:\gnu\Cygwin-B20\h-i586-cygwin32\bin\sh.exe

  371k 1998/12/01 e:\gnu\Cygwin-B20\h-i586-cygwin32\bin\cygtcl80.dll
    5k 1998/12/01 e:\gnu\Cygwin-B20\h-i586-cygwin32\bin\cygtclpip80.dll
   10k 1998/12/01 e:\gnu\Cygwin-B20\h-i586-cygwin32\bin\cygtclreg80.dll
  600k 1998/12/01 e:\gnu\Cygwin-B20\h-i586-cygwin32\bin\cygtk80.dll
  446k 1998/12/04 e:\gnu\Cygwin-B20\h-i586-cygwin32\bin\cygwin1.dll
Use -h to see help about each section


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


^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: gdb under EMACS - only works on drive C:
  1999-03-17  9:24             ` Anders Norlander
@ 1999-03-31 19:45               ` Anders Norlander
  0 siblings, 0 replies; 14+ messages in thread
From: Anders Norlander @ 1999-03-31 19:45 UTC (permalink / raw)
  To: Richard Stanton; +Cc: cygwin

Richard Stanton wrote:
> 
> I've been using gcc + gdb under EMACS for a long time with no trouble, but
> have just noticed a problem. I can't debug a program that's on a drive other
> than drive C: (I've never tried this before). Here's what happens when I try
> running d:\scratch\amput.exe:
[snip]
> This GDB was configured as "i586-cygwin32"...
> (gdb) break main
> Breakpoint 1 at 0x401077: file amput.c, line 31.
> (gdb) run
> Starting program: //D/scratch/amput.exe
		    ^^^^ cygwin path
[snip]
> So far so good, except that in the source window, a NEW file amput.c is
> created and displayed. Emacs seems to think it's called
> d:/D/scratch/amput.c.
> 
> Any idea what's going wrong?
You are using NT emacs, right? NT emacs is not a cygwin program (it
could
possibly be compiled with cygwin tools. Anybody tried this?) and
therefore
doesn't recognize cygwin style paths with a specified drive or paths
containing "mounted" directories. As you see emacs strips the first
leading '/' and thinks the rest is a valid windows path, which it is
not!

Regards,
Anders

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


^ permalink raw reply	[flat|nested] 14+ messages in thread

* [ANN] EGCS-1.1.2 binaries for Cygwin b20.1 available
  1999-03-16 12:10 [ANN] EGCS-1.1.2 binaries for Cygwin b20.1 available Mumit Khan
       [not found] ` < 199903162010.OAA04606@modi.xraylith.wisc.edu >
@ 1999-03-31 19:45 ` Mumit Khan
  1 sibling, 0 replies; 14+ messages in thread
From: Mumit Khan @ 1999-03-31 19:45 UTC (permalink / raw)
  To: cygwin

EGCS 1.1.2 for Cygwin b20.1+ (i586-cygwin32) -- Release information
===================================================================

Release date: Mar 16, 1998.

I'd like to announce egcs-1.1.2 for Cygwin B20.x (i586-cygwin32).  These 
are meant to replace the b20.1 compiler, so the pathnames are compatible 
with b20.1. This has only been tested with Cygwin B20.1, and will NOT
work previous releases such as Cygwin B20.

What's in this package?
  
  egcs-1.1.2: The compilers for C, C++, ObjC and F77 plus runtime
    libraries. Also provides a working info viewer (info.exe).

  egcs-1.1.2-docs: Provides the documentation in GNU info format.

What's not in this package?
  
  libg++: Sorry, but it's about time I acted on my long-standing threat 
    to remove this deprecated library.

Where?
  
  Web: http://www.xraylith.wisc.edu/~khan/software/gnu-win32/
  FTP: ftp://ftp.xraylith.wisc.edu/pub/khan/gnu-win32/cygwin/egcs-1.1.2/

  Please visit the web page before you attempt to download/install. It
  may address problems you might run into.

Installation? 

  Just unpack into the existing Cygnus installation tree and you're set 
  to go. See the INSTALL file for more info.

Disk space?
   
  About 12M, give or take a few.

Where to report bugs?

  Report configuration and Win32 specific bugs to me, GCC specific bugs 
  egcs-bugs, and always copy Cygwin mailing list so others can see it
  as well. If you send me email, please do have patience, since I usually 
  do not have the time to respond to each email right away.

Regards,
Mumit -- khan@xraylith.wisc.edu
http://www.xraylith.wisc.edu/~khan/


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


^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [ANN] EGCS-1.1.2 binaries for Cygwin b20.1 available
  1999-03-16 22:20       ` Mumit Khan
       [not found]         ` < 199903170620.AAA05167@modi.xraylith.wisc.edu >
@ 1999-03-31 19:45         ` Mumit Khan
  1 sibling, 0 replies; 14+ messages in thread
From: Mumit Khan @ 1999-03-31 19:45 UTC (permalink / raw)
  To: tjump; +Cc: cygwin

tjump@tertius.com (Theodore Jump) writes:
> 
> Mumit,
> 
> I want to thank you for your work, but I've a quirk I can't quite figure out
> preventing me from using the new release for Cygwin code builds.
> 
> Basically, it appears that 'as' is being called with an incomplete command li
> ne
> in that it's not being fed a proper file name (it's being fed a ^M as the fil
> e
> name), thus the build of even a trivial file fails, e.g.: g++ test.cc
> 
> I tried this altering the state of my CYGWIN env-var, removing either and bot
> h
> of 'tty' and 'binmode' but this did not change the behavior at all.
> 
> Building either a C or CPP file results in build failure, I have not tested
> other types.  The same build error occurs if I'm trying to generate an .o fil
> e
> or a .exe file.
> 
> The error reported is:
> 
>     Assembler messages:
>      for reading.open
>     : No such file or directory
> 
> ... and occurs with or without the '-save-temps' option.

Yikes! I have no idea what may be causing this! I'm travelling until
Sunday and have no way to checking/fixing, but will do as soon as I
return.

When you added/removed the CYGWIN values (binmode, tty, etc), did you
restart bash? All this should work irrespective of mount types, so even 
if it does, there's still a nasty bug in there somewhere. And it should
also work correctly from CMD shell. 

And I was hoping that this was going to be the best tested release yet. 
Sigh. This is also the first released built natively, so I'll try my
usual canadian-cross build and see if that solves your problem or not.

Regards,
Mumit


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


^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: gdb under EMACS - only works on drive C:
  1999-03-17  9:57 gdb under EMACS - only works on drive C: Earnie Boyd
@ 1999-03-31 19:45 ` Earnie Boyd
  0 siblings, 0 replies; 14+ messages in thread
From: Earnie Boyd @ 1999-03-31 19:45 UTC (permalink / raw)
  To: Anders Norlander, Richard Stanton; +Cc: cygwin

---Anders Norlander <anorland@hem2.passagen.se> wrote:
>
> Richard Stanton wrote:
> > 
> > I've been using gcc + gdb under EMACS for a long time with no
trouble, but
> > have just noticed a problem. I can't debug a program that's on a
drive other
> > than drive C: (I've never tried this before). Here's what happens
when I try
> > running d:\scratch\amput.exe:
> [snip]
> > This GDB was configured as "i586-cygwin32"...
> > (gdb) break main
> > Breakpoint 1 at 0x401077: file amput.c, line 31.
> > (gdb) run
> > Starting program: //D/scratch/amput.exe
> 		    ^^^^ cygwin path
> [snip]
> > So far so good, except that in the source window, a NEW file
amput.c is
> > created and displayed. Emacs seems to think it's called
> > d:/D/scratch/amput.c.
> > 
> > Any idea what's going wrong?
> You are using NT emacs, right? NT emacs is not a cygwin program (it
> could
> possibly be compiled with cygwin tools. Anybody tried this?) and
> therefore
> doesn't recognize cygwin style paths with a specified drive or paths
> containing "mounted" directories. As you see emacs strips the first
> leading '/' and thinks the rest is a valid windows path, which it is
> not!

Check the archives, I think someone posted a howto on this.  BTW, I'd
use the http://www.eGroups.com mirror to search for this if I were the
one doing the searching.

==
-                        \\||//
-------------------o0O0--Earnie--0O0o-------------------
--                earnie_boyd@yahoo.com               --
-- http://www.freeyellow.com/members5/gw32/index.html --
----------------------ooo0O--O0ooo----------------------

PS: Newbie's, you should visit my page.
_________________________________________________________
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com


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


^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: gdb under EMACS - only works on drive C:
@ 1999-03-17  9:57 Earnie Boyd
  1999-03-31 19:45 ` Earnie Boyd
  0 siblings, 1 reply; 14+ messages in thread
From: Earnie Boyd @ 1999-03-17  9:57 UTC (permalink / raw)
  To: Anders Norlander, Richard Stanton; +Cc: cygwin

---Anders Norlander <anorland@hem2.passagen.se> wrote:
>
> Richard Stanton wrote:
> > 
> > I've been using gcc + gdb under EMACS for a long time with no
trouble, but
> > have just noticed a problem. I can't debug a program that's on a
drive other
> > than drive C: (I've never tried this before). Here's what happens
when I try
> > running d:\scratch\amput.exe:
> [snip]
> > This GDB was configured as "i586-cygwin32"...
> > (gdb) break main
> > Breakpoint 1 at 0x401077: file amput.c, line 31.
> > (gdb) run
> > Starting program: //D/scratch/amput.exe
> 		    ^^^^ cygwin path
> [snip]
> > So far so good, except that in the source window, a NEW file
amput.c is
> > created and displayed. Emacs seems to think it's called
> > d:/D/scratch/amput.c.
> > 
> > Any idea what's going wrong?
> You are using NT emacs, right? NT emacs is not a cygwin program (it
> could
> possibly be compiled with cygwin tools. Anybody tried this?) and
> therefore
> doesn't recognize cygwin style paths with a specified drive or paths
> containing "mounted" directories. As you see emacs strips the first
> leading '/' and thinks the rest is a valid windows path, which it is
> not!

Check the archives, I think someone posted a howto on this.  BTW, I'd
use the http://www.eGroups.com mirror to search for this if I were the
one doing the searching.

==
-                        \\||//
-------------------o0O0--Earnie--0O0o-------------------
--                earnie_boyd@yahoo.com               --
-- http://www.freeyellow.com/members5/gw32/index.html --
----------------------ooo0O--O0ooo----------------------

PS: Newbie's, you should visit my page.
_________________________________________________________
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com


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

^ permalink raw reply	[flat|nested] 14+ messages in thread

end of thread, other threads:[~1999-03-31 19:45 UTC | newest]

Thread overview: 14+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1999-03-16 12:10 [ANN] EGCS-1.1.2 binaries for Cygwin b20.1 available Mumit Khan
     [not found] ` < 199903162010.OAA04606@modi.xraylith.wisc.edu >
1999-03-16 21:37   ` Theodore Jump
     [not found]     ` < 36ef3b5d.2548875@smtp.tertius.com >
1999-03-16 22:20       ` Mumit Khan
     [not found]         ` < 199903170620.AAA05167@modi.xraylith.wisc.edu >
1999-03-16 22:31           ` gdb under EMACS - only works on drive C: Richard Stanton
1999-03-17  9:24             ` Anders Norlander
1999-03-31 19:45               ` Anders Norlander
1999-03-31 19:45             ` Richard Stanton
1999-03-17  5:33           ` [ANN] EGCS-1.1.2 binaries for Cygwin b20.1 available Theodore Jump
1999-03-31 19:45             ` Theodore Jump
1999-03-31 19:45         ` Mumit Khan
1999-03-31 19:45     ` Theodore Jump
1999-03-31 19:45 ` Mumit Khan
1999-03-17  9:57 gdb under EMACS - only works on drive C: Earnie Boyd
1999-03-31 19:45 ` Earnie Boyd

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).