managing autoconf versions?

This is a little off topic. How do people manage autoconf/automake versions? In particular, I'm not doing "my own work" -- I could probably just install one recent version of everything and be ok. Rather I'm wondering about submitting patches to other projects, some projects might use

Re: [1.7] Proposal: the filename encoding in C locale uses UTF-8 instead of SO/UTF-8

(This mail is encoded in utf-8) After tested with 1.7.0-48, many problems are eliminated. But cygpath doesn't return good pathnames, see: 1, Get absolute path of current directory: C:\Profiles\Shecti\桌面> set LANG=zh_CN.GBK& cygpath -am . C:/Profiles/Shecti/桌面 (good) C:\Profiles\Sh

Re: libtool, how should the version be parsed?

Charles Wilson wrote: [snip] > So, next time, kindly refrain from accusing my package of insanity. But > while we're on the subject...libtool-1.4 dates from 27-Nov-2003, more > than 5.5 years ago... Thanks for all the info. I learned something new. As for the old version, that's just a require

Re: libtool, how should the version be parsed?

René Berber wrote: > Hi, > > I was trying to build some package and it complained that libtool 1.4 > was needed... looking at the version: > > $ libtool --version > libtool (GNU libtool 1.3081 2009-02-17) 2.2.7a > > Is it 1.3081 or 2.2.7a? It is 2.2.7a. You can see that from the announcement h

libtool, how should the version be parsed?

Hi, I was trying to build some package and it complained that libtool 1.4 was needed... looking at the version: $ libtool --version libtool (GNU libtool 1.3081 2009-02-17) 2.2.7a Is it 1.3081 or 2.2.7a? I see at gnu.org that the latest stable is 2.2.6a, so I suppose the one in Cygwin (1.7) is t

Re: Calling Cygwin to start a shellscript

On Fri, May 15, 2009 at 5:35 PM, Thomas Wiedmann wrote: > Hello, > > How can a shellscript be called from the Windows cmd console using Cygwin, > i. e. by which command, options and arguments has Cygwin to be called to run > a shellscript, e. g. myscript.sh? > > Thomas Wiedmann What I have done

Calling Cygwin to start a shellscript

Hello, How can a shellscript be called from the Windows cmd console using Cygwin, i. e. by which command, options and arguments has Cygwin to be called to run a shellscript, e. g. myscript.sh? Thomas Wiedmann -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem report

[ANNOUNCEMENT] [1.7] Updated: cygwin-1.7.0-48

Hi folks, I just uploaded a new Cygwin 1.7 test release, 1.7.0-48. The list with the changes related to the previous test release 1.7.0-47 is attached below. === IMPORTANT NOTE This -48 test release com

Re: [1.7] Updated: {emacs,emacs-X11,emacs-el}-23.0.92-1

On 5/15/2009 9:09 AM, gustav wrote: Dear Ken, First, thank you so much for having taken care of Emacs! I enclose a patch to rmail.el, which I always have to apply, because version 21.2 normally attempts to create files with "po:", but neither Windows nor Cygwin tolerate that. Current rmail.el c

[ANNOUNCEMENT] [1.7] Updated: {emacs,emacs-X11,emacs-el}-23.0.92-1

New experimental versions of the emacs, emacs-X11, and emacs-el packages are now available for download for those testing cygwin 1.7, replacing the previous experimental 22.1-3 packages. I have left 21.2-13 as current. CYGWIN NEWS: This is the first release in almost two years, af

Re: [1.7] Proposal: the filename encoding in C locale uses UTF-8 instead of SO/UTF-8

On May 15 20:34, IWAMURO Motonori wrote: > 2009/5/15 Corinna Vinschen : > > I have just trouble with SJIS, but that's not something I can easily > > test. Maybe you can look into that in the next couple of days? > > Maybe I can. Please explain details of the trouble. Probably I only fall over my

Re: [Fwd: [1.7] wcwidth failing configure tests]

On May 14 17:51, Jeff Johnston wrote: > Corinna, I have no problem with checking the new patch in and extending > this later, assuming you have thoroughly tested this implementation. I tested it with _MB_CAPABLE defined and with _MB_CAPABLE undefined. Both variations worked as expected, the latt

Re: [1.7] Proposal: the filename encoding in C locale uses UTF-8 instead of SO/UTF-8

2009/5/15 Corinna Vinschen : > I have just trouble with SJIS, but that's not something I can easily > test. Maybe you can look into that in the next couple of days? Maybe I can. Please explain details of the trouble. -- IWAMURO Motnori -- Unsubscribe info: http://cygwin.com

Re: [1.7] bug in printf and %ls

On May 15 13:49, Alexey Borzenkov wrote: > On Fri, May 15, 2009 at 1:30 PM, Alexey Borzenkov wrote: > > And I found why. It appears that there's a bug in printf with %ls that > > will refuse to print the string completely if the wide string for %ls > > cannot be represented in current charset. >

Re: Cygwin 1.7 setup question

On May 14 13:54, Karl M wrote: > > From: corinna > > It's not running scripts as administrators.none, it's running them as > > user.users-primary-group. That's "None" for all local accounts. > > > Is this setup behavior expected to stay the same, or eventually run > them as administrator.administra

Re: [1.7] bug in printf and %ls

On May 15 13:30, Alexey Borzenkov wrote: > [...] > It appears that there's a bug in printf with %ls that > will refuse to print the string completely if the wide string for %ls > cannot be represented in current charset. It's interesting that > sometimes it behaves differently. For example: > > $

Re: [1.7] bug in printf and %ls

On Fri, May 15, 2009 at 1:30 PM, Alexey Borzenkov wrote: > And I found why. It appears that there's a bug in printf with %ls that > will refuse to print the string completely if the wide string for %ls > cannot be represented in current charset. [...] > Prints nothing, i.e. it doesn't print neit

Re: [1.7] mkpasswd and mkgroup ignore user and group names with national characters

On May 15 11:43, Alexey Borzenkov wrote: > I'm in a domain at work and previously used mkpasswd -d and mkgroup -d > to populate /etc/passwd and /etc/group files. Unfortunately, we mostly > use Russian versions of Windows (especially on servers) here and most > built-in user and group names (like Ad

Re: [1.7] bug in printf and %ls

On Fri, May 15, 2009 at 11:43 AM, Alexey Borzenkov wrote: > I'm in a domain at work and previously used mkpasswd -d and mkgroup -d > to populate /etc/passwd and /etc/group files. Unfortunately, we mostly > use Russian versions of Windows (especially on servers) here and most > built-in user and gr

[1.7] mkpasswd and mkgroup ignore user and group names with national characters

I'm in a domain at work and previously used mkpasswd -d and mkgroup -d to populate /etc/passwd and /etc/group files. Unfortunately, we mostly use Russian versions of Windows (especially on servers) here and most built-in user and group names (like Administrator, Domain Users, etc.) are localized. W