If I run up the cygwin bash (presukably under some flavour of
cmd.exe), and then run rxvt, I get a new window with TERM=xterm
as expected, but all attempts to print escape codes print '\e'!
Cursor movement's shot to hell too; pressing 'up' actually
moves the cursor in the window as oppo
Around about 01/07/02 16:56, Jean le Roux scribbled ...
> ... I also got a tarball
> of libstdc++-v3 from ftp://ftp.xraylith.wisc.edu/pub/khan/gnu-win32/cygwin/snapshots/
> and copied that to /usr/include/g++-3/
That's not going to work, if that's all you did!
The V3 STL headers are *just
Nobody seems to have had any comment WRT my continued, random
'signal 11' errors trying to configure and/or make (even in a
make clean!).
If I run purely off a C:\-installed cygwin, I suffer no
problems at all - I seem to have compiled up gcc fine.
So - why would running cygwin off
I have need to prove that I can compile up a gcc 2.95.3 with
the latest libstdc++ (to get the proper C++ STL).
I've set up cygwin as best as seems necessary, and fetched
the latest gcc & libstdc++ source (gcc from the cygwin src dist.).
However, whenever I do a 'configure' in a clea
4 matches
Mail list logo