This is the mail archive of the cygwin-announce mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[1.7] Updated: cygwin-1.7.0-45

Hi folks,

I just uploaded a new Cygwin 1.7 test release, 1.7.0-45.

                        IMPORTANT NOTE

This test release comes with a major change in terms of support for
native character sets.  I added a new chapter to the documentation to
explain the new capabilities and how to use them.  Along the same lines
the CYGWIN=codepage environment variable option has gone away.

Please, see the "What's new" section below for more details!

Cygwin 1.7 is a major jump from Cygwin 1.5.x.  The list with all
changes related to Cygwin 1.5.25 is attached below.

If nothing goes overly wrong, the official 1.7.1 release goes public
within the next two and a half months.

Just download and use that setup tool
to install Cygwin 1.7.  As usual, please report bugs and problems to
the mailing list cygwin AT cygwin DOT com.

We also have a new User's Guide for 1.7, which is currently located at

We also now have new API documentation

And we have a new FAQ, though very likely not quite complete since
we still don't know what exactly *is* a FAQ related to Cygwin 1.7.

The list of user visible changes in Cygwin 1.7 compared to the old
Cygwin 1.5.25 release is NOT appended to this mail anymore, rather
it's now part of the Cygwin User's Guide:

Bug fixes and extensions to the documentation in the form of patches
to the source SGML files are much appreciated.  The SGML sources are
located in the CVS repository under the winsup/doc directory, for
example here:

Same goes for Cygwin patches in general, of course.

This is still a TEST release.  Don't use in critical production

Nevertheless I'd like to encourage everyone to give 1.7 a shot.  Due to
internal changes it is possible to install a 1.7 release in parallel to
a 1.5 release and even run 1.7 processes in parallel to 1.5 processes.

* The processes will not know about each other!  Any try to interact
* between 1.7-based and 1.5-based processes will lead to, at least, funny
* results.

To install a 1.7 release in parallel to a 1.5 release, all you have
to do is to choose another root directory (for instance: C:\cygwin-1.7)
in setup-1.7's "Choose Installation Directory" dialog.

* NOTE: Due to the way setup-1.7 works, you have to change the directory
* right the first time you visit this dialog!  If you pressed the "Next"
* button and then "Back" again, it's already too late and setup-1.7 will
* create a broken 1.7 install.  If you pressed "Next" by mistake, exit
* setup-1.7 and start it again.

What's new in contrast to 1.7.0-44

- A lot of character sets are supported now via a call to setlocale().
  The setting of the environment variables $LANG, $LC_ALL or $LC_CTYPE will
  be used.  For instance, setting $LANG to "de_DE.ISO-8859-15" before
  starting a Cygwin session will use the ISO-8859-15 character set in
  the entire session.  UTF-8 is supported as well, as in "en_US.UTF-8".

  Along these lines, the "CYGWIN=codepage:{ansi,oem}" setting has been
  removed in favor of using $LANG, $LC_ALL, or $LC_CTYPE.

  The full list of supported character sets: "ASCII", "ISO-8859-x" with x
  in 1-16, except 12, "UTF-8", Windows codepages "CPxxx", with xxx in
  (437, 720, 737, 775, 850, 852, 855, 857, 858, 862, 866, 874, 1125,
  1250, 1251, 1252, 1253, 1254, 1255, 1256, 1257, 1258), "JIS", "SJIS",
  "GBK", "eucJP", "eucKR", and "Big5".  The leading language and territory
  part (en_US, for instance) is not used by Cygwin yet, but is required
  for POSIX compatibility.

  This is documented in length now in the Cygwin documentation.  Please

- If a filename cannot be represented in the current character set,
  the character will be converted to a sequence Ctrl-N + UTF-8 representation
  of the character.  This allows to access all files, even those not
  having a valid representation of their filename in the current character
  set (codepage).

  This is also documented in the Cygwin documentation.  Please read

- Symlinks are now using UTF-16 encoding for the target filename for
  better internationalization support.  Cygwin 1.7 can read all old style
  symlinks, but the new style is not compatible with older Cygwin releases.

  No surprise, this is also documented in the Cygwin documentation now.
  Please read
  and the shiny new FAQ entry:

- New functions log2, log2f, wordexp, wordfree.


- Fix a bug in creating secondary libs pointing to the Cygwin DLL
  (libc.a, libm.a, libdl.a, libpthread.a, libresolv.a, libutil.a)

- Revert a patch in dlopen which disallowed to load shared libs using
  the Windows default DLL search path.

- Several fixes in header files.

- Fix a memory leak in pathconf(3).

- Fix a potential crash in getaddrinfo(3).

- Print IPv6 address using lowercase hex characters in inet_ntop(3).

- Fix various bugs in passwd(1) tool which disallowed to change
  user information or password if the calling user wasn't the same
  as the user to be changed.

- mbtowc now sets errno to EILSEQ if an invalid multibyte char has been
  found, according to POSIX.


- Q: How do I know that I'm running Cygwin 1.7.0-45?

  A: The `uname -v' command prints "2009-03-31 12:05"

Have fun,


If you want to unsubscribe from the cygwin-announce mailing list, look
at the "List-Unsubscribe: " tag in the email header of this message.
Send email to the address specified there.  It will be in the format:

If you need more information on unsubscribing, start reading here:

Please read *all* of the information on unsubscribing that is available
starting at this URL.

Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                      
Red Hat, Inc.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]