> 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
