Re: Ratpoison build error
I would guess that the ratpoison Makefile is putting the libraries in the wrong order. I think that the libraries shold be listed after the object files in the link command. On Mon, Apr 26, 2010 at 8:41 AM, David Sastre d.sastre.med...@gmail.com wrote: Hello, I'm trying to build ratpoison-1.4.5 (it's a window manager) with cygport but I'm failing at compile stage, because it complains about some some symbols not being defined (log attached). The devel libraries containing those symbols are installed. This is how gcc is invoked: gcc -march=prescott -O2 -pipe -fomit-frame-pointer -Wall -O2 -lXtst -lXinerama -lXext -lX11 -lXft -lXrender -lfontconfig -lexpat -liconv -lfreetype -lz -lX11 -lxcb -lXau -lXdmcp -lhistory -o ratpoison.exe actions.o bar.o completions.o communications.o editor.o events.o format.o frame.o getopt.o getopt1.o globals.o group.o history.o hook.o input.o linkedlist.o main.o manage.o number.o sbuf.o screen.o split.o window.o xinerama.o I'd like to understand what causes the linking error (if any). Any help would be much appreciated. Regards. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: xterm no longer accepts keyboard input
On Mon, Mar 15, 2010 at 10:44 AM, Jon TURNEY jon.tur...@dronecode.org.uk wrote: No. startx and startxwin are different tools to solve different problems. I keep adding more text to [1] to clarify this, but this doesn't appear to help, perhaps because nobody actually reads it... [1] http://x.cygwin.com/docs/ug/using.html#using-starting I read it. I just don't agree with it. These appear to be the reasons: 1) startxwin supplies the -multiwindow option to XWin.exe So does startx if you put that in the shortcut. 2) It uses a different script to start clients (~/.startxwinrc rather than ~/.xinitrc), because ~/.xinitrc will normally end by starting a window manager, which would be incorrect for ~/.startxwinrc (as it would discover the internal window manager is already running and exit immediately). In my opinion, it doesn't really matter with .xinitrc normally ends with. We can end it with anything that we want. It sounds like you can get the startxwin behavior (if that's what you really want) from startx if you put sh ~/.startxwinrc while : ; do sleep 1000; done in your .xinitrc. 3) startxwin exits after ~/.startxwinrc has completed and leaves XWin.exe running, whereas startx waits until ~/.xinitrc exits (which is usually waiting for the window manager started by it to exit) and then kills XWin.exe. If you don't like the behavior of startx exiting after the .xinitrc is complete, then why not write your .xinitrc so that it doesn't exit? Is it really worth maintaining another program when you can get the same behavior out of existing programs through config changes? Additionally, the startxwin.exe program is missing the security feature of creating a .Xauthority file. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: xterm no longer accepts keyboard input
On Sun, Mar 14, 2010 at 7:17 AM, Jeff Spirko spi...@gmail.com wrote: The icon runs from the Windows environment, so the run.exe and bash.exe wrapper programs are needed to set up the proper cygwin environment. Once you're in a cygwin shell, you already have the cygwin environment set up. That's why you don't need to type them in from the command line. So, they really should be equivalent. I've probably missed a prior discussion, but if startxwin.exe doesn't set up the Cygwin environment, then what good is it? I thought that this was about the only advantage that startxwin.bat had over startx. Considering that startx also sets up the .Xauthority file and startxwin.exe doesn't, I see absolutely no reason to use startxwin.exe instead of startx. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: XWin crashing...
On Tue, Mar 11, 2008 at 1:58 PM, [EMAIL PROTECTED] wrote: I've just installed cygwin latest stable version, and after trying to execute 'startx' it fails with some errors. I've tried several times, and in the third time, a popup appeared saying XWin.exe crashed. Please see below for the output of the startx command (no xwin crash this time)... I'm running Windows Vista Business with latest patches also... ... 365 [main] xterm 4772 child_copy: linked dll bss write copy failed, 0x333000..0x333A50, done 0, windows pid 6076, Win32 error 487 I had a similar error that was caused by Logitech webcam software. I'd check out the Cygwin FAQ (http://cygwin.com/faq.html), especially 4.42. What applications have been found to interfere with Cygwin? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
