Re: latest lighttpd (1.4.45) not working on Windows 10 Home Edition
> Please don't top-post on this list. Yikes. I intended not to top-post, but it seems that replying from a forwarded copy (I forward Outlook.com email to another email provider) is no good. I've reconfigured my email client hoping I fixed it. > Your build is not identical with it. I remember choosing that word; I should have gone with "similar". > If your goal is to provide useful information for the lighttpd > maintainer, you should use the same configure options that he used. I wanted to somehow ameliorate my first post with the bits I could recently gather because I considered them sort of good news, but I'll try to reproduce lighttpd package ASAP and report back. Alejandro El 07/12/2018 a las 12:06, Ken Brown escribió: > [Please don't top-post on this list.] > > On 12/7/2018 9:13 AM, Alejandro Benitez wrote: >> Hi, >> >> I'd like to add more information to the report. >> >> With the help of the IRC support channel I've managed to successfully >> run a build of a later version of lighttpd (v 1.4.52) which is the >> latest tarball available at >> >> https://www.lighttpd.net/download/ >> >> with the following build configuration >> >> `./configure --without-bzip2 --with-openssl --with-lua` >> >> The build is quite identical to the Cygwin build; I did not have to >> tweak my configuration files and everything worked as expected, whereas >> the current Cygwin package (v 1.4.45) shows the behavior I previously >> reported. > Out of curiosity, I downloaded the source for the Cygwin build, and your build > is not identical with it. If your goal is to provide useful information for > the > lighttpd maintainer, you should use the same configure options that he used. > > Ken > > -- > 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 > -- 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: latest lighttpd (1.4.45) not working on Windows 10 Home Edition
Hi, I'd like to add more information to the report. With the help of the IRC support channel I've managed to successfully run a build of a later version of lighttpd (v 1.4.52) which is the latest tarball available at https://www.lighttpd.net/download/ with the following build configuration `./configure --without-bzip2 --with-openssl --with-lua` The build is quite identical to the Cygwin build; I did not have to tweak my configuration files and everything worked as expected, whereas the current Cygwin package (v 1.4.45) shows the behavior I previously reported. Best regards, El 29/11/2018 a las 11:31 a.m., Alejandro Benitez escribió: > Hi, > Id like to share that the latest Cygwin lighttpd package does not work > for me on Windows 10 Home Edition. Neither 32-bit nor 64-bit package. I > had the chance to test it on both architectures because when I first ran > into this problem I was running Windows 10 32-bit on this AMD64 PC, but > later on I did a fresh install of Windows 10 64-bit; the reason for the > architecture mismatch was that PC vendor sold AMD64 PCs with Windows 7 > Starter Edition (which was 32-bit only IIRC). > Back to lighttpd: the previous version (1.4.41) does run OK with the > same config files. > I suspected the newer lighttpd might have been somehow incompatible with > v 1.4.41 config files, but I have another machine with Windows 7 64-bit > and v 1.4.45 does run OK with similar config files. > The error is non verbose: when I try to load any web page (static or > PHP) the browser just remains *loading* for a long time and later ends > with a timeout error page, whereas the previous lighttpd binary just > loads the page fast. There are no logs written in access.log error.log > or cygrunsrv.log files. > I'm not sure, but I'd guess it's a compatibility issue with Windows 10. > I have mod_access, mod_redirect, mod_rewrite, mod_magnet, mod_proxy, > mod_fastcgi (for PHP integration) enabled. > I tried accessing it at every ip (127.0.0.1, lan ip and internet ip) > where the previous version succeeds, to no avail. > The lighttpd (1.4.45) service also takes too long to stop and sometimes > it just fails to do so. > I use latest PHP packages for both v 1.4.41 and v 1.4.45 tests. > I run Windows 10 April 2018 Update or Windows 10 version 1803. > Thanks in advance, > > > -- > 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 > -- 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
latest lighttpd (1.4.45) not working on Windows 10 Home Edition
Hi, Id like to share that the latest Cygwin lighttpd package does not work for me on Windows 10 Home Edition. Neither 32-bit nor 64-bit package. I had the chance to test it on both architectures because when I first ran into this problem I was running Windows 10 32-bit on this AMD64 PC, but later on I did a fresh install of Windows 10 64-bit; the reason for the architecture mismatch was that PC vendor sold AMD64 PCs with Windows 7 Starter Edition (which was 32-bit only IIRC). Back to lighttpd: the previous version (1.4.41) does run OK with the same config files. I suspected the newer lighttpd might have been somehow incompatible with v 1.4.41 config files, but I have another machine with Windows 7 64-bit and v 1.4.45 does run OK with similar config files. The error is non verbose: when I try to load any web page (static or PHP) the browser just remains *loading* for a long time and later ends with a timeout error page, whereas the previous lighttpd binary just loads the page fast. There are no logs written in access.log error.log or cygrunsrv.log files. I'm not sure, but I'd guess it's a compatibility issue with Windows 10. I have mod_access, mod_redirect, mod_rewrite, mod_magnet, mod_proxy, mod_fastcgi (for PHP integration) enabled. I tried accessing it at every ip (127.0.0.1, lan ip and internet ip) where the previous version succeeds, to no avail. The lighttpd (1.4.45) service also takes too long to stop and sometimes it just fails to do so. I use latest PHP packages for both v 1.4.41 and v 1.4.45 tests. I run Windows 10 April 2018 Update or Windows 10 version 1803. Thanks in advance, -- 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
Windows upgrade
Hi, I have a 32 bit cygwin installation of 8 years of age in an amd64 PC with 2 GB of RAM with Windows 10. So far it's been so good. I never had the need to use a 64 bit Windows, but recently 64 bit has become mainstream and I also started having low memory issues, so I upgraded to 4 GB of RAM. The thing is 32 bit Windows has issues with the whole 4 GB of RAM therefore I have quite less available, so I decided I will be switching to 64 bit Windows 10 via a clean install (yuk!) when I am able. I'll be following the steps outlined in this post or a similar one: https://www.howtogeek.com/228042/how-to-switch-from-32-bit-windows-10-to-64-bit-windows-10/ It's somehow clear I thankfully won't need to upgrade to cygwin64 until later, I mean it seems I'll be able to still use my 32 bit cygwin after I upgrade to 64 bit Windows 10, I just don't know what I'll need to tweak / migrate so that the new Windows installation installed on top of the same drive that currently holds the 32 bit cygwin knows it's there. I'm betting some registry entries and environment variables. Does anyone know these tweaks for certain? I need cygwin to be fully functional, I mean setup.exe needs to be able to install packages, otherwise it won't be of much use. I might also be wrong and need to install cygwin64 as I upgrade Windows. Fingers are crossed. Thanks in advance, -- 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: Add emacs build with LUCID X toolkit ?
> vfork issues almost always indicate a need to do a full rebase. Thank you. I really should have clarified that, I did try several rebaseall approaches to no avail. It seems this emacs build is a bit dated (March 2017) and might be linking to some dll files rebaseall is not honoring. I will post this or a related question in a new thread as soon as I can perform further tests. I just didn't want to wait to do the emacs build with lucid x toolkit suggestion. El 05/03/2018 a las 11:03 a.m., Ken Brown escribió: > On 3/5/2018 8:21 AM, Alejandro Benitez wrote: >> Hi, >> I often painstakingly work on my build of emacs and never look back, >> praying to never come back, but then I get some annoyances such as >> vfork issues I can't fix. I will go further on this in a different post. > > vfork issues almost always indicate a need to do a full rebase. See > > https://cygwin.com/faq/faq.html#faq.using.fixing-fork-failures . > > Or switch from 32-bit Cygwin to 64-bit Cygwin, where such problems are > extremely rare. > >> Maybe add a new emacs-lucid package ? > > Cygwin's emacs uses GTK+ because that's the default for an emacs build > on all unix-like platforms. But I'll think about adding an > emacs-lucid package for the next emacs release. It would be good to > know how much demand there is for this. Are there other emacs-X11 > users who would prefer the Lucid toolkit? > > Ken > > > -- > 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 > -- 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
Add emacs build with LUCID X toolkit ?
Hi, I often painstakingly work on my build of emacs and never look back, praying to never come back, but then I get some annoyances such as vfork issues I can't fix. I will go further on this in a different post. So, if there's anyone related to the Cygwin's emacs package, pretty please change the widget choice from gtk to lucid / athena, it adds a lot more power to emacs. Otherwise, every time you close the X Server, emacs running in server mode will crash due to a longstanding gtk bug when X display is disconnected. Emacs even outputs a friendly last message with a link to the bug before crashing. Emacs folks tend to have an eternal emacs server instance running on their PCs that often / can endure killing the Windows console session and then resuming it at your next logon or just keep the fun via ssh. We can't do this with Cygwin's emacs package, so it needs to build emacs yourself. Maybe add a new emacs-lucid package ? And really I guess most emacs users just remove tool-bars, menu-bars, scroll-bars first thing in their config file and use the keyboard. Thanks! Same request to Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=1471258 -- 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
