[ANNOUNCEMENT] ghostscript 9.22-1
The following packages have been uploaded to the Cygwin distribution: * ghostscript-9.22-1 * libgs9-9.22-1 * libgs-devel-9.22-1 GNU Ghostscript is a PostScript interpreter capable of converting PS files into a number of printer output formats. Ghostscript can also render PS files into a number of graphics file formats. This is an update to the latest upstream release, which now works with preview-latex. Ken Brown Cygwin's Ghostscript maintainer -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: mksetupini fails validating packages because curr is test
Ok, thanks! But what would be the schedule of releasing it to cygwin repo? I don't want to mess up my CI scripts which install the whole build env from scratch on every build, so I need it in cygwin repo. Br, Ivan 2017-12-01 13:00 GMT+02:00 Jon Turney : > On 30/11/2017 22:16, Ivan Gagis wrote: >> >> Thanks for prompt actions! > > > No problem. > >> I think no need to package it separately for testing, just release it >> to cygwin repo. > > > Ok. You can get it with: > > pip3 install git+http://cygwin.com/git/cygwin-apps/calm.git -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Challenge: a VERY strange problem with command substitution in bash
Hello I have seen a similar problem on Windows 7, using Cygwin bash version 4.4.12(3)-release (x86_64-unknown-cygwin). After repeating a simplified test on my own host and 6 other colleagues, my conclusion is that the cause is found in BeyondTrust SecureDesktop, which you also may have installed (I saw you wrote something about TrustedInstaller). I have raised an internal case with my IT service desk to resolve the issue (and see what they can do). The observations are as follows, in bash, standing in a subdir with 3 files a,b and c: (The results shown are on a host with SecureDesktop, but the only difference is at the last command) $ ls a b c $ echo $(ls) a b c $ echo $(ls|sort) a b c $ echo "$(ls)" a b c $ echo "$(ls|sort)" $ The problem is seen in the last line, where no output is produced, and the expected output is just like the previous command (the one without the ‘sort’). 3 colleagues also with SecureDesktop sees the same as I do, and 3 other colleagues without SecureDesktop sees the expected result (the last command produces output). Best regards Erik Haukjær Andersen Sr Pncpl Software Developer -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Challenge: a VERY strange problem with command substitution in bash
On 4. 12. 2017 14:01, Erik Haukjær Andersen wrote: Hello I have seen a similar problem on Windows 7, using Cygwin bash version 4.4.12(3)-release (x86_64-unknown-cygwin). After repeating a simplified test on my own host and 6 other colleagues, my conclusion is that the cause is found in BeyondTrust SecureDesktop, which you also may have installed (I saw you wrote something about TrustedInstaller). I have raised an internal case with my IT service desk to resolve the issue (and see what they can do). My understanding is that you're just reporing your findings, not asking for support here. Assuming that's the case, the only thing to do here is to add this to the BLODA. I actually can't find any mention of a product nor feature called SecureDesktop, so unless there are better ideas, let's do only "BeyondTrust". -- David Macek smime.p7s Description: S/MIME Cryptographic Signature
Re: mksetupini fails validating packages because curr is test
On 04/12/2017 12:02, Ivan Gagis wrote: Ok, thanks! But what would be the schedule of releasing it to cygwin repo? I don't want to mess up my CI scripts which install the whole build env from scratch on every build, so I need it in cygwin repo. So, you do want me to package it! I uploaded calm-20171204-1 -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] Updated: weechat-2.0-1
Version 2.0-1 of "weechat" has been uploaded. ChangeLog: https://weechat.org/files/changelog/ChangeLog-2.0.html DESCRIPTION WeeChat is a fast, light and extensible chat client. It runs on many platforms like Linux, Unix, BSD, GNU Hurd, Mac OS X and Windows (bash/ubuntu and cygwin). HOMEPAGE https://weechat.org/ Sébastien Helleu. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: gcc / gfortran 5.x
Thanks to all the lead me the way. Using cygwin's time machine I was able to build a working cygwin enviroment with gcc/gfortran at version 5.40. (http://ctm.crouchingtigerhiddenfruitbat.org/pub/cygwin/circa/64bit/2017/09/05/224214/) On 11/27/2017 12:58 PM, Achim Gratz wrote: Hans Horn writes: I noticed that cywgin's gcc/gfortran has moved whole sale to gcc 6.4. How can I get the latest release of the 5.x branch (32 and 64bit) back? Use the Cygwin Time Machine, some other post had the link. I'm trying to build a legacy suite of programs that I know builds under 5.x, but fails miserably under 6.4. Been there, done that. In general, trying to freeze the compilation environment is a losing proposition and it's better to fix up the sources instead. Regards, Achim. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: mksetupini fails validating packages because curr is test
Exactly! Thanks, it works perfectly now! Br, Ivan 2017-12-04 16:00 GMT+02:00 Jon Turney : > On 04/12/2017 12:02, Ivan Gagis wrote: >> >> Ok, thanks! But what would be the schedule of releasing it to cygwin repo? >> >> I don't want to mess up my CI scripts which install the whole build >> env from scratch on every build, so I need it in cygwin repo. > > > So, you do want me to package it! > > I uploaded calm-20171204-1 -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Challenge: a VERY strange problem with command substitution in bash
Greetings, Erik Haukjær Andersen! > (I saw you wrote something about TrustedInstaller). TrustedInstalller is a Windows component. %SystemRoot%\servicing\TrustedInstaller.exe -- With best regards, Andrey Repin Monday, December 4, 2017 23:08:53 Sorry for my terrible english...
Re: Challenge: a VERY strange problem with command substitution in bash
On 2017-12-04 06:22, David Macek wrote: > On 4. 12. 2017 14:01, Erik Haukjær Andersen wrote: >> Hello >> >> >> I have seen a similar problem on Windows 7, using Cygwin bash version >> 4.4.12(3)-release (x86_64-unknown-cygwin). >> >> After repeating a simplified test on my own host and 6 other >> colleagues, my conclusion is that the cause is found in BeyondTrust >> SecureDesktop, which you also may have installed (I saw you wrote >> something about TrustedInstaller). >> >> I have raised an internal case with my IT service desk to resolve the >> issue (and see what they can do). > > My understanding is that you're just reporing your findings, not asking for > support here. Assuming that's the case, the only thing to do here is to add > this to the BLODA. > > I actually can't find any mention of a product nor feature called > SecureDesktop, > so unless there are better ideas, let's do only "BeyondTrust". It's a marketing suggestion for referring to the PowerBroker product which manages locking down desktop and server privileges. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Case-sensitivity for #include with gcc
On 2017-12-04 17:14, Laurent Tassan-Got wrote: > Just consider the simple C program tstl.c [snip] > The compilation with the command > gcc -Wall -O2 -o tstl.exe tstl.c > is successful and the execution as well. > > Now the compilation with: > gcc -Wall -O2 -o tstl.exe -I /usr/include/X11 tstl.c > fails with the following messages: -I/usr/include/X11 is incorrect, regardless of case (in)sensitivity. X11 headers are namespaced, meaning that you should e.g. #include instead of . If your code doesn't do that, then you need to fix it. -- Yaakov signature.asc Description: OpenPGP digital signature
Need help with multibyte UTF-8 characters
I want to use multibyte UTF-8 characters in 64-bit Cygwin under Windows 7. The "vim" editor running in mintty displays the two-byte characters correctly, but not the three- (and I assume four-) byte characters, which instead display as rectangular filled-in blocks. The "less" program doesn't even display two-byte characters correctly, but instead displays them as to , depending on the character in question, in reverse color in the terminal window. The "cat" program is even worse, replacing every two-byte character with a character that looks like three horizontal bars stacked one above the other. I've read the "Internationalization" page in the Cygwin online manual, but am still baffled. My LANG environment variable is set to "en_US.UTF-8". Can anyone help? -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Need help with multibyte UTF-8 characters
On 2017-12-04 18:23, Thomas Taylor wrote:
> I want to use multibyte UTF-8 characters in 64-bit Cygwin under Windows 7.
> The
> "vim" editor running in mintty displays the two-byte characters correctly, but
> not the three- (and I assume four-) byte characters, which instead display as
> rectangular filled-in blocks. The "less" program doesn't even display
> two-byte
> characters correctly, but instead displays them as to , depending on
> the character in question, in reverse color in the terminal window. The "cat"
> program is even worse, replacing every two-byte character with a character
> that
> looks like three horizontal bars stacked one above the other. I've read the
> "Internationalization" page in the Cygwin online manual, but am still
> baffled.
> My LANG environment variable is set to "en_US.UTF-8". Can anyone help?
Check mintty/Options/Text/Locale[en_US]/Character set[UTF-8]/Apply/Save.
Then exit and restart mintty and your shell.
To see what locale Cygwin thinks you are set to, run:
$ locale
To check all Windows locale settings, you can run:
$ for o in -s -u -n -i -f ''; do locale $o; done
The first two should show your Windows install locale, the rest should show
anything you have set up, or the same locale.
If any settings don't match LANG, you may have to set LC_ALL=$LANG to force the
setting.
I use the following profile stanza across all systems for consistency:
# Set user-defined locale - use regional settings if available
locale -fU > /dev/null 2>&1 \
&& LC_ALL=`locale -fU` \
|| LC_ALL=`locale | \
/bin/sed '/^LANG=\|^LC_CTYPE=\|^LC_ALL=/{s///;h};$!d;x;s/"//g'`
export LC_ALL
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
