Re: croos compiler error
Mark A. Engel wrote: cygwin64: I have been trying to build the cross compiler tool for my Windows 10. I have installed cygwin64 and is working well. I downloaded the crosstool-0.43 version. I have executed "sh demo-x86_64.sh" and after a bout 10 minutes of building the build fails with "cc: error: spawn: No such file or directory". See attached file. I have tried to install/get a spawn package with the setup-x86_64 command. There is no spawn package. I cannot get any further on the build. I have looked everywhere and no use. Let me know what I am missing or where I can get the spawn command for cygwin64 on Windows 10. Thanks for continuing here, Mark. Unfortunately, you can color me mystified. "spawn" is not a Cygwin command or package. It's not clear from the log what exactly is requiring "spawn". I see that a number of gprof source files were compiled successfully by gcc, but then there's a "cc" command that failed. On normal Cygwin installations, cc is a symlink to gcc.exe but I wonder if that's true on your system. To go further with this we'll need the cygcheck output described on http://cygwin.com/problems.html, namely 'cygcheck -svr > foo' and then *attach* foo to your next reply, without compressing or encoding it. I also see that crosstool has not been updated since 2006. The source packages it downloads to build are all old versions of things. You may be interested that there is also a crosstool-NG (next generation) that was updated last year and I was able to download, configure, build, and install on Cygwin64 without any trouble. So this may be way forward for you if ct-ng supports your target and you don't absolutely require crosstool. Hope this helps somehow, ..mark -- 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
p11-kit: p11-kit-trust: module failed to initialize
$ wget -q -O/dev/null https://cygwin.com p11-kit: p11-kit-trust: module failed to initialize: The module has already been initialized This is with wget 1.19.1-2 and p11-kit 0.23.5-1. Any ideas what the problem is? Thanks, Andrew -- 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: p11-kit: p11-kit-trust: module failed to initialize
> $ wget -q -O/dev/null https://cygwin.com > p11-kit: p11-kit-trust: module failed to initialize: The module has already > been > initialized Sorry, I see this is a dup. Please ignore. https://sourceware.org/ml/cygwin/2018-04/msg3.html -- 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: p11-kit: p11-kit-trust: module failed to initialize
On 2018-04-06 09:22, Andrew Schulman wrote: > $ wget -q -O/dev/null https://cygwin.com > p11-kit: p11-kit-trust: module failed to initialize: The module has already > been > initialized > > This is with wget 1.19.1-2 and p11-kit 0.23.5-1. Any ideas what the problem > is? Rolling libgnutls30 back to 3.5.13-1 [prev] eliminates the message. -- 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: Cygwin warning while running IC-CAP
On 2018-04-06 10:11, Sheida Gohardehi wrote: > My name is Sheida Gohardehi and I'm a research assistant at the University > of Waterloo under the supervision of Prof. Dr. Sachdev. > I have the IC-CAP tool and its licence, But every time I open a new example > or anything I receive the following warning: > "0 [main] cygpath 1308 find_fast_cwd: WARNING: Couldn't compute FAST_CWD > pointer. Please report this problem to the public mailing list > cygwin@cygwin.com" This is just a warning to please upgrade Cygwin as explained at: https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings and please report the issue to whoever distributes the software you are using. -- 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
openssh AuthorizedKeysFile
I've got a new server for Cygwin @work and wanted to get the sshd to run with StrictMode on (it's been off on the old server). Long story short, some accounts used for administrative tasks are contrained so that I need to store the authorized_keys file directly on the server, so I added /etc/ssh/%u/authorized_keys in front of the default .ssh/authorized_keys. Unfortunately that only works if the same administrative account has been used to install Cygwin itself, lest sshd declares the directory /etc/ssh unsafe (or use StrictMode=no). I found this patch that seems to address exactly the same situation: https://github.com/pierresouchay/cygwin_patches/blob/master/openssh.patch The code has since been refactored and a similar change would need to be applied elsewhere. Interestingly enough there is some special handling to _not_ check all the leading path components for the home directory (otherwise it wouldn't work at all). In my reading of the refactored code it seems that the same effect could be achieved by defining PLATFORM_SYS_DIR_UID appropriately (although I would prefer if that was configurable somewhere in a file). But it seems that for Cygwin that symbol doesn't get defined at all? Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables
