Re: mingw-targeted cross-compiler question

On Wed, 22 Dec 2010 15:36:01 +0100, Kai Tietz wrote: 2010/12/22 : On Wed, 22 Dec 2010 15:11:18 +0100, Kai Tietz wrote: 2010/12/22 : On Wed, 22 Dec 2010 14:13:15 +0100, Frédéric Bron wrote: I checked the Make file, it used this flag: gcc -mno-cygwin -g -Wl,--add-stdcall-alias -

Re: mingw-targeted cross-compiler question

On Wed, 22 Dec 2010 15:11:18 +0100, Kai Tietz wrote: 2010/12/22 : On Wed, 22 Dec 2010 14:13:15 +0100, Frédéric Bron wrote: I checked the Make file, it used this flag: gcc -mno-cygwin -g -Wl,--add-stdcall-alias -Wl,--export-all-symbols ... replace gcc by gcc-3 gcc 4 is now the defau

Re: mingw-targeted cross-compiler question

On Wed, 22 Dec 2010 14:13:15 +0100, Frédéric Bron wrote: I checked the Make file, it used this flag: gcc -mno-cygwin -g -Wl,--add-stdcall-alias -Wl,--export-all-symbols ... replace gcc by gcc-3 gcc 4 is now the default on cygwin but the cross compiler is not supported for that version. Fr

Re: configure rxvt on cygwin 1.7.5

On Fri, 09 Jul 2010 00:41:25 +0200, Jeremy Bopp wrote: On 7/8/2010 4:22 PM, philippe wrote: Jeremy Bopp a écrit : [...] However, if rxvt used to work for you under Cygwin 1.5, you might be able to make it happy again by changing your LANG setting to LANG=C. No, i don't know where to modif

Re: UTF8 and cvs issues in 1.7.2

On Fri, 26 Mar 2010 15:51:38 -0600 Erik Blake wrote: On 03/26/2010 03:44 PM, lemke...@t-online.de wrote: >> What you can do is either to >> use ISO-8859-1 sort of like above, or you convert the file content >> to UTF-8 so you can use UTF-8 from now on. >> The only problem is this file is none of

Re: UTF8 and cvs issues in 1.7.2

On Fri, 26 Mar 2010 10:30:28 +0100 Corinna Vinschen wrote: On Mar 26 00:24, lemkemch wrote: > Erik Blake wrote: > >On 03/25/2010 05:05 PM, lemkemch wrote: > >> orion> cvs -qn up -l > >> U Ãppel.txt > >> cvs update: warning: `âppel.txt' is not (any

Re: UTF8 and cvs issues in 1.7.2

Erik Blake wrote: On 03/25/2010 05:05 PM, lemkemch wrote: > orion> cvs -qn up -l > U Ãppel.txt > cvs update: warning: `âppel.txt' is not (any longer) pertinent >> And frankly, I can't see how the terminal could influence the > behavior of the cvs executab

Re: UTF8 and cvs issues in 1.7.2

Larry Hall wrote: With Google. Pretty easy to find, eh? You practically bumped into each other. Thanks for the quick answer, but sorry, no, mintty doesn't help: orion> cvs -qn up -l U äppel.txt cvs update: warning: `▒ppel.txt' is not (an

UTF8 and cvs issues in 1.7.2

Some time ago in cygwin 1.5 I did this: orion> cvs ci äppel.txt /home/michael/Repos/äppel.txt,v <-- äppel.txt initial revision: 1.1 orion> orion> cvs -qn up orion> Exactly the expected behavior. Now in my new 1.7.2 installation the cvs up gives this (in an rxvt window): orion> cvs -qn

Re: [1.7] Accented characters don't work

On Sat, 28 Nov 2009 20:23:49 +0100, I wrote: On Sat, 28 Nov 2009 17:16:44 +0100, Marco Atzeri wrote: --- Sab 28/11/09, lemkemch ha scritto: > and the Cygwin console. Urxvt and xterm require an X server. And that I really don't like. Way too complex for my taste for the simple

Re: [1.7] Accented characters don't work

On Sat, 28 Nov 2009 17:16:44 +0100, Marco Atzeri wrote: --- Sab 28/11/09, lemkemch ha scritto: > and the Cygwin console. Urxvt and xterm require an X server. And that I really don't like. Way too complex for my taste for the simple task of popping up a text window. > mintty i

Re: [1.7] Accented characters don't work

On Sat, 28 Nov 2009 07:57:52 +0100, Andy Koppe wrote: 2009/11/27 : What am I doing wrong with my first tries of 1.7? I created in Windows Explorer a directory Ébène and in it a file très. When I look at it with ls in an rxvt window I don't see the accented characters but the two utf-8 bytes.

[1.7] Accented characters don't work

What am I doing wrong with my first tries of 1.7? I created in Windows Explorer a directory Ébène and in it a file très. When I look at it with ls in an rxvt window I don't see the accented characters but the two utf-8 bytes. Hm. I then created the same directory from tcsh (my standard shell)

Re: [1.7] su

On Thu, 19 Nov 2009 cgf wrote: On Thu, Nov 19, 2009 at 10:15:17PM +0100, lemke...@t-online.de wrote: Is su supposed to work? No. Ok. Michael -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/do

[1.7] su

Is su supposed to work? When I try from an unprivileged account I get: michael> su addmini Password: su: /bin/bash: Permission denied michael> procps -ef UIDPID PPID C STIME TTY TIME CMD michael 7580 1 0 Nov28 tty0 00:00:11 /usr/bin/rxvt -sb -sl 1024 -geom mich

Re: autoconf/configure problem on text mounts

lemkemch wrote on 10 August 2008 18:46: I am not familar enough with autoconf to be able to tell how that line gets into configure. I can't find it in configure.in. All I can see is stuff like AH_VERBATIM([HAVE_UINT64_T] and AC_CHECK_TYPES([uint8_t, int8_t, uint16_t, int16_t, uin

autoconf/configure problem on text mounts

There seems to be a problem with autoconf generated scripts when running the resulting configure on a text mount. I came across this when trying to compile lame: checking for int64_t... yes configure: error: CHECK_TYPE_uint32_t - please report to lame-dev lists.sourceforge.net I tracke