[ANNOUNCEMENT] Updated: scons-2.3.0-5
CYGWIN NEWS: This release prefers /usr/bin to /bin for Cygwin, to avoid the problem invoking /bin/gcc reported here http://cygwin.com/ml/cygwin/2013-11/msg00018.html DESCRIPTION: SCons is an Open Source software construction tool—that is, a next-generation build tool. Think of SCons as an improved, cross-platform substitute for the classic Make utility with integrated functionality similar to autoconf/automake and compiler caches such as ccache. In short, SCons is an easier, more reliable and faster way to build software. See http://www.scons.org/ for more details. CYGWIN NOTES: = Upstream does not provide good support for building DLLs for Cygwin. SCons will build the DLL as libMODULE.dll, but will not build an import library. This release includes a patched linker for Cygwin that will: * build the DLL as cygMODULE.dll * create an import library using the instructions from here: http://cygwin.com/cygwin-ug-net/dll.html This patched linker is only lightly tested. Please report any bugs to the main mailing list. If you're a Python programmer, please consider providing a patch, as the Cygwin maintainer is not a Python programmer. QUESTIONS: == If you want to make a point or ask a question the Cygwin mailing list is the appropriate place. -- David Rothenberger daver...@acm.org -- 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: vi stealing SYSTEM-owned permissions and ownership
Greetings, D. Boland! >> Your main problem is that you are trying to break into native Windows >> ACL system with Cygwin tools. And not only that, you also trying to >> wrest native ACLs into POSIX permissions, and expect native applications to >> work fine afterward. >> Which can be done theoretically, but in reality is a real big headache to >> maintain. > You are speaking of Cygwin as if it's some kind of quick hack. It is NOT a "quick hack". But to work across different paradigm boundaries, you have to know, what exactly it means and how it works. > This is not the case. Most of the tools are of the GNU software collection, > which is high quality software. ACL is also available on other Linux > flavours, and they don't have to "wrest" it into POSIX. I'm NOT talking about tools provided. I tell you about inherent difference between POSIX and Windows ACL's, short version and consequences of which I've explained already, and you can find some more technical details in Cygwin documentation. > Also, one could say that ACL is a superset of the POSIX model. No, unfortunately, you can not. As I said, there's inherent differences. > It uses POSIX's idea of users, groups and others, but then offers the > posibility to add more users and groups for more elaborate schemes. The > headache starts when one actually starts using these extra posibilities. POSIX ACL do not use selective inheritance model, as I'm aware. >> If you truly want to show your students their Windows systems from the >> command >> line, I suggest you learn Windows command line. >> If not very robust, it is nonetheless rich, and allow for many operations >> normally performed from GUI, and some operations, that can not be done from >> GUI, either without much complication or at all. >> In the case mentioned below, the "net" tool should come in handy. As well >> as "sc" tool. > I could just give my students an iMac, but these are not used in IT production > infrastructures. Windows (business/government) and Linux/Unix (ISP's) are. You make it sound like Macs are something from a parallel universe. Same *NIX, just more thoroughly put together. For the record: I've had a MacBook for near a year. Wrested it all to my needs. No problem whatsoever. > The Windows command line is frustrating to work on. For instance, their > implementation of autocompleting with the tab-key sucks. I'll give you a hint: http://farmanager.com/index.php?l=en > In stead of really simplifying and improving on DOS, MS comes up with more > weird tools like PowerShell. > Now you have to be a programmer to use the command-line. No need to "use command line". This is where you make a mistake. You use command-line tools to perform specific tasks. That's it. But if you inclined to "use command line", check out http://jpsoft.com/all-downloads/downloads.html >> Also, forcing someone to use vi over more sane editors is a torture which no >> one deserve. >> > Haha, yes. But if my students have to administer remote production-machines, > most of the time they have no other option. I want them to succeed where > others fail. I can't imagine a situation, where I only have one way to edit the file. Even on my web hosting, I have a choice between vi, mcedit, ed and ee. -- WBR, Andrey Repin (anrdae...@yandex.ru) 04.11.2013, <01:39> 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
Still confused about cyg_server vs. user id when logging in via ssh
When I login via ssh, I *appear* at first glance to have the same id and privileges as I do when I log in directly. a) If I am an administrator, then 'id -a' gives the following consistent answer for both direct and ssh login: uid=1001(myusername) gid=513(None) groups=513(None),0(root),544(Administrators),545(Users) b) If I am a regular user, then 'id -a' gives the following consistent answer: uid=1001(myusername) gid=513(None) groups=513(None),545(Users) However, there are some important differences. 1. First and most importantly, when I log in as administrator via 'ssh', somehow cyg_server seems to be the real owner of all my files (despite the fact that cygwin 'ls -al' seems to mask that). In particular, 'subinacl' gives /owner =mymachine\cyg_server /pace =winlawyer\cyg_server Type=0x0 Flags=0x0 AccessMask=0x1f019f For all files that are actually owned by me... though it gets the ownership right for files owned by others. This is a problem since I use ssh, as part of my backup scripts to run subinacl to backup acls. My bottom line question is whether there is any way to login via SSH and to get a shell with true ADMINISTRATOR privileges so that there is no difference between a SSH log in and a local login... at a minimum is there any way to get subinacl to work right. 2. Whether I log in as an ordinary user or as administrator via SSH, only some but not all user variables are properly set. So, for example "HOME" seems to be set properly but not for example "APPDATA". I don't understand why some variables are set and not others... -- 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-4.8.2-1: /bin/gcc fails
On 11/2/2013 9:54 PM, Yaakov (Cygwin/X) wrote: > On 2013-11-02 04:36, Corinna Vinschen wrote: >> On Nov 1 23:23, David Rothenberger wrote: >>> With gcc-4.8.2-1, the following fails: >>> >>> % touch /tmp/t.c >>> % /bin/gcc -c /tmp/t.c >>> gcc: error: spawn: No such file or directory > > Curious, are you seeing real-life references to /bin/gcc? Because that > wouldn't be portable anyway. I saw it when building serf, which uses scons. The "cygwin" environment in scons is derived from the "posix" environment, which sets PATH such that /bin is before /usr/bin. I've made a new scons release which reverses this for Cygwin, and that fixes the problem. -- David Rothenberger daver...@acm.org "We will bury you." -- Nikita Kruschev -- 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: How about a 64-bit installer that doesn't require UAC?
My apologies for the snark. The list archive ends at the same message as the top of the second page of the nabble rendering and I didn't immediately see the additional messages in nabble that include a workaround. On 2013-11-02 18:28, Andrey Repin wrote: Greetings, Bill Welch! Yes, I could try to change the application manifest myself, but that seems esoteric and I haven't been able to find any GPL tool. I suggest you use search before posting. This has been discussed already. The real solution would be a tool that run in postinstall scripts and can prompt user for privilege elevation, but noone had time or inclination to write one. Yet. -- WBR, Andrey Repin (anrdae...@yandex.ru) 03.11.2013, <02:26> 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: Some first questions.
Gert Koefoed Andersen wrote: > > Hello list. > > I have some first questions for cygwin works on windows 7 by compile sources > I normally just fine compile on my linux systems but not like to compile > well and by cygwin. > The sources I trying to compile is been packed on linux with tar archiwing > program so I can get the sources over to windows 7 and cygwin. > > So it is then this then. > 1. where is the best place to unpack the sources for compile by cygwin. >My windows cygwin is installed on c:\cygwin and by installing cygwin is > the cygwin download sources been put at k:\cygwinsrc. > 2. if the extra sources is best to be places at k:\cygwin, then is it then > best to handle them for cygwin ? > > 3. Then is it that - the sources have makefiles .cyg and other compilers + > some main configs like Makefile and huskymak.cfg. > When I have copied the file makefile.cyg to makefile.cfg and then have this > file in the main home dir for example - \...\husky\smapi\ and then is got in > to \smapi source dir and then run make to compile the sources for smapi goes > it fine to I getting a error of gcc -mno-cygwin and then error 2 of it not > can find some file it should make and when I checking out for the file is it > where it should be by not compile to make a .o files for more compile > finish. > > Regards, > Gert There is a standard location for sources, as is for libraries and includes. In Cygwin it's /usr/src. In some other Linuxes it's /usr/local/src. I have been compiling lots of source distributions over the years. I am not aware that you have to move or copy Makefiles. As far as I know you just need to: cd /usr/src/yournewapp ./configure make make install With the last command, all configuration files are automatically put in the right folders. HTH, Daniel -- 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: vi stealing SYSTEM-owned permissions and ownership
Andrey Repin wrote: > > Greetings, D. Boland! > > Your main problem is that you are trying to break into native Windows > ACL system with Cygwin tools. And not only that, you also trying to > wrest native ACLs into POSIX permissions, and expect native applications to > work fine afterward. > Which can be done theoretically, but in reality is a real big headache to > maintain. You are speaking of Cygwin as if it's some kind of quick hack. This is not the case. Most of the tools are of the GNU software collection, which is high quality software. ACL is also available on other Linux flavours, and they don't have to "wrest" it into POSIX. Also, one could say that ACL is a superset of the POSIX model. It uses POSIX's idea of users, groups and others, but then offers the posibility to add more users and groups for more elaborate schemes. The headache starts when one actually starts using these extra posibilities. > > If you truly want to show your students their Windows systems from the command > line, I suggest you learn Windows command line. > If not very robust, it is nonetheless rich, and allow for many operations > normally performed from GUI, and some operations, that can not be done from > GUI, either without much complication or at all. > In the case mentioned below, the "net" tool should come in handy. As well > as "sc" tool. > I could just give my students an iMac, but these are not used in IT production infrastructures. Windows (business/government) and Linux/Unix (ISP's) are. The Windows command line is frustrating to work on. For instance, their implementation of autocompleting with the tab-key sucks. In stead of really simplifying and improving on DOS, MS comes up with more weird tools like PowerShell. Now you have to be a programmer to use the command-line. > Also, forcing someone to use vi over more sane editors is a torture which no > one deserve. > Haha, yes. But if my students have to administer remote production-machines, most of the time they have no other option. I want them to succeed where others fail. > Sorry for my terrible english... No problem. Sincerely, Daniel -- 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: How about a 64-bit installer that doesn't require UAC?
I presume you're referring to http://cygwin.1069669.n5.nabble.com/cannot-run-setup64-exe-without-admin-privileges-even-if-renamed-foo-exe-td102712.html, where the final (official cygwin, apparently) word is that you think cygwin users are too stupid to be allowed a choice in 64-bit, that they have in 32-bit, no matter how locked down and single user their corporate machine might be. Thanks. On 2013-11-02 18:28, Andrey Repin wrote: Greetings, Bill Welch! Yes, I could try to change the application manifest myself, but that seems esoteric and I haven't been able to find any GPL tool. I suggest you use search before posting. This has been discussed already. The real solution would be a tool that run in postinstall scripts and can prompt user for privilege elevation, but noone had time or inclination to write one. Yet. -- WBR, Andrey Repin (anrdae...@yandex.ru) 03.11.2013, <02:26> 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
