Problem with NC.1.107
Just installed nc 1.107-4 expecting to use it to debug some code. This is what I get when I try to run it. $ nc 192.168.1.135 23 bash: /usr/bin/nc: Permission denied The file permissions are messed up. $ file /usr/bin/nc /usr/bin/nc: writable, executable, regular file, no read permission I don't see the PE32+ executable (console) x86-64, for MS Windows string. here is the file in /usr/bin $ ls -l nc* -rwxr-xr-x 1 lbmgm lbmgm 24576 Mar 19 2013 nc.exe I looked at the make file, it seems to be o.k. for generating a runable program. (uses gcc) but I don't have enough stuff installed to allow a build. -- 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 -fsanitize => cannot find -lubsan
On 3/27/18, Brian Inglis wrote:
> On 2018-03-27 11:39, Lee wrote:
>> How do you figure out which package is missing from your install?
>> $cat sbstrict.c
>> int main () {
>> return 0;
>> }
>> $i686-w64-mingw32-gcc -fsanitize=bounds-strict sbstrict.c
>> /usr/lib/gcc/i686-w64-mingw32/6.4.0/../../../../i686-w64-mingw32/bin/ld:
>> cannot find -lubsan
>> collect2: error: ld returned 1 exit status
>> $gcc -fsanitize=bounds-strict sbstrict.c
>> /usr/lib/gcc/x86_64-pc-cygwin/6.4.0/../../../../x86_64-pc-cygwin/bin/ld:
>> cannot find -lubsan
>> collect2: error: ld returned 1 exit status
>> I looked at
>> https://cygwin.com/cgi-bin2/package-grep.cgi?grep=ubsan=x86_64
>> and both
>> gcc-debuginfo-6.4.0-5
>> mingw64-i686-gcc-debuginfo-6.4.0-1
>> have a ubsan.c, but ld wouldn't be looking for that. Right??
>
> Implies that gcc includes support, but not supported as of 2015:
>
> https://sourceware.org/ml/cygwin/2015-10/msg00528.html
>
> - don't know why - or if since added.
I dunno what version of gcc cygwin had in 2015 but it looks like it wasn't v6.
https://www.gnu.org/software/gcc/gcc-6/
GCC 6.1 April 27, 2016 (there is no gcc 6.0 listed in the release history)
-fsanitize=bounds-strict was added in gcc v6, which is the current
cygwin & mingw gcc
https://www.gnu.org/software/gcc/gcc-6/changes.html
UndefinedBehaviorSanitizer gained a new sanitization option,
-fsanitize=bounds-strict, which enables strict checking of array
bounds. In particular, it enables -fsanitize=bounds as well as
instrumentation of flexible array member-like arrays.
$gcc --version
gcc (GCC) 6.4.0
Copyright (C) 2017 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
$i686-w64-mingw32-gcc --version
i686-w64-mingw32-gcc (GCC) 6.4.0
Copyright (C) 2017 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Thanks,
Lee
--
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: setup: uninstalling an orphaned package
On 3/26/2018 1:55 PM, Ken Brown wrote:
In ChooserPage::applyCommandLinePackageSelection() we have the following
code:
bool wanted = pkg.isManuallyWanted();
bool deleted = pkg.isManuallyDeleted();
bool basemisc = (pkg.categories.find ("Base") !=
pkg.categories.end ()
|| pkg.categories.find ("Orphaned") != pkg.categories.end
());
[...]
bool reinstall = (wanted || basemisc) && deleted;
One strange consequence of this is that if the user tries to uninstall
an orphaned package on the command line, then setup will instead try to
reinstall it.
This behavior was introduced in the following commit:
commit a667a8b289ccb6e70ec6bf4c70cceeca4d3fb5d3
Author: Corinna Vinschen
Date: Thu Jul 25 12:03:49 2013 +
[...]
Uninstalled packages in categories "Base" or "Misc" are always selected
for installation; installed packages in these categories are not
eligible for deletion and will be reinstalled or upgraded instead.
[...]
I can't understand the rationale for this. Did "Misc" (which has since
been renamed to "Orphaned") used to have a different meaning?
I found it very surprising when I tried to uninstall a bunch of packages
in unattended mode, and setup failed with download errors because it
tried to reinstall orphaned packages.
Patch attached.
Ken
From 3a78453fd8a3b5d9734a11b839f13e68c84d1c05 Mon Sep 17 00:00:00 2001
From: Ken Brown
Date: Tue, 27 Mar 2018 13:56:27 -0400
Subject: [PATCH setup] Allow command-line uninstallation of specific orphaned
packages
Also change the implementation of the "--delete-orphans" option to use
the same definition of "orphaned" that's used elsewhere in the code.
---
choose.cc | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/choose.cc b/choose.cc
index 5a4d3ad..1249efa 100644
--- a/choose.cc
+++ b/choose.cc
@@ -295,13 +295,13 @@ ChooserPage::applyCommandLinePackageSelection()
packagemeta = *(i->second);
bool wanted= pkg.isManuallyWanted();
bool deleted = pkg.isManuallyDeleted();
- bool basemisc = (pkg.categories.find ("Base") != pkg.categories.end ()
-|| pkg.categories.find ("Orphaned") != pkg.categories.end
());
- bool upgrade = wanted || (!pkg.installed && basemisc);
+ bool base = pkg.categories.find ("Base") != pkg.categories.end ();
+ bool orphaned = pkg.categories.find ("Orphaned") != pkg.categories.end
();
+ bool upgrade = wanted || (!pkg.installed && base);
bool install = wanted && !deleted && !pkg.installed;
- bool reinstall = (wanted || basemisc) && deleted;
- bool uninstall = (!(wanted || basemisc) && (deleted ||
PruneInstallOption))
-|| (!pkg.curr && CleanOrphansOption);
+ bool reinstall = (wanted || base) && deleted;
+ bool uninstall = (!(wanted || base) && (deleted || PruneInstallOption))
+|| (orphaned && CleanOrphansOption);
if (install)
pkg.set_action (packagemeta::Install_action, pkg.curr);
else if (reinstall)
--
2.16.2
Re: gcc -fsanitize => cannot find -lubsan
On 2018-03-27 11:39, Lee wrote:
> How do you figure out which package is missing from your install?
> $cat sbstrict.c
> int main () {
> return 0;
> }
> $i686-w64-mingw32-gcc -fsanitize=bounds-strict sbstrict.c
> /usr/lib/gcc/i686-w64-mingw32/6.4.0/../../../../i686-w64-mingw32/bin/ld:
> cannot find -lubsan
> collect2: error: ld returned 1 exit status
> $gcc -fsanitize=bounds-strict sbstrict.c
> /usr/lib/gcc/x86_64-pc-cygwin/6.4.0/../../../../x86_64-pc-cygwin/bin/ld:
> cannot find -lubsan
> collect2: error: ld returned 1 exit status
> I looked at
> https://cygwin.com/cgi-bin2/package-grep.cgi?grep=ubsan=x86_64
> and both
> gcc-debuginfo-6.4.0-5
> mingw64-i686-gcc-debuginfo-6.4.0-1
> have a ubsan.c, but ld wouldn't be looking for that. Right??
Implies that gcc includes support, but not supported as of 2015:
https://sourceware.org/ml/cygwin/2015-10/msg00528.html
- don't know why - or if since added.
--
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
gcc -fsanitize => cannot find -lubsan
How do you figure out which package is missing from your install?
$cat sbstrict.c
int main () {
return 0;
}
$i686-w64-mingw32-gcc -fsanitize=bounds-strict sbstrict.c
/usr/lib/gcc/i686-w64-mingw32/6.4.0/../../../../i686-w64-mingw32/bin/ld:
cannot find -lubsan
collect2: error: ld returned 1 exit status
$gcc -fsanitize=bounds-strict sbstrict.c
/usr/lib/gcc/x86_64-pc-cygwin/6.4.0/../../../../x86_64-pc-cygwin/bin/ld:
cannot find -lubsan
collect2: error: ld returned 1 exit status
I looked at
https://cygwin.com/cgi-bin2/package-grep.cgi?grep=ubsan=x86_64
and both
gcc-debuginfo-6.4.0-5
mingw64-i686-gcc-debuginfo-6.4.0-1
have a ubsan.c, but ld wouldn't be looking for that. Right??
Thanks
Lee
--
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: Quotes around command-line argument that has unicode characters are not removed
On 2018-03-27 03:56, Andrey Repin wrote: >>> Locale settings affecting Cygwin binary. >>> If you >>> set LANG=ru_RU.CP866 >>> (f.e.) >>> before invoking cygwin testcase in native CMD, you will likely see it >>> working better. >> Thanks for this advise, Andrey. I see that it reacts, but works worth :) >> I think it advises to output characters in CP866, but console is UTF-8: >> D:\cli> set LANG=ru_RU.CP866 >> D:\cli> test "текст плюс.txt" >> param 0 = test >> param 1 = ⥪▒▒ .txt >> Failed to open '⥪▒▒ .txt': No such file or directory >> But.. ta-da! I made it working like that: >> D:\cli> set LANG=ru_RU.UTF-8 >> D:\cli> test "текст плюс.txt" >> param 0 = test >> param 1 = текст плюс.txt >> File 'текст плюс.txt' was opened >> Hooray, it worked! > This is no magic. Console settings must match locale set in the environment. > Please test again with "chcp" to get current console codepage and setting > LANG to match it. > I could not see which version of Windows you're using, sorry. It is possible > that console is set to a different codepage than usual. >>> Alternatively, you could try >>> chcp 65001 >> That does not help: >> D:\cli> chcp 65001 >> Active code page: 65001 >> D:\cli> test "текст плюс.txt" >> param 0 = test >> param 1 = "текст плюс.txt" >> Failed to open '"текст плюс.txt"': No such file or directory >> [1] >> https://github.com/openunix/cygwin/blob/master/winsup/cygwin/dcrt0.cc#L297 >> [2] >> https://github.com/openunix/cygwin/blob/master/winsup/cygwin/dcrt0.cc#L165 If you're using cmd you can also set AutoRun commands like: $ cat HKCU-SW-MS-Command_Processor-AutoRun-chcp_65001.reg Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Command Processor] "AutoRun"="@chcp 65001 >nul" - append " && command..." to add more commands to AutoRun; these must use only the common base characters. -- 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: Tarball from cygwin.com git tag
reply on the mailing list please
On 27/03/2018 06:19, Wolfgang Stoeggl wrote:
>On 27/03/2018 01:22, Wolfgang Stoeggl via cygwin wrote:
>> Hello,
>> is it possible to get a tarball with the source files from a tag in
cygwin.com git?
>>
>> Similar to:
>>
https://github.com/OWNER/%{name}/archive/%{gittag}/%{name}-%{version}.tar.gz
>>
https://bitbucket.org/OWNER/%{name}/get/%{gittag}.tar.gz#/%{name}-%{version}.tar.gz
>>
https://gitlab.com/OWNER/%{name}/repository/archive.tar.gz?ref=GIT-TAG#/%{name}-%{version}.tar.gz
>>
>> e.g. from the following gittag (release-6_4):
>>
>>
https://cygwin.com/git/?p=cygwin-apps/windows-default-manifest.git;a=shortlog;h=refs/tags/release-6_4
>>
>> Thanks and best regards
>> Wolfgang
>>
>
>use mirror
>https://github.com/cygwin/cygwin
>https://github.com/cygwin/cygwin/releases
>
>Regards
>Marco
Dear Marco,
thanks for you reply.
Currently, the cygwin-apps of interest are not mirrored at github, e.g.
https://cygwin.com/git/?p=cygwin-apps/windows-default-manifest.git
Only calm is mirrored so far (https://github.com/cygwin/calm).
Would you have another idea?
Thanks and best regards
Wolfgang
cygwin-apps is not a single repository.
Except setup and calm the rest of utilities are not updated a lot
so to have the last one you can just download the source package,
If you clarify which one you are interested may be the maintainer will
mirror on github.
Regards
Marco
--
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: Issues with setting or not setting HOME environment variable
Greetings, David Karr! > I currently do not set the HOME environment variable. I get the > impression you're not supposed to do that. When I run a mintty shell, > it correctly puts me in "/home/", which is what I want. > I'm running into a problem with Eclipse egit, as I think it's looking > for the "HOME" environment variable to determine where the .gitconfig > file is. If it doesn't find "HOME" set, I have a feeling it's looking > for "HOMEDRIVE", which is set to something I can't easily control. > Is there some way I can set "HOME" to my Windows home location, but > still have Cygwin do the right thing and go to "/home/"? It's not Cygwin, it's bash setting HOME when run as login shell. If you wish, you can force that setting in ~/.profile or otherwise manipulate the environment prior to starting mintty. I, for one, prefer my $HOME match my real profile home. Don't see the reason to spread my stuff thin across the filesystem. -- With best regards, Andrey Repin Tuesday, March 27, 2018 12:57:18 Sorry for my terrible english... -- 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: Quotes around command-line argument that has unicode characters are not removed
Greetings, Dmitry Katsubo! >> Locale settings affecting Cygwin binary. >> >> If you >> set LANG=ru_RU.CP866 >> (f.e.) >> before invoking cygwin testcase in native CMD, you will likely see it >> working better. > Thanks for this advise, Andrey. I see that it reacts, but works worth :) > I think it advises to output characters in CP866, but console is UTF-8: > D:\cli> set LANG=ru_RU.CP866 > D:\cli> test "текст плюс.txt" > param 0 = test > param 1 = ⥪▒▒ .txt > Failed to open '⥪▒▒ .txt': No such file or directory > But.. ta-da! I made it working like that: > D:\cli> set LANG=ru_RU.UTF-8 > D:\cli> test "текст плюс.txt" > param 0 = test > param 1 = текст плюс.txt > File 'текст плюс.txt' was opened > Hooray, it worked! This is no magic. Console settings must match locale set in the environment. Please test again with "chcp" to get current console codepage and setting LANG to match it. I could not see which version of Windows you're using, sorry. It is possible that console is set to a different codepage than usual. >> Alternatively, you could try >> chcp 65001 > That does not help: > D:\cli> chcp 65001 > Active code page: 65001 > D:\cli> test "текст плюс.txt" > param 0 = test > param 1 = "текст плюс.txt" > Failed to open '"текст плюс.txt"': No such file or directory > [1] https://github.com/openunix/cygwin/blob/master/winsup/cygwin/dcrt0.cc#L297 > [2] https://github.com/openunix/cygwin/blob/master/winsup/cygwin/dcrt0.cc#L165 -- With best regards, Andrey Repin Tuesday, March 27, 2018 12:51:10 Sorry for my terrible english...
Re: Tarball from cygwin.com git tag
On 27/03/2018 01:22, Wolfgang Stoeggl via cygwin wrote:
Hello,
is it possible to get a tarball with the source files from a tag in cygwin.com
git?
Similar to:
https://github.com/OWNER/%{name}/archive/%{gittag}/%{name}-%{version}.tar.gz
https://bitbucket.org/OWNER/%{name}/get/%{gittag}.tar.gz#/%{name}-%{version}.tar.gz
https://gitlab.com/OWNER/%{name}/repository/archive.tar.gz?ref=GIT-TAG#/%{name}-%{version}.tar.gz
e.g. from the following gittag (release-6_4):
https://cygwin.com/git/?p=cygwin-apps/windows-default-manifest.git;a=shortlog;h=refs/tags/release-6_4
Thanks and best regards
Wolfgang
use mirror
https://github.com/cygwin/cygwin
https://github.com/cygwin/cygwin/releases
Regards
Marco
--
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
Tarball from cygwin.com git tag
Hello,
is it possible to get a tarball with the source files from a tag in cygwin.com
git?
Similar to:
https://github.com/OWNER/%{name}/archive/%{gittag}/%{name}-%{version}.tar.gz
https://bitbucket.org/OWNER/%{name}/get/%{gittag}.tar.gz#/%{name}-%{version}.tar.gz
https://gitlab.com/OWNER/%{name}/repository/archive.tar.gz?ref=GIT-TAG#/%{name}-%{version}.tar.gz
e.g. from the following gittag (release-6_4):
https://cygwin.com/git/?p=cygwin-apps/windows-default-manifest.git;a=shortlog;h=refs/tags/release-6_4
Thanks and best regards
Wolfgang
--
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
