Re: Cannot get icon box with lesstif
On Sat, 16 Dec 2006, Irving Bunton wrote: > I'm trying to get the icon box to appear with lesstif. What window manager are you using? -- Brian Ford Lead Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained crew... -- 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: glTexImage3D missing?
On Thu, 31 Aug 2006, Bernhard Ege wrote: > Thanks. I tried to link with GL, GLU and glut but linking kept failing. Note that these are: the X11 versions, newer than 1.1, but based on Mesa, so they are software rendering. There is a special test version of the X server that allows hardware rendering to work here, but it is very alpha. So, if performance is a major consideration, the Windows native versions are your only good choice. > Brian Ford wrote: > > Microsoft's OpenGL is version 1.1. glTexImage3D is not a version 1.1 > > feature. You need to learn how to load extensions and look at > > EXT_texture3d and glTexImage3DEXT. > > Thanks again. I knew glTexImage3D wasn't a 1.1 feature, but since I had > so many problems compiling opengl with cygwin, I ended up linking with > the windows libraries. I did try to load glTexImage3D but kept failing. > I'll try using you hints to work out a solution using the windows libraries. Given you have a glut based app, if there are no extraneous X11 calls, this is your best bet. -- Brian Ford Lead Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained crew... . -- 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: glTexImage3D missing?
On Wed, 30 Aug 2006, Bernhard Ege wrote: > I am trying to compile an opengl program and have managed to get all but > 1 error to disappear: > > gcc -o 3dtexture 3dtexture.c -lglut32 -lglu32 -lopengl32 > /cygdrive/c/DOCUME~1/bme/LOCALS~1/Temp/ccAhs05G.o:3dtexture.c:(.text+0xa7b): > undefined reference to [EMAIL PROTECTED]' > collect2: ld returned 1 exit status > make: *** [3dtexture] Error 1 > > I have been unable to resolve this error. I did find _glTexImage3D in > /usr/X11R6/lib/libGL.dll.a but I have been unable to take advantage of it. > > Am I missing something obvious? ;-) Several things. You linked with -lglut32 -lglu32 -lopengl32 which are Windows native libraries, but posted to the cygwin-xfree mailing list. As such, you're off topic ;-). cygwin is the place to discuss these libraries. /usr/X11R6/lib/libGL.dll.a is the OpenGL for X11 and would be linked as -L/usr/X11R6/lib -lGLU -lGL (I think that freeglut is now available for X11 in Cygwin, but I have never used it). Microsoft's OpenGL is version 1.1. glTexImage3D is not a version 1.1 feature. You need to learn how to load extensions and look at EXT_texture3d and glTexImage3DEXT. -- Brian Ford Lead Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained crew... . -- 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: Cygwin/X on multiple displays, nothing displayed
On Tue, 29 Aug 2006, Justin Patrin wrote: > On 8/29/06, Brian Ford wrote: http://cygwin.com/acronyms/#PCYMTNQREAIYR Thanks. > > On Tue, 29 Aug 2006, Justin Patrin wrote: > > > Does anyone have any clues how to fix this issue? > > > > -multiplemonitors ? > > Thanks, I should have checked for/tried that previously. Unfortunately > it makes no difference at all. I've attempted some more things and > here is what I have found: > > -multiplemonitors makes no difference with any of the other options I tried. > > -multiwindow is my default mode and works on one monitor but not on > two. Some more testing today has shown that output works only on the > leftmost monitor but only at the resolution of the primary monitor. Works fine for me with two. Are the two monitors at different color depths? Are they being driven by the same vendor's video driver? You did start X after having the destop extended, right? Changes in monitor configuration are currently not detected. -- Brian Ford Lead Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained crew... . -- 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: Cygwin/X on multiple displays, nothing displayed
On Tue, 29 Aug 2006, Justin Patrin wrote: > Does anyone have any clues how to fix this issue? -multiplemonitors ? -- Brian Ford Lead Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained crew... . -- 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: Xm/Xt auto-import linking issues
On Wed, 8 Feb 2006, Marc Vaillant wrote: > > > > > I'm trying to build xmbase-grok (http://www.bitrot.de/grok.html). It > > > > > successfully compiles but crashes when I click most buttons. > > > > > > > > Could you give the test version of lesstif a try and report back please? > > > > > > Thanks for your help Brian. I tried lesstif 0.94.4-1 and it's better > > > but still very buggy. In particular, it always crashes the second > > > time I access a menu. > > > > Steps to reproduce, please? I just built grok after much fuddling with > > errno and can not reproduce. I know nothing of how to use it, though. > > All menu options seem to work even with current released lesstif > > (0.92.94-2). > > The problems seem to be somewhat different depending on the lesstif > version. With 0.92.94-2, menu selection seems to be fine but buttons > are not: select the first database (biblio) under the Database menu. > Now click on any of the buttons labeled A-Z. This always produces a > crash for me. With 0.94.4-1, select the phone2 database under the > Database menu. Now try to select another database. You may have to > repeat once more to get a crash. Ok, I can reproduce this now. I haven't had much time to work on it yet, but my initial impression is that it is an upstream LessTif issue. Would you consider filing a bug with lesstif.sourceforge.net? If not, I'll try to follow up as time permits. LessTif is not very actively maintained anymore, though :-(. -- Brian Ford Lead Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained pilot... -- 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: Xm/Xt auto-import linking issues
On Tue, 7 Feb 2006, Marc Vaillant wrote: > > > I'm trying to build xmbase-grok (http://www.bitrot.de/grok.html). It > > > successfully compiles but crashes when I click most buttons. > > > > Could you give the test version of lesstif a try and report back please? > > Thanks for your help Brian. I tried lesstif 0.94.4-1 and it's better > but still very buggy. In particular, it always crashes the second > time I access a menu. Steps to reproduce, please? I just built grok after much fuddling with errno and can not reproduce. I know nothing of how to use it, though. All menu options seem to work even with current released lesstif (0.92.94-2). Volunteer Cygwin Lesstif maintainer... -- Brian Ford Lead Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained pilot... -- 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: Xm/Xt auto-import linking issues
On Sat, 4 Feb 2006, Marc Vaillant wrote: > Hello, > > I'm trying to build xmbase-grok (http://www.bitrot.de/grok.html). It > successfully compiles but crashes when I click most buttons. I'm > wondering if these problems might be related to the various Xm/Xt > auto-import linking messages that I receive, as shown below. No, those are informational only. > Archived messages suggest that X11 and/or binutils are not up to date. No, this is due to the current lesstif release not using the proper DLL import/export decorations in its headers, thus relying on binutils to do the right 'nix like thing. Could you give the test version of lesstif a try and report back please? I keep meaning to roll it into a current one but hadn't yet found the time. Volunteer Lesstif maintainer... -- Brian Ford Lead Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained pilot... -- 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: Consensus about man and doc X11 directory structure
On Mon, 10 Oct 2005, Dr. Volker Zell wrote: > I propose that documentation in general should go to /usr/share/doc/$PACKAGE > even for X11 packages and the main man page directory should be dictated > by the generic X11 tree, which is right now /usr/X11R6/man/manX (X=1,) > > Any comments ? Why do you propose keeping a distinct X11R6 tree yet puting documentation outside it. I would prefer these to be consistent. IIRC, Harold had decided to eliminate the X11R6 subtree and cgf agreed. I guess that was the direction Xorg and several Linux distros were taking. http://www.cygwin.com/ml/cygwin-apps/2004-01/msg00228.html IMHO, that was not desirable. Eventually I could imagine X11 and Cygwin native versions of the same package. I liked this method of making the distinction. > The situation right now is: [snip] > Docs pages not belonging to the x11-org packages: > = > > /usr/X11R6/doc: > > fvwm-2.4.7 > lesstif-0.93.94 > libPropList-0.10.1 > openbox-0.99.1 > transfig-3.2.4 <- empty > x2x-1.30 > Xaw3d-1.5D > xfig-3.2.4 > xgraph-12.1 > xpdf-0.91 I believe these are simply packages that have not been updated since the FHS standards began being enforced. > /usr/X11R6/share/doc: > > xorg-x11-xwin > freeglut-2.2.0 > gv-3.5.8 > libXft-2.1.6 > nedit-5.5 > tcm-2.20 > WindowMaker-0.90.0 > X-start-menu-icons-1.0.3 > X-startup-scripts-1.0.10 > x3270-3.2.20 > XmHTML-1.1.7 > xwinclip-1.2.0 These would appear correct from my point of view. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained pilot... -- 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/
lesstif update request
Harold, Any chance of a lesstif update in the near future? A lot of fixes have gone in in the last two years including several Windows specific ones. Thanks. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained pilot...
gtk2-x11.sh postinstall bug
Note to maintainer: Please quote $PATH when exporting to support spaces in path components. Thanks. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained pilot...
Re: Bug tracking services?
I hate to cross post like this, but I think it's appropriate for the question posed... On Wed, 27 Oct 2004, Christopher Faylor wrote: > I've set up the categories for cygwin: > > http://sourceware.org/bugzilla/describecomponents.cgi?product=cygwin Should the "Default Owner" be changed for Cygwin/X and setup.exe to Alex and Max respectively? Just curious... -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained pilot...
Re: xpdf: error messages
On Tue, 26 Oct 2004, Dr. Volker Zell wrote: > >>>>> Fergus Daly writes: > > Warning: XtRemoveGrab asked to remove a widget not on the list > > The message seems to come from cygXt-6.dll. Sorry but I have no idea > what's causing this. FWIW, xemacs shows the same phenomenon. > > Is there any X guru who can show a light on this ? It's a long standing issue in lesstif, but that's where my knowledge stops. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained pilot...
Re: Error message to start Cygwin/X
On Mon, 30 Aug 2004, Fabio Miranda wrote: > Sirs: > > I installed Cygwin in a computer running Windows 2000. In this computer > there are three account, administrator account and two users accounts. > When I start Cygwin/X from administrator account, everything works fine, > but if I try to start from one of users account, I receive the following > error message: > > Did you forget to paste in the error message? Did you try looking here? http://x.cygwin.com/docs/faq/cygwin-x-faq.html#errors > I would like to know what is wrong and what I shall do to correct this > problem. > > Regards, > > Fabio Miranda -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained pilot...
Re: window manager
On Wed, 16 Jun 2004, Chris W wrote: > Ok I guess I need to be more specific. I have a brand new install of > cygwin. I have been using cygwin for a while but this is my first try > with the Xwin x server. I just run the startxwin.bat file to start it. By default, that starts Xwin in "multiwindow" mode which uses the Windows window manager. > What I want is to be able to change colors and font sizes on the fly and AFAIK, font sizes are application specific and have nothing to do with the window manager. I'm not sure what you mean by colors. You mean like the Windows desktop themes? > some way of opening more windows or other x applications with a menu of > some kind. Is Start->All Programs->Cygwin-X not sufficient? You want a real X window manager instead of the Windows one? -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained pilot...
Re: window manager
On Wed, 16 Jun 2004, Chris W wrote: > Can someone tell me how to configure cygXWin to use a nicer window > manager than the default? You're going to have to do better than that. I assume cygXwin means the Xwin X server that comes with Cygwin so as to be on topic for this list. What does nicer mean? ie. What things are you missing that you want. What do you think the default is? ie. How are you starting Xwin? -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained pilot...
Re: matlab
On Tue, 15 Jun 2004, Rohan Shah wrote: > Does the linux version of matlab install and run on cygwin. Has anyone > tried this? Any pointers on how to install it? Any problems you might > have had? No. I think you had better read what Cygwin is again: Cygwin != Linux. I wish it didn't imply this so strongly on the cygwin.com home page. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained pilot...
Re: Re: Cygwin and X
On Mon, 14 Jun 2004, Erik Abrahamsson wrote: > Hi! I am not sure I am doing this right, I hope this is the right forum > now... Forgive me if it's not! Others have objected to my classification of your post. I still think this is a more appropriate forum since you are asking X related questions. But, it is bordering on off topic for this list as well since you are asking about third party software. > Also, top posting or not? What's "on" here? Bottom or inlined. > Personally I hate "bottom posting"...Sorry folks! I personally don't care about this style issue. > I choose not to include the previous post here. Is that OK? I already sent it here, so it shouldn't matter. What's with the tiny line wrapping though? > - I knew I would get a "the DISPLAY parameter isn't right and you need > to specify the problem"-reply... I've been around in other forums, so I > know the drill... :-p Ok, so why didn't you :-p? > 1. Yes, I have read about the DISPLAY parameter. Unfortunately I looked > everywhere for one. Where is it and how do I set it to 0, or any other > value that might be correct? It's an environment variable. Look at a basic X FAQ since this is not Cygwin related. Try: export DISPLAY=locahost:0.0 > 2. The problem is that Cygwin can't find the X-server. Ok, what does that mean? > I don't get any error messages. Starting Cygwin with or without a > x-server (not Cygwin/X) running results in just the same thing. Which is? > Running Cygwin/X works fine, Which means? > apart from an 100% CPU usage, as described in in the FAQ. Running > Cygwin/X *and* another x-server, such as Exceed, causes problems, such > as dissaparing cursors and the like. Ah..., now were at least getting a little bit of information. > I'm sorry, I can't describe it better than that. Then, I can't help more than this. You haven't even stated what applications you are having problems with. > 3. Of course, since that the problem is caused by a firewall (as > described in the FAQ) I could disable that. But, as I am sitting on an > unprotected university network, it takes about 30 seconds for my XP > machine to be hacked. Do not think I have not tried that one already. > And it's not funny! Can't you disable it for connections to localhost? > If this isn't a common problem with a simple solution, I don't think > I'll manage to fix it. I don't know enough about the stuff to write my > own config files and things. We have no idea since you have done very little to describe the problem. > Thank you, again, for any help I can get. Try reading http://cygwin.com/problems.html again. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained pilot...
Re: Cygwin and X
Since this is Cygwin/X related, you have chosen the wrong list to post to. Please read http://cygwin.com/lists.html for more information. I have redirected this thread to the cygwin-xfree list. On Mon, 14 Jun 2004, Erik Abrahamsson wrote: > Hi all! > I have been running Cygwin/X for some time, with very low performance. > In the Cygwin/X FAQ this is explained by the fact that I have a personal > firewall (in this case it's Zonealarm). It is also the process vsmon.exe > that is draining my system while using Cygwin/X. The solution to this > problem would be do disable the firewall, which is not an option on > Win2000 or XP... Why is this not an option on Win2k or XP? > Previously I used F-Secure with Himmingbird Exceed as X-server, without > any problems. > > So my question is: Is it possible to run Cygwin with the X-server of > your choice, which in my case is Exceed? What do I need to do? Yes, and nothing but set your DISPLAY variable correctly. You would get much more informative responses if you actually describe a particular problem you have when trying to do this. Also, see http://cygwin.com/problems.html. > I am quite familiar with win, but not *nix. > > Thank you for any help I can get! > > /Erik -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained pilot...
Re: Combination of Windows based GUI and Cygwin.
On Thu, 27 May 2004, kirat shah wrote: > Hi all, > > I need suggestion about following topic. > I have Fortran90 codes which is working fine in > cygwin-X. What i need to do is i want to connect those > codes with windows based GUI. What GUI does is just > creating INPUT file. I want INPUT file to use in > cygwin in background(users dont know about cygwin) and > give output files. My problem is how to make cygwin > run in background from GUI, is it possible?. Cygwin doesn't "run in background". Cygwin is a DLL that you link to applications. If your Windows GUI just creates an input file, why can't your Cygwin program read that file? > If it is then what is the best way to do it. I think you need to explain what you want in much greater detail. It is unclear to me that Cygwin/X is even involved in the question. > Cygwin-X is necessary because results are in form of some plots which > needs to be plotted in gnuplot or can be view in gs/gv combination. Ok, but how does that relate to making your Windows GUI interact with your Cygwin Fortran code via an input file? I'm lost. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained pilot...
Re: XWin on Larger Secondary Monitor?
On Thu, 27 May 2004, Sean O'Boyle wrote: > Hello, > > I'm running a weird configuration and would like to see if anyone has this > working. > > I have a laptop with a secondary monitor. The primary (laptop screen) is > 1400 x 1050. The secondary monitor is a larger 1600 x 1200. > > I'd like to launch xwin on the secondary monitor such that the root window > fills the screen. Can anyone tell me how to do this? The closest that I > could get was to run in -multimonitor mode - but that filled both of my > screens with a giant root window. > > Currently I'm settling with running XWin on the primary monitor and moving > it to the secondary. So it fills *most* of the screen... You could temporarilly make the secondary monitor the primary one via the control pannel. Why not just use -multiwindow -multiplemonitors, though? You might also try using "-screen screen_number width height" -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained pilot...
Re: C-shell:commands are not working
On Thu, 27 May 2004, kirat shah wrote: > Some serious problem is going on here, in my C-shell > application all things are fine Great, no problem! Then why are you posting again? > previously i can use all commands like ls , gv .. all. But suddenly i am > not able to do that. Ah yes. What does that mean? > What should i have to do to solve this, plese help me. Start here: http://cygwin.com/lists.html to find out which list is the correct one to address your problem. This is the Cygwin/X list. Since your problem is not Cygwin/X related, it is off topic for this list. As such, I have redirected further replies to the correct list (the main Cygwin list). But, before you post there, please read: http://cygwin.com/problems.html It will tell you how to properly format a problem report so that we don't have to use our psychic abilities and guess what's wrong. It will also inform you about the required attachment that tells us about your particular installation. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained pilot...
Re: Problems to patch files.
This does not appear to be Cygwin/X related. As such, it is off topic for this mailing list. Please review the list descriptions here: http://cygwin.com/lists.html and repost to the correct list. I redirected this reply and further posts to the main cygwin list since that appears to be correct given this limited information. Also, this problem report makes little to no sense. Please consult the problem reporting guidelines available here: http://cygwin.com/problems.html for how to submit a useful problem report. Please pay special attention to the part about *attaching* the required cygcheck output. More replies inline below. On Thu, 20 May 2004, Marcus Vinicius M.Fernandes wrote: > Hello > > I am can't compile any programm outside of /usr/local/bin/ In the subject you say you are having problems patching files, but here you say you can't compile any programs outside of /usr/local/bin. Which is it? What are you trying to patch and why? What exact command did you use to do so? What did you expect to happen and what did happen? What does can't compile mean? What does outside of /usr/local/bin mean? > It does compile but the executable doesn't work. Ok, now you can compile, but you can't run the program? What about it doesn't work? > I already put the path to my directory What is your directory? > in the .bashrc file, Exactly how? > but it didn't work. What didn't work? > I don't know what to do? Neither do I as I can't even understand your question. > Could you help me? Maybe, if you supply a lot more information. I understand there may be a language barrier here, but we really do need more detail and a clearer problem description to help. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained pilot...
Re: Kerio PF warning windows when using X
Wrong list. This is a Cygwin/X related issue. Please see: http://cygwin.com/lists.html for details. Redirecting... Also see: http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-cannot-open-display especially the Note. On Tue, 18 May 2004, Romain Michard wrote: > Hi, I've tried the new X.org and when I use graphic apps (xterm, xcalc, > xfig, xemacs, etc...) my firewall (Kerio personnal firewall) keeps > alerting me (even if I check the box telling it I want a rule for that > alert) that Kerio Virtual Private Network try to connect to localhost > port 4090. Here are the details : > > [18/5/2004 19:46:20] > > Direction: sortant > Point local: 0.0.0.0, port 4092 > Matériel: N/A > Point distant: localhost [127.0.0.1], port 4090 > Protocole: TCP > > Fichier: KVPN > Description: Kerio Virtual Private Network > Version: (null) > Créé le: N/A > Modifié le: N/A > Accédé le: N/A > > RuleId = 402653209 > > I don't know what is the problem. > > Thanks for helping, > > Romain -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained pilot...
Re: '"GLX" missing on display' Problems
Wrong list: http://cygwin.com/lists.html This is a Cygwin/X specific question. Redirecting... On Wed, 28 Apr 2004, eti1 wrote: > I use cygwin from home (on a Windows box) to ssh into my machine at work > (Linux box). I get the following error when I try to run programs that use > opengl libs for displaying: > > [EMAIL PROTECTED] cubit90]$ glxgears > Xlib: extension "GLX" missing on display "localhost:10.0". > Error: couldn't get an RGB, Double-buffered visual > > When I ssh, I use the -X option so that graphics get forwarded to my local > machine. I am aware that this error is usually manifested because opengl > libs are not installed on the local machine, but I know I have them on my > local machine because if I go a 'glxgears' before ssh-ing the gears > graphics window displays just fine. It appears that after ssh-ing into my > work machine, display information is lost. > > What is very troubling with this problem is that sometimes the problem > altogether disappears. For example, if I ssh into my work machine and let > the terminal sit for a while, it sometimes works, sometimes not. Other > times after ssh-ing in, if I edit a file with "vim" I can run glxgears > after, but not always. Nothing is reproducable to get it to work. But > once it starts displaying, it usually doesn't stop. I tried a complete > uninstall/reinstall of cygwin but it didn't do anything. > > Help! > --Corey Please also see: > Problem reports: http://cygwin.com/problems.html We need more information to help you. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained pilot...
Re: I miss files and openssl doesnt want to install
This is not related to Cygwin/X. As such, I have redirected futher discussion to the main Cygwin mailing list. Please consult http://cygwin.com/lists.html before posting again. Also, please consult http://cygwin.com/problems.html for the required way to submit a useful problem report. Finally, please search the mailing list archives before posting. Often, you question has already been asked and answered. Note: Using google as your search engine with a "site:cygwin.com" keyword will often produce better results than the search engine provided at cygwin.com. On Thu, 8 Apr 2004, Inqu wrote: > Where can I find the rxvt-thingie? To answer question like this in general, please consult the package search facility available at http://cygwin.com/packages. I also suggest you read http://cygwin.com/faq/faq_toc.html#TOC13 and the following entry since it seems you did not understand what they have to say. > Today I dloaded openssl 0.9.7d, located the compiler and perl from > internet and installed it. > The install went ok but the openssl doesnt work (or I cant find it). [snip] > Is the ssl installed now or not and how can I find it? No, it is not. Again, consulting the package search facility mentioned above will solve your problem. > I'm using "mingw" compiler, and winxp. If you're using the mingw compiler, then this question is off topic even for the main Cygwin list. Please consult mingw-users at lists.sourceforge.net. HTH -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: lesstif 0.93.94 and the "attempt to add non-widget ..." error
Sorry I can't be more helpful than this right now. LtXmFixupVendorShell is not working. Find out why. On Mon, 29 Mar 2004, Volker Quetschke wrote: > In order to burn a few minutes and debug a grace (lesstif) problem > (See thread "Grace (xmgrace) 5.1.12-1 graph program -- ...") I > rebuild lesstif-0.93.94-1. > > A few patches were needed to use the build script, see the > attached patch. (It also contains a slight modification to > use autoreconf, proposed by Brian Ford) > > BUT it didn't help. When I build grace with lesstif-0.93.94 > (selfbuild or the testversion installed with setup) and > start xmgrace I get this: > > --- snip --- > $ grace-5.1.14/src/xmgrace.exe > Warning: XmManager ClassInitialize: XmeTraitSet failed > > Error: attempt to add non-widget child "DropSiteManager" to parent > "xmgrace" which supports only widgets > --- snip --- > > Using the same xmgrace.exe but downgrading to lesstif 0.93.91-6 > I can start grace. !? > > The lesstif faq <http://www.lesstif.org/FAQ.html#QU3.0> claims that > this error stems from using the wrong order of linker flags, but I > guess that 0.93.94 fails and 0.93.91 works contradicts this. > > The linker flags are: "../Xbae/Xbae/libXbae.a -lXm -lXpm -lXp -lXmu > -lXt -lXext -lX11 -lSM -lICE ../cephes/libcephes.a > ../T1lib/libt1.a -ltiff -ljpeg -lpng -lz -lm" (from the actual build) > > Any ideas? > > Volker > > -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
auto-import failure for new libXt
I guess this is just a heads up since I don't have time to debug it right now, but with the latest XFree packages, I get a stream of error messages like the following when linking our apps: /home/ford/v9winsym/util/Failure_report/../../../vissym/util/Failure_report/failure_report.c:104: variable '_XtStrings' can't be auto-imported. Please read the documentation for ld's --enable-auto-import for details. failure_report.o(.text+0x203f): In function `main': This used to work, all be it with similar warnings. Is it time to make a pass through the X headers, adding the proper export tags? Ugh... -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: Fontpath and IPC problems when switching from XWin-44 to 54 under latest cygwin
On Fri, 12 Mar 2004, Dr. Volker Zell wrote: > Hi all > > Because lack of time I tried switching from XWin-44 to XWin-54 today and > got the following errors in my XWin.log which were not present in > XWin-44 (see logfile below), 2 font paths could not be initialized and > IPC support was disabled although cygip2 was running (as can be seen in > the log file from XWin-44) > > I also had the XWin versions 47 and 49 handy, so I'm attaching also the > their logfiles. As can be seen IPC support is not recognized anymore in > 47 and the path initialization problems show up in 49. > > Any hints, cause I really need IPC support and don't want to sty behind > with my XWin version. > Just the obvious one here: http://cygwin.com/ml/cygwin-announce/2004-02/msg8.html IIRC, XWin has not been updated to use cygserver, or updated to use the new cygipc layout. So, it's probably a broken mix at the moment. I'll try to provide a patch to transition to cygserver later, time permitting. It should be fairly easy for anyone to try, though. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: Some help with [re-]installation please
Since none of this is really specific to Cygwin/X, I've redirected this thread to the main cygwin list. I'll take a stab at a few of these, but there are parts I am not sure of either. On Wed, 10 Mar 2004, Chris Green wrote: > I had a disk disaster over the week-end, a disk 'optimiser' made my > 160Gb main drive very optimal by wiping it completely. I was fairly > well backed up etc. but it takes a while to get everything back to > normality. > Yep. My 160Gb main drive in a brand new Dell box died in less than a month. I had just got the box up and configured, but I had no backups yet :(. So, I sympathsize. > I found re-installing cygwin and cygwin/X a bit confusing so would > appreciate some comments and help. > > I had all the ftp'ed files left from installing cygwin previously > sitting in a directory on a networded drive, could I have used these > to re-install cygwin rather than downloading everything again? If so, > how does one do it? > Yes. Choose "Install from Local Directory" instead of "Install from Internet", and point setup there. Keep in mind, however, you would have missed out on all the new and exciting updates :). > There are a number of different directories, one for each FTP site I've > used. > This is the part I am not sure how to handle. > As it was I chose an FTP site (the last one I had used I think) and > re-downloaded from there, or did I? If I accept defaults does it just > download only the files which have been updated and install the rest > from the previously downloaded files on disk. > I think it uses the "Local Package Directory" that it prompted you for as a cache. So, I think the answer is yes. > I really find the window where you select what to download, etc. > *very* confusing, some of the wording is very odd. Two examples from > the User's Guide which I find difficult to understand are:- > > You can change setup.exe's view style, which is helpful if you know > the name of a package you want to install but not which category it is > in. Click on the View button and it will rotate between Category (the > default), Full (all packages), and Partial (only packages to be > upgraded). If you are familiar with Unix, you will probably want to at > east glance through the Full listing for your favorite tools. > > So what does 'Partial' mean? I can see that Category means all > packages sorted into types, Full means all in alphabetical order but > what does Partial mean? Does it mean only display packages that I've > got already? > I found it confusing at first too :). No, it is more of a view of what is to come ie. the packages that you or it have selected to upgrade/install. Does that help? > ... and the second (and more confusing for me) bit is:- > > Once you have an existing Cygwin installation, the setup.exe chooser > is also used to manage your Cygwin installation. Information on > installed packages is kept in the /etc/setup/ directory of your Cygwin > installation; if setup.exe cannot find this directory it will act just > like you had no Cygwin installation. If setup.exe finds a newer > version of an installed package available, it will automatically mark > it to be upgraded. To Uninstall, Reinstall, or get the Source for an > existing package, click on Keep to toggle it. Also, to avoid the need > to reboot after upgrading, make sure to close all Cygwin windows and > stop all Cygwin processes before setup.exe begins to install the > upgraded package. > > What on earth does "To Uninstall, Reinstall, or get the Source for an > existing package, click on Keep to toggle it.", mean??? > Did you try it? Clicking on Keep transitions it to Uninstall, Reinstall, Source, etc. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: Cygwin Openbox queries
On Mon, 1 Mar 2004, Jophrey Lim wrote: > I am trying to start the X server with Cygwin/X running in Rootless mode > with the /openbox/ window manager running locally (one of the screenshots). > Please show us the exact command you used to do this. > However, I have no idea on how to do it. I tried running "openbox" but I > got this error saying Connection to X server failed. I had checked the > online user guide and searched the internet for any guide but failed. > What does echo $DISPLAY say? > Do you have any script on how to start the X server with openbox window > manager? Any website that I can refer to? > /usr/X11R6/bin/Xwin.exe :0 -rootless& /usr/X11R6/bin/openbox -display :0 WFM. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: [Fwd: [Bug 217] New: Menu bar in window is not clickable - Cygwin - XWin]
On Wed, 25 Feb 2004, Harold L Hunt II wrote: > Does anyone have an environment to test the reproducibility of this bug > report? I would appreciate any help in debugging it. > WFM with current packages. Differing details follow. > Version: unspecified > That was helpful! > When I use Cygwin/XWin as my X Server on a: > Windows XP Professional > Version 2002 Service Pack 1 > NVidia Quadro2 MXR/EX > ATI 9800XT > Driver Version: 4.3.5.1 > Catalyst 4.2 > and run > Purify: > Version 2001a.04.00 Solaris 2 > Version 2002a.06.00 Solaris 2 > on a: > Machine hardware: sun4u > OS version: 5.7 > OS version: 5.8 > Processor type: sparc > Processor type: sparcv9 > Hardware: SUNW,Ultra-4 > Hardware: SUNW,UltraAX-MP > I can not click on any of the menus: File, View, Actions, Options, Help. > The buttons on the toolbar work and the window contents itself is > clickable as well. > > The X Server is started with the following command: > start XWin -multiwindow -clipboard > HTH. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: xfree and windows XP home version
On Sat, 31 Jan 2004, Robert Tramel wrote: > Hi > > Hopefully per Brian Ford's suggestions this will be more helpful > > This time I've attached the requested cygcheck.out file. > Thank you. It shows you are running the 1.5.6 version of the Cygwin DLL (cygwin1.dll). Don't. It was a fairly broken release. Please upgrade to 1.5.7. It was released on the same day you sent this email. > The problem is that under I open a bash shell, and then cd into the > /usr/X11R6/bin directory. > Under what? > I have tried using both the startx as well as the startxwin.bat commands. > > when I run startxwin.bat I get the following message > > startxwin.bat - Starting on Windows NT/2000/XP/2003. I see the X symbol > appear at the bottom left corner of the display but that is it no > xwindow pops up. I have tried the alt-tab combo and the X window never > appears as an option. > The default script should pop up an xterm in a standard Windows style application window. Have you edited this script? > With startx the situation is slightly better in that an full screen > seized X window appears but the system never clears the windows > icons/background etc. out of the X window. Also the hourglass never goes > away. I can toggle between applications using alt-tab sequence but > nothing ever changes in the X window. > Do you have a .xinitrc or .xserverrc script. If so, what are the contents? > In both cases the X application does not respond to the system when I > attempt to shut down/restart the system. > Please try to upgrade your installation, and then report if you have more problems. Thanks. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: Notes on adding accelerated OpenGL support to Cygwin/X
On Fri, 30 Jan 2004, Alan Hourihane wrote: > One note Harold on this > > You'll find that a lot of OpenGL drivers that are used on Windows are > seriously lagging behind in support for the hardware. That's because > a lot of vendors don't bother updating support for OpenGL directly > and are more interested in Direct3D. > That is probably because Microsoft does the same. They only ship/support OpenGL 1.1. Everything else is an extension that needs to be loaded manually via GetProcAddress. > Just run a native 'glinfo' application and you'll see that ATI and nVidia > are pretty good in this area and provide very up-to-date OpenGL drivers. > But others aren't so great. > But, you still have to jump through the GetProcAddress hoops to get there, even with ATI and nVidia because of the base layer that Microsoft provides. > Apparently SciTech (Kendall Bennett) donated some code (a driver) for Mesa > that allows it to accept the OpenGL commands from the client and call > the equivalent Direct3D counterparts thus providing hardware that has > a more capable Direct3D layer much more benefit. > > I think Karl Schultz on the Mesa list has the code and is integrating it, > but I don't know the status. You may want to contact him. > > You won't need this to get started though, but it's certainly worth > investigating once you've got an initial implementation. > This would be a good option to have, but I wouldn't make it exclusive. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: Notes on adding accelerated OpenGL support to Cygwin/X
On Thu, 29 Jan 2004, Harold L Hunt II wrote: > I just spoke with Torrey Lyons regarding OpenGL acceleration in Xdarwin. > He enlightened me on several points: > > 1) Most of the code that I described in my first email is for the > "direct" rendering path. That path allows X Clients on the same machine > as the X Server to avoid calling through the X Server and instead of the > GLX lib draw directly to OpenGL. > I'd say you covered both. And, at least *I* was aware of both paths. > 2) There is another path called the "indirect" rendering path. This > path is used by all remote clients that use OpenGL as well as by local > clients if the "direct" rendering path is not provided. Thus, the > "indirect" path must always be provided. > True. > 3) The "direct" path is not needed until later and the "indirect" path > is much, much simpler. > That may be open for debate, I guess. The last time I checked, the Linux DRI project implemented the direct path first, and let software Mesa handle the indirect path. In fact, it may still be that way. For them, that was more important, and certainly more optimal. For most Xwin users, however, I understand why the indirect path might be more important. > Implementing the "indirect" path: > > 1) See xc/programs/Xserver/GL/apple/indirect.c > > 2) indirect.c should be simple to duplicate and will give all of the > functionality needed for indirect acceleration. This will still provide > a tremendous boost in performance for OpenGL apps, as well as a decrease > in CPU usage. > > 3) The only tricky bit is that we need to take a WindowPtr in indirect.c > and translate it into either the HWND for the corresponding Win32 > window, or we need to translate it directly into a handle/pointer to the > OpenGL surface associated with that window. > I'm still trying to look at this, but I may not get to it until next week. I have done all the trivial stuff like copying the apple files to a windows directory, modifying the Imakefiles, etc. > I actually already have most of the "direct" path code compiling, but I > will be shelving that for the moment until we implement the "indirect" > path. Please, work on the "indirect" path first if you are interested > in this. > That's great! I wouldn't shelve it, though. It should be possible to roll out the direct stuff independently from the indirect stuff like DRI Linux did (still using Mesa for indirect). > Thanks for contributing, > I'll try :-). -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: xfree and windows XP home version
On Thu, 29 Jan 2004, Robert Tramel wrote: > I down loaded the Cygwin/X package to a machine running windows XP home > edition. > Howver the X windows never fire up properly, i..e., they don't do > anyting at all are freeze imediately depending on which startup option I > try. Is this a limitation of XP home or am I missing something? > AFAIK, there are no known issues with XP home. As such, I suggest you do the following three things so we can help you better. 1.) Please visit http://cygwin.com/problems.html and review the problem reporting guide lines. Specifically, review the part about *attaching uncompressed* cygcheck output. That will allow us to see all the relevent versions of your software, and if they are properly installed. 2.) Please give more detail about exactly how you do both "start options". Then, we have the information necessary to try and reproduce your problem, or see if you are starting Xwin incorrectly. 3.) Please describe in more detail what "freeze imediately" and "don't do anything at all" means ie. what did you expect to happen, and what did happen. Thanks. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: Notes on adding accelerated OpenGL support to Cygwin/X
On Thu, 29 Jan 2004, Harold L Hunt II wrote: > I am interested in adding this support as well, but I think it would be > nice if some users and/or developers out there would help get this > started by creating some of the boilerplate files for me and ensuring > that these initial files compile correctly (although they will not do > anything and might not link correctly). > I don't want to discourage anyone, but this is to let you know I am trying to work this in "my spare time" :-). > I have put together a one page set of notes on the files that we need to > adapt to our platform and the minor changes to the build system that we > need to make to get those files to build: > > http://msu.edu/~huntharo/xwin/devel/server/CygwinX-Accelerated-OpenGL-Support-20040128.pdf > (44 KiB) > Thanks for the notes. I have looked at this on and off for a year or two but always got lost quickly. > These notes apply to the CYGWIN tag on the xorg repository that lives at > freedesktop.org. See the XWin Server development page for information > on how to check out a tree: > > http://x.cygwin.com/devel/server/ > Just built it for the first time :-). -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: Installation question
On Tue, 27 Jan 2004, Rick Daihl wrote: > Rather than installing CYGwin and CYGwin/X locally on each machine, can I run > from a common network drive?In this scenario I would have > several machines running from this drive.I've already tried this and ran > into /tmp/XWin.log file not being unique.I know I'll pay a heavy > price for hitting the network (that might be an uderstatement). We are > replacing Exceed with this package. Most of our desktops don't have > enough free space to load the two packages and have anything leftover. > http://www.cygwin.com/ml/cygwin-xfree/2001-q3/msg00997.html http://sources.redhat.com/ml/cygwin-xfree/2002-07/msg00165.html http://www.google.com/search?q=shared%20network%20install%20site%3Acygwin.com etc. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: ddd broken on CYGWIN 1.5.6
On Wed, 21 Jan 2004, Dirk Fassbender wrote: > i have a problem with the start of ddd after upgrade to CYGWIN 1.5.6 > and LATEST snapshot. > > See below : > > [EMAIL PROTECTED] ~ > $ ddd > gdb: access /dev/tty1: No such file or directory > gdb: cannot open master pty: No such file or directory > gdb: communication setup failed > In case you did not see it, this problem is now confirmed to be fixed in the latest snapshot. http://www.cygwin.com/ml/cygwin/2004-01/msg01036.html HTH -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
RE: Startx on WinXP
On Wed, 21 Jan 2004, Brian L. Walter wrote: > the *solution* was a cheat. I commented out the references in startx to > $HOME. Since I don't have specific configurations, this is an acceptable > white lie. > Why not try startxwin.bat and the "nifty" multiwindow mode (ie. Windows is the window manager)? > The version of lesstif is 0.93.91-6. Interestingly enough, it's -2 on the > win98 machine, on which mwm *does* work. I might try downgrading to -2 > (from the install packages on the win98 machine). > WFM. -2 was a broken attempt at an Xm DLL. It just so happened that mwm was still linked to the static Xm in that package. In general, it was broken, so don't revert please. You might post strace mwm | grep Mwm 2>&1 to see if it is an app-default issue. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
RE: non-widget child "DropSiteManager" error (WAS: RE: Grace (xmgrace) 5.1.12-1 ... )
On Wed, 21 Jan 2004, Brian Ford wrote:
> I have my new machine set up now, so I'll try to take a stab at compiling
> it myself today. I'll let you know how I make out. Thanks for being
> patient.
>
It compiled for me (including DLLs) almost out of the box. I did make the
following change to lesstif-0.93.91-6.sh. I am not sure that the change
was required, because I did not try without it. But, it "felt" like a
better idea to me :^D.
In the prep rule, remove all the autotool stuff between:
touch INSTALL && \
and
rm -f INSTALL )
replacing it simply with:
autoreconf --install --force && \
so it reads:
prep() {
(cd ${topdir} && \
tar xv${opt_decomp}f ${src_orig_pkg} ; \
cd ${topdir} && \
patch -p0 < ${src_patch}
&& mkdirs ) && \
(cd ${srcdir} && \
touch INSTALL && \
autoreconf --install --force && \
rm -f INSTALL )
}
To do a debug build, just look at the target all:
all) prep && conf && build && install && \
strip && pkg && spkg && finish ; \
STATUS=$? ;;
and do everything but the strip step.
Let me know if this doesn't work for you.
--
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax: 314-551-8444
RE: non-widget child "DropSiteManager" error (WAS: RE: Grace (xmgrace) 5.1.12-1 ... )
On Wed, 21 Jan 2004, Atwood, Robert C wrote: > Brian Ford wrote: > >Robert C Atwood wrote: > >> Is this documented somewhere? > >> > >What does *this* mean :^D? > > > :-C > *fulmination removed* > > Umm ... is there a place where it says 'Here is how you build a Cygwin > package from the source archive distributed via Cygwin setup. 1. Unpack > the archive 2. There will be a script called .sh 3. > Run this script with (one of) the followign arguments: prep , build, > all, (etc.) 4. Here is what each of the arguments do. ... 5. this > produces an archive, unpack this as follows 6. anything else. > Sorry. If you look at the context from your previous message, it really was not clear whether this refered to --[enable|disable]-[static|shared], how to build a DLL with libtool, etc. In fact, the this you explained above was not even on my guess list :). Is think this is the closest this to what you are looking for: http://cygwin.com/setup.html#package_contents Look under "Method 2". > Also I believe the following addition to the script would probably save > some people (like me) much headache ... suitably filled in where blank, > I don't quite get what all the different options are for. > I agree. PTC. Please send them to cygwin-apps at cygwin dot com. Although, don't get your hopes up. There has been another very useful patch to this script pending for a long time now, and it is not clear why it has not been accepted. I'm not sure who is in charge of the generic build script. Maybe that is the problem. [snip] I have my new machine set up now, so I'll try to take a stab at compiling it myself today. I'll let you know how I make out. Thanks for being patient. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
RE: non-widget child "DropSiteManager" error (WAS: RE: Grace (xmgrace) 5.1.12-1 ... )
On Tue, 20 Jan 2004, Atwood, Robert C wrote: > As far as I can tell, it not only build static .a library files, but did > not create any shared .dll files. Is there another step needed to do > this? I will try to comprehend some parts of the script and see if I can > figure how to create the dll's or why I did not get them in the first > place. > Did you make sure that this step from Harold's lesstif announcement worked? 2) Make the build script run aclocal, autoconf, and automake, and make the mkpatch step exclude files generated by these programs. This makes the package patch readable and useful. I think you might need to include libtool in that list. Make sure all of the afore mentioned tools are up to date, and then try: autoreconf --install --force > At first I tried buildign the lesstif by manually runing ./configure and > make but this did not work. > Probably due to the above. > This is a list all the files called Xm that got installed : > $find . -name '*Xm\.*' > ./lib/libXm.la > ./lib/libXm.a > ./include/Xm/Xm.h > Thanks again > Robert > Yeah, there should definately be more. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
RE: non-widget child "DropSiteManager" error (WAS: RE: Grace (xmgrace) 5.1.12-1 ... )
On Tue, 20 Jan 2004, Atwood, Robert C wrote: > >I believe this is a static lesstif lib. And, AFAIK, a static lesstif > lib will not work now that Xt is a DLL. I don't know why > >it is still in the package. I would think that lesstif-0.93.91-6.sh > should be passing --disable-static to configure and that > >would keep this from being built/installed. > > It has both --enable-static and --enable-shared in there, does one > override the other? I do not get the dll. > No. They are supposed to be independent. > I am trying again with the --enable-static removed ; or do you actually > have to specify --disable-static? > It depends on how this package is defaulted. I don't remember and am still in the process of migrating to a new PC, so I don't have easy access to the source. That is also the reason for all the vague replies. > Is this documented somewhere? > What does *this* mean :^D? > However, I don't see why one library can't be static and the other > shared, doesn't it just look for the needed symbol at run-time? -- I > am willing to take your word for it though. > No. Windows requires all symbols to be defined at link time. Xt/Xm/Xaw3d all depend on more *nix like behavior and expect to override symbols at run time. The hack used to fix this hooks into DLL initialization. Thus, no static lib support. There are probably other reasons as well. Search the achives for VendorShell if you want more detail. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
RE: non-widget child "DropSiteManager" error (WAS: RE: Grace (xmgrace) 5.1.12-1 ... )
On Tue, 20 Jan 2004, Atwood, Robert C wrote: > What I did: Building lesstif -- just using the provided script (for now, > without even trying debugging) > Sorry this is my first exposure to the cygwin building scripts, I am not > sure what it did with my config.log, but it is the script included in > 0.93.91-6, using .sh all > The whole build is done in .build. > Installing lesstif -- untarred the resulting archive into > the / location > > Configuring grace -- grace-5.1.12-1.sh prep > export X_EXTRA_LIBS="-lXft -lfontconfig > -lXrender" > cd grace-5.1.12 > ./configure > --with-motif-library-/usr/X11R6/lib/libXm.a [--enable-debug] (tried > with/without) > I believe this is a static lesstif lib. And, AFAIK, a static lesstif lib will not work now that Xt is a DLL. I don't know why it is still in the package. I would think that lesstif-0.93.91-6.sh should be passing --disable-static to configure and that would keep this from being built/installed. Do not use that lib. Move it out of the way. You should be linking with libXm.dll.a, although -lXm should just do that. > make > make tests > > The errors occurred here. I tried some other ways of getting the > librarys included (before I settled on this way) with identical results. > With the lesstif installed from the binary package via setup, the tests > work (but crash, as mentioned, with a seg fault if an axis dialog is > opened) In this case no graphs open, only the error message (non-widget > etc.) in the parent terminal window. > That is because you are linking with the broken static lib. > I am not sure why X_EXTRA_LIBS were needed when they were not needed > when I compiled grace using the lesstif that was installed from the > binary package. This was very confusing. As far as I can tell, these > libraries are not part of lesstif,(are they?) > Libtool may have taken care of this for you, although I don't know why it isn't now. Look in libXm.la. See the following reference for some details: http://sources.redhat.com/ml/cygwin-xfree/2003-10/msg00401.html > Final linking line: > > gcc -O2 -mcpu=pentiumpro -fno-common -Wall -pedantic -Wpointer-arith > -Wnested-externs -I.. -I. -I../T1lib/t1lib -I../Xbae > -I/usr/X11R6/include main.o plotone.o files.o ssdata.o utils.o > drawticks.o nonlfit.o lmdif.o as274c.o fit.o fourier.o graphs.o > graphutils.o setutils.o regionutils.o objutils.o computils.o defaults.o > params.o draw.o dlmodule.o pars.o missing.o iofilters.o dates.o > t1fonts.o device.o dummydrv.o mfdrv.o mifdrv.o psdrv.o pdfdrv.o svgdrv.o > gd.o rstdrv.o mathstuff.o Tab.o motifutils.o compwin.o comwin.o > eblockwin.o editpwin.o events.o featext.o fileswin.o plotwin.o > graphappwin.o helpwin.o hotwin.o locatewin.o miscwin.o monwin.o > nonlwin.o printwin.o ptswin.o regionwin.o setwin.o strwin.o setappwin.o > tickwin.o worldwin.o fontwin.o xutil.o x11drv.o xmgrace.o -o xmgrace.exe > -L/usr/X11R6/lib ../Xbae/Xbae/libXbae.a /usr/X11R6/lib/libXm.a -lXpm > Yep. Don't use that one. > -lXp -lXmu -lXt -lXext -lX11 -lSM -lICE -lXft -lfontconfig -lXrender > ../cephes/libcephes.a ../T1lib/libt1.a -ltiff -ljpeg -lpng -lz -lm > You will still need the debug build to find the dialog problem. Look in the .sh script to figure out how to do one manually. It isn't that hard to dig through. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
RE: non-widget child "DropSiteManager" error (WAS: RE: Grace (xmgrace) 5.1.12-1 ... )
On Tue, 20 Jan 2004, Atwood, Robert C wrote: > Dear Brian and other list people: > > Why am I trying to build it myself? > > Because the distributed package (0-93-91-5) seems to cause another > problem, even the version that Harold Hunt patched (0.93.91-6) using > Danny Backx's fix for the bug I encounterd a few months ago, and have no > idea why it still crashes. I cannot find out in any more detail unless I > run with a debug-compiled version. > > Please see the archived thread on 'Grace (xmgrace) 5.1.12-1 ... ' for > much greater detail on this (including backtraces, etc) > Ok. I'm way behind on my list traffic because of the flu, holidays, and a funeral. I have briefly scanned the thread you refer to now. > Is there another way to get a debug-compiled version other than building > it myself? > Not that I know of. > Harold's test-version of 0.93.94 seems to have this problem (non-widget > etc.) (if it really is from lesstif) and he says it causes problems with > nedit as well, so it is not a true release. But I am building a > 0.93.91-6 without changes (at first) just to find out exactly where the > crash is coming from, but get this (different) problem. > It is from lesstif. Could you post your exact link line? I haven't had time to try the test version yet. > I certainly realize that a 'properly built' lesstif is what I want, in > what way is my version not 'properly built'? That is essentially what I > was asking in the first place! However I followed Harold's directions > exactly without trying to patch it or even debug it (at first) and I > have this problem. > > How do I distinguish whether it is not 'properly built' or not 'properly > updated'? Which is the problem? > I don't know. Properly linked might also be the problem, hence the request above. What did you pass to configure? Did you try putting the extra freetype libs in LIBS? > Can you provide details on what constitutes a 'properly updated' > lesstif? I got the source from 0.93.91-6 (one line different from > 0.93.91-5) > That should be fine. > Can you build xmgrace from source and then get the axis properties > dialog box (double click an axis) to open without crashing? (Note the > release 5-1-12-1 package binaries are compiled with STATIC libraries > from an earlier version of lesstif and do not crash.) > Maybe, but it'll be a while. > > Update: by adding absolute paths to the missing libraries, I can get > > it to compile,but now I get > > This is probably bad. By "the libraries", you mean the dll's, or the import libs? You want the latter, I believe. Sorry to be so sparse with the reply. I'm really backed up right now. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: non-widget child "DropSiteManager" error (WAS: RE: Grace (xmgrace) 5.1.12-1 ... )
On Mon, 19 Jan 2004, Atwood, Robert C wrote: > Update: by adding absolute paths to the missing libraries, I can get it > to compile,but now I get > > Error: attempt to add non-widget child "DropSiteManager" to parent > "xmgrace" which supports only widgets > > I have scanned the mailing list archive , and notice this problem > mentioned a few times with other software, eg DDD, but I cannot find > any resolution to this problem mentioned. > Any pointers/ redirections to an example I haven't found yet? > Using a properly updated or build lesstif will correct this problem. Why are you trying to build it yourself?
Re: Geomview compilation under cygwin ...
On Thu, 15 Jan 2004, B. Marchand wrote: > At any rate, I had already posted this to the cygwin-xfree site with no > real success in terms of responses. I posted it here as well only for > completion. > I appologize, as I just found that post. I am *really* behind on my list reading because of the flu, then the holidays, and then a funeral. As such, I am reading the list backward chronologically and trying to keep up with the current stuff. At any case, that post did not contain the vital error message that clearly implies your problem. If you would follow my suggestions about updating your installation (particularly Xt, and lesstif), then recompile, you should get much further. Good luck. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: Geomview compilation under cygwin ...
On Thu, 15 Jan 2004, B. Marchand wrote: > Warning: XmManager ClassInitialize: XmeTraitSet failed > Error: attempt to add non-widget child "DropSiteManager" to parent > "Geomview" which supports only widgets. > This is an Cygwin X issue. Please see http://cygwin.com/lists.html so you can direct you questions to the proper audience. I have directed this response there. Your installation is out-of-date, or you used a stale mirror. Please search the cygwin-xfree archives if you need more information. The resolution for this error message is there several times (ie. Use setup to update from an up-to-date mirror and possibly recompile cleanly.) -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: using xbiff on remote mail
On Tue, 16 Dec 2003, Lester Ingber wrote: > I've been trying to use xbiff to monitor a remote mailbox as in `man xbiff`: > checkCommand (class CheckCommand) [snip] >therefore contain i/o redirection. An exit status of 0 indi- >cates that new mail is waiting, 1 indicates that there has been >no change in size, and 2 indicates that the mail has been >cleared. By default, no shell command is provided. > Notice it says exit status. [snip] > --8<-- top cut 2/2 -> bottom 2/2 --->8-- > #!/bin/tcsh -f > set HEADER = 13 > set MB = `ssh -q -x XXX.com -n /home/ingber/local/bin//mbsize` > if ( $MB <= $HEADER) then > /bin/rm -f /home/ingber/.Lester_mailbox > echo 2 exit 2? > else > if (-e /home/ingber/.Lester_mailbox) then > set MBHOME = `cat /home/ingber/.Lester_mailbox` > if ($MB > $MBHOME) then > /bin/rm -f /home/ingber/.Lester_mailbox > echo $MB > /home/ingber/.Lester_mailbox > echo 0 exit 0? > else > echo 1 exit 1? > endif > else > echo $MB > /home/ingber/.Lester_mailbox > echo 0 exit 0? > endif > endif > --8<-- bottom cut 2/2 <- top 2/2 --->8-- > -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: can't use windows with GoBack?
Just my late WAG: Try setting your display variable to localhost:0.0 and using -nolisten local. That should avoid some possible file system interaction. On Fri, 12 Dec 2003, Lester Ingber wrote: > Harold: > > Until this GoBack problem occurred, I was using > XWin -unixkill -emulate3buttons -clipboard -rootless & > wmaker & > > After I installed GoBack, I hit the terrible/impossible performance. > I found that > XWin -unixkill -emulate3buttons -clipboard -multiwindow & > and with even 1 or 2 xterm windows was just a bit better, but still miserable. > -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: Minimal set for XFree86
On Fri, 12 Dec 2003, Vinod Gupta wrote: > What is the minimal set of packages I need to download for > running XFree86 X-server? > If you use Cygwin's setup program to do the install, it will automatically select them for you. If it does not do that correctly, that's a bug. Please report it. However, before sending your next message, please take a look at http://cygwin.com/lists.html and select the appropriate list to send it to. (Hint: Xfree86 questions should go to [EMAIL PROTECTED]) I have redirected this reply there. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: Portable Cygwin works, but XWin fails
On Wed, 10 Dec 2003 [EMAIL PROTECTED] wrote: > Brian Ford wrote: > > No, you don't need to. Just Xwin.exe -nolisten local. > > Thank you. This worked just fine. I take the point about Google-ing - that's > how I learned that diverting tmp/XWin.log might help. I didn't see the > "-nolisten local" advice ... > I found both in the same message, although it is older than I stated: http://sources.redhat.com/ml/cygwin-xfree/2002-07/msg00165.html > Just one final question: when I get into rxvt after "XWin -nolisten > local -multiwindow &", the keyboard suddenly becomes USA, whereas it is set > (correctly) to UK otherwise, within bash, within rxvt and for that matter > within Windows. In this case, when I exit rxvt back to bash, the UK keyboard > is recovered. > I think the message listed above has another hint for you about this :). > Does the "-nolisten local" switch impose some kind USA default, as it would > indeed appear to do? > No, not related at all. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
RE: how to make xterm point for active window without mouse click
On Wed, 10 Dec 2003, Haomin Wu wrote: > Does anyone understand what I am stating below? > Yes. > Since no any response so far, maybe I did not describe it clearly. > Some people on this list are students and are very busy with finals now. Others have year end projects at work to wrap up. Please be patient. > If you have any inputs, let me know. > > I have recently installed cygwin on my pc windown-xp. > You meant Windows XP. > The cygwin version 2.416. > No. That is the version of the Cygwin installer (setup.exe) that you used. See the output of "uname -a" for the Cygwin version. > I run startxwin on my window dos prompt and get a xfree86 server > running on the window. I find one thing amazing is that all x-terms can > be opened on MS window xp instead on the xfree86 own window which used > to be the case with previous version. > startxwin now uses the -multiwindow switch to enable the native Windows XP window manager instead of twm or the like. Stay tuned for an even more improved version comming soon. > But one thing that I don't quite > like is that now all the xterm windows don't have the point-to-active > functions which should be the case in x-window. Now every time, I want > to type commands on a xterm, I have to use mouse click to make it active > like MS window. This is really inconienent. Is there any way I can set > up the windows for mouse point-to-make acive. > This is a function of your window manager. You have two options: 2.) Edit the startxwin.sh script to remove the -multiwindow switch and use a window manager such as twm that you have configured to react this way. 2.) Continue using -multiwindow and try XP PowerToys Tweakui, although I believe there are behavioral problems here as well, YMMV. With it, you can make all of Windows act the way you want. See: http://www.microsoft.com/windowsxp/pro/downloads/powertoys.asp -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: Portable Cygwin works, but XWin fails
On Wed, 10 Dec 2003 [EMAIL PROTECTED] wrote: > PS: Entirely unrelated question. When I start XWin from a conventional HD > full installation of Cygwin, on a broadband 24-hour internet-connected > machine, it evidently accesses the web. (I know this, because when Norton is > up and running, I can tell that XWin specifically asks permission to do so.) > Why does it do this? As far as I can tell, if I pull the broadband plug, > Cygwin and XWin still work ...) > It doesn't really access "the web". Your display variable is set to localhost:0.0. localhost is 127.0.0.1, ie. a TCP/IP address. Thus, X11 uses TCP/IP for loopback communications. Even if you set your display variable to just :0.0, ie. use a local AF_UNIX socket (which -nolisten local defeats), it would still use TCP/IP because this is how Cygwin emulates local AF_UNIX sockets. Secondly, I think there is one piece of code that tries to look up your hostname via DNS. That may actually breifly access "the web" depending on your DNS configuration. HTH BTW, both of these questions that I answered for you are in the recent (< 3 month old) list archives. Please try searching them and google before posting. Thanks. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: Portable Cygwin works, but XWin fails
On Wed, 10 Dec 2003 [EMAIL PROTECTED] wrote: > > What is your display variable set to? > > > localhost:0.0 > > > Do you have a /tmp/.X11-unix/X0 file on your memory stick? > > > Yes: so I wonder whether in trying to make a CD version, as well as > re-routing the file /tmp/XWin.log, I ought also to try to re-route the file > /tmp/.X11-unix/X0. > No, you don't need to. Just Xwin.exe -nolisten local. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: Portable Cygwin works, but XWin fails
On Wed, 10 Dec 2003 [EMAIL PROTECTED] wrote: > I have been able to run portable versions of Cygwin, reduced in one way or > another, both from writable USB memory sticks and from unwritable CDs. > Lately I tried running XWin from a writable stick. By observing which files > were written where, and as a consequence setting up links using > ln -s /dev/null /tmp/Xwin.log > ln -s /dev/null /var/run/utmp > it really seemed that I had addressed all problems: in repeated uses, > nothing new was written to the stick at all. I then burned a CD, but > disappointingly XWin "dies" as soon as it is started. That is, I start the > process with bash, and then try > XWin -multiwindow & > which I would normally follow with > rxvt -display localhost:0.0 -e bash > but XWin does not persist. (Sorry: I don't know how to express what happens > other than to say it "dies" immediately.) > This is VERY disappointing. Any clues to what else I might try? > What is your display variable set to? Do you have a /tmp/.X11-unix/X0 file on your memory stick? That might be the issue. > By the way, in mounting the portable version, I have already established > that the directory /cygdrive/c/tmp/ must exist, so I suppose I could try > ln -s /cygdrive/c/tmp/XWin.log /tmp/XWin.log > before burning to CD. (I've already made 5 coasters. At this rate I'll be > able to floor the bathroom.) > Thanks. > Fergus > -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: cygwin as X client
I think you read that wrong. He is trying to do the inverse of your
recipie.
On Wed, 10 Dec 2003, Oliver Brandt wrote:
> 1. "X11Forwarding" in ssh_conifg (etc/ssh/ssh_config) on your linux box
> is enabled ("Yes")
> 2. "X11Forwarding" in sshd_config (etc/ssh/ssh_config) on your linux box
> is enabled ("Yes")
> 3. ssh on your linux box is enabled (/etc/services)
> 4. on your windows machine: export DISPLAY=YOUR_IP_WINDOWS2000:0.0
> 5. start XWin.exe AND your windowmanager (e.g. wmaker, fvwm ...)
> 6. ssh -X -l username hostname_linuxbox from your cygwinshell
> 7. open xemacs or xterm or any X-application and it should pop up in
> your X-Window
>
> > Now I am on trip, the computer in my offcie is cygwin/win2000. I opened the ssh
> > and apache server.
> > The computer I used now is a linux system. I sshed to
> > my cygwin and want to use xterm. But it gave the error
> > information
> >xterm Xt error: Can't open display:
> > But I can use xterm on cygwin locally.
> > I sshed with the parameter -X,
> > and I browsered the mail archives, I didn't find help
> > for me.
> > I only wanted to use the Xapplication and I should be
> > able to do so for I can use it locally. What is going
> > wrong?
> >
--
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax: 314-551-8444
Re: keyboard settings
On Wed, 10 Dec 2003, Alexander Gottwald wrote: > On Wed, 10 Dec 2003, Cee Rainer wrote: > > I do not succeed in setting my german keyboard (portable PC, 88 > > keys) under Cygwin XFree86. I have read the FAQ's and the hints on > > the Chemnitz homepage > > (http://www-user.tu-chemnitz.de/~goal/xfree/#config). > > I do not know how applicable to Cygwin Xfree86 those hints are. AFAIK, the goal of Cygwin XFree86 is to automatically detect the proper settings from Windows when possible. > > This is what I did so far: > > > > - I have copied the XF86Config sample file into the directory > > etc/X11/XF86Config, which I first had to create, and unpacked it > > I think you meant /etc/X11/. If that directory did not exist, you have an installation problem. Please then see http://www.cygwin.com/problems.html and *attach* an *uncompressed* cygcheck.out as requested. This would be a good idea anyway. The XF86Config file should go in /etc/X11/. But, IIRC, until recently at least, this file was ignored. > > - I have uncommented the lines > > Option "XkbRules""xfree86" > > Option "XkbModel""pc105" > > Option "XkbLayout""de" > > > > Nevertheless I still have the US keyboard settings. It seems as if the > > config file is completely ignored. My /tmp directory is not mounted at > > all. I am using the latest Cygwin version (1.5.5-1.) > > As above, depending on your version, it may be. But, I suspect, you put it in the wrong place. I did not understand the relevance on the /tmp reference. > What tells /tmp/XWin.log? > Alexander meant to please also attach this file. Thanks. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: Problems with windowmaker icons
Please search the archives before posting as this is a frequently reported issue. Please also *attach* your cygcheck -svr output. Thanks. http://sources.redhat.com/ml/cygwin-xfree/2003-11/msg00273.html http://www.cygwin.com/ml/cygwin-xfree/2003-11/msg00298.html On Tue, 9 Dec 2003, RK wrote: > Dear Cygwin/XFree developers, > > I am starting XFree using my script containing following commands: > #! /bin/sh [snip] > wmaker.exe > > Starting with above script results in following warning messages: > TIFFReadDirectory: Warning, /usr/X11R6/share/WINGs/Images.tiff: unknown > field with tag 317 (0x13d) encountered. > TIFFReadDirectory: Warning, > /usr/X11R6/share/WindowMaker/Icons/Terminal.tiff: unknown field with tag > 317 (0x13d) encountered. > > Visibly the middle icon of the three in the upper right corner is broken. > -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: [Lesstif] INSTALL.html#compile_Windows
On Sun, 7 Dec 2003, Danny Backx wrote: > Hmm, maybe I didn't read some message carefully enough to figure > out that this was a complete and working patch set, not work > in progress. > At the time, a lesstif DLL for Cygwin was still a work in progress, all be it an iminent one. But, the Xt/Xmu/Xaw DLLs described by your documentation as the reason for its impossibility did already exist. Hence, I requested a documentation update while soliciting help for the work in progress. > If that is so, my apologies. > It was confusing, and I should have supplied an actual documentation patch instead of just the commentary. So, my appologies as well. > Anyway : I've located the messages in your mail and worked through > the patch set. I've applied them. One was wrong (aclocal.m4 is a > generated file, ac_find_xft.m4 needed to be changed instead. > I definately did not expect you to do this. As I stated previously, I intended to clean them up and submit them myself given sufficient time. At the time of the first report, this patch set did not exist, yet. Anyway, thank you for taking the time to do this. I have not yet had the time to review the resul, but I will try to soon. > I've edited the INSTALL document, you may want to read the > changes. I am not sure whether Interix and others still exist, > maybe you'd like me to add more comments about Cygwin. If you > do, don't hesitate to ask. > This looks fine for now. Thank you again. > I don't run Cygwin regularly so I'm not in a position to test > these changes. Can someone check ? Do you want me to create > another release of LessTif with this change ? > I will check as soon as I find time. Cygwin distributes its own binary and source releases independant of the lesstif release schedule, so a new release from you is not necessary. Thanks for the offer. > On Thu, 2003-12-04 at 20:35, Brian Ford wrote: > > Arnaud Desitter wrote: > > > Harold L Hunt II wrote: > > >> Richard Campbell wrote: > > >>>Arnaud Desitter wrote: > > >>>>http://www.lesstif.org/INSTALL.html > > >>> > > >>> "On windows using Cygwin, U/WIN or Interix, LessTif must be built as > > >>> static libraries. Because, one of the biggest issues with X on Win32 > > >>> is the moronic DLL format. Specifically - it is not possible to export > > >>> data from a Win32 DLL in a form that can be used to statically initialize > > >>> another global variable. Data access from a DLL requires at least one > > >>> pointer indirection, and hence executable code. This is why X11R6 doesn't > > >>> have DLLs for Xt/Xmu/Xaw (and Motif) on Win32." > > >>> > > >>> If yes, these rules have been changing. Brian, isn't this what you > > >>> were specifically working on recently? > > >>> > > I was just trying to help pick up the pieces. > > > > Ralf Habacker and Harold L Hunt II fixed the shared Xt problem here: > > > > http://www.cygwin.com/ml/cygwin-xfree/2003-10/msg00173.html > > > > Then, Zhangrong Huang and Harold L Hunt II fixed lesstif here: > > > > http://www.cygwin.com/ml/cygwin-xfree/2003-10/msg00347.html > > > > > > The statement in quotes above is now misleading and completely > > > > incorrect. We are distributing *only* a shared version of LessTif on > > > > Cygwin now. The various problems mentioned in the quote all have > > > > work-arounds, some of which were already used by OS/2; we enabled those > > > > work-arounds and adding one or two more of our own and the shared > > > > LessTif library compiles and works fine now. > > > > > > I'll take an action item to push these changes back upstream to lesstif, > > but don't expect any particular time line. > > > > > Fill free to contact the lesstif guys to fix it. > > > > > I did, here: > > > > http://www.cygwin.com/ml/cygwin-xfree/2003-10/msg00291.html > > > > They have not, yet. > > > > I guess I need to supply an actual documentation patch. Again, I'll put > > it on my list. But, don't expect immediate action. > -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: DDD 3.3.8 recipe - was - RE: libtool created import libs brok en? was RE: DDD 3.3.8 (i686-pc-cygwin) gets `Segmentation fault
On Fri, 5 Dec 2003, Harold L Hunt II wrote: > Richard Campbell wrote: > >Harold L Hunt II wrote: > >>This is due to the way that the configure script for libiberty is called > >>in configure.ac: > >> > > If I was paying attention, libiberty uses autoconf 2.13 or similar, and the > > other pieces use 2.5...That's going to be a real pain to set up, I think... > > > It's just our top-level configure being stupid and passing CFLAGS and > LDFLAGS as options instead of as environment variables. I don't think > it matters what version of autoconf libiberty is using (at least not for > this problem). > HTH http://cvs.sourceforge.net/viewcvs.py/ddd/ddd/PROBLEMS?r1=1.106&r2=1.107 -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: Cygwin crashed by emacs???
On Fri, 5 Dec 2003, Sergey Barabash wrote:
> Dear Brian,
>
> Thank you for your reply.
>
You are welcome. But, I prefer that you send all Cygwin XFree related
mail only to cygwin-xfree at cygwin dot com instead of sending me private
mail. Thanks.
> In fact, cygwin-xfree was for "discussion" of XFree and
> answering "how to" questions, according to the online description.
> I wanted to report a bug and the only group mentioning bug
> reports was cygwin. Sorry if this was misdirected, but then the
> online description should be clarified.
>
I'm glad you read the list descriptions that closely :). Most people
don't.
PTC, but this one is not worth my time.
> > I also suggest you use http://www.cygwin.com/setup.exe to update your
> > installation (especially the cygwin package, emacs package, and all
>
> It is not an emacs problem: as I mentioned, I ran different versions
> of emacs on different platforms and they all crash XWin.
>
I agree.
But, your Cygwin installation sounded like it was significantly
out-of-date (<= 1.3.22. Since you still have not provided the
information requested in http://www.cygwin.com/problems.html, I still
can not tell.)
Since 1.5.x was an major ABI change, I suggested that you update
everything (at least what you claimed to be using) to avoid additional
breakage. Furthermore, you will generally not get free "support" from
an open source community if your software is very out-of-date.
> Furthermore, an XServer must be stable no matter what
> crazy thing a window application does -- if it is not, it is a bug
> with the Xserver and not the problem of the application -- don't you
> think so?
>
Yes, but you should always check to see if the bug has been fixed in the
latest version first.
> > This is XWin.exe, not your "entire cygwin session" (whatever that means).
> > As such, please use the [EMAIL PROTECTED] list. I have directed
> > this reply there.
>
> I hope you do not assume that every cygwin user has done extensive
> study of the code and knows that "XWin" is same as "XFree"...
>
No, I don't. That would be amazing if they did.
> Also, I installed cygwin because I needed a free X-server and that's
> how I normally use it. I do appreciate the fact that cygwin
> provides many more tools and a virtual linux machine running on my
> computer, but the only way I know how to use those tools (not to say
> that I frequently use them, but still..) is through the X-interface, so
> indeed an "entire cygwin cession", being all interactive jobs, whether
> local or remote (and in my case all remote), would crash for me anyway..
>
Ok, how about "my entire Cygwin *X* session". That would be the normal
term to use, I think.
> > I don't know what Cygwin version 1.3-4 was/is.
>
> Actually that's the documentation version
> (usr/doc/Cygwin/cygwin-doc-1.3-4.README) which I assumed was same as
> the program version.
> The uname info is actually CYGWIN_NT-5.0 1.3.22(0.78/3/2)
> Sorry, I did not know that I could not trust documentation... ;(
>
Why would you expect the documentation version to be the same as the
program version? The two do not usually change together. I would expect,
however, that if the documentation documented the program version, it
would document the correct version number.
> > I suggest you visit http://www.cygwin.com/problems.html to see how to
> I did, except it was all obvious stuff.
>
Where is your cygcheck output?
> If you are concerned about people not knowing which version
> they are running, you could have that web page explain how to correctly
> look up the version number! Similarly, if the executable name ("XWin") is
> different from the project name ("XFree"), the webpage could list both...
>
Ok on the latter. The former would have been included in cygcheck.out.
> I'll try to update cygwin but I doubt it will change anything,
> if similar problem has not been addressed recently, which apparently is
> not the case. My version is only 4 months old, and this looks like
> quite a nasty bug...
>
I tremendous amount of work on Cygwin and Cygwin Xfree86 has been done in
those four months. It may not fix your problem, but we won't know until
you try. And, I don't know anyone who is going to take you seriously
until you do.
> Anyway, thanks again for the reply
> and for your help!
> I'll send one more reply to the group with the correct version #.
>
You are welcome again.
I don't mean to come on too strong, but we have many people who do not
take the time to read any of the web site/documentation/list archives
first. That is the standard assumption, especially if you do not attach
cygcheck output as requested.
Your reply to the list was probably too short to solicit any real
feedback. Please try to update and post your results again. Thanks.
--
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax: 314-551-8444
Re: Xaw patch (focus problem) & DLL
On Thu, 4 Dec 2003, John E Urbanczyk wrote: > I am working with an xterm I modified and rebuilt under the latest > cygwin source files and binaries and have experienced the problem with > focus (the xterm only has keyboard focus if the mouse is in the window). > This was corrected with a patch by Harold Hunt recently, and I have been > looking into implementing the patch. > What do you mean, implementing the patch? > However, when I rebuilt the library > with the patch, using the Imake and make with the default settings, it > builds a static library. > Why build the library at all? Why not just use the one Harold released here? http://www.cygwin.com/ml/cygwin-xfree-announce/2003-11/msg3.html > (I am building using the files in > cygwin/xc/programs/Xaw. And because of the firewall I work behind, I > have been unable to access the CVS source tree, so am unaware of what > may be missing in my cygwin environment.) > Now I'm really lost. You said you were using the "latest cygwin source files and binaries." And, how does the XFree CVS source tree have anything to do with things missing from your "cygwin environment". > It appears from Harold's email > that he rebuilt a dynamic library, as he states that he tested the patch > by running a non-recompiled xterm against the library. > Yes. > So my question > is: what library (or libraries) need to be rebuilt, > None if you are using the release in the announcement above. > and does one go about building it? > I would say without getting up-to-date CVS sources, no one would be interested in re-inventing this for you. > I have looked at the documentation on dlltool, but > have never used it before. (The last time I built xterm under cygwin was > over two years ago, and I believe that static libraries were all that I > used. > I hope your sources are not that old :). > And I am confused by the various libraries used in my cygwin setup > - for example, libXaw-7.dll.a is used by the linker in building xterm, > It's an import library. Read up on them. > apparently, but cygxaw-7.dll is required at runtime.) Thanks in advance > for any help. > This is the actual dll. Maybe it's just me, but I found your description very confusing. Since you had not received a reply yet, I thought I would try to help you clarify. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
libtool created import libs broken? was RE: DDD 3.3.8 (i686-pc-cygwin) gets `Segmentation fault
Charles Wilson, Could you look at the problem discovered in the thread below and give us a comment? Thanks. http://www.cygwin.com/ml/cygwin-xfree/2003-12/msg00053.html I'm not an autotool expert, but: On Thu, 4 Dec 2003, Richard Campbell wrote: > bash-2.05b$ autoreconf --install --force These are just warnings, so I think this part worked fine. I guess the ddd people should clean these up? > configure.ac:248: warning: AC_CANONICAL_HOST invoked multiple times > autoconf/specific.m4:363: AC_CYGWIN is expanded from... > configure.ac:248: the top level > autoheader: WARNING: Using auxiliary files such as `acconfig.h', > `config.h.bot' > autoheader: WARNING: and `config.h.top', to define templates for > `config.h.in' > autoheader: WARNING: is deprecated and discouraged. > autoheader: > autoheader: WARNING: Using the third argument of `AC_DEFINE' and > autoheader: WARNING: `AC_DEFINE_UNQUOTED' allows to define a template > without > autoheader: WARNING: `acconfig.h': > autoheader: > autoheader: WARNING: AC_DEFINE([NEED_FUNC_MAIN], 1, > autoheader: [Define if a function `main' is needed.]) > autoheader: > autoheader: WARNING: More sophisticated templates can also be produced, see > the > autoheader: WARNING: documentation. > Here is where we should have stopped, although I don't know how to do that with autoreconf. The following are errors from subdirectories that use older (circa 2.13) autoconf scripts. autoreconf does not support mixed versions, I guess? > configure.in:54: error: possibly undefined macro: AC_PROG_CC_GNU > If this token and others are legitimate, please use m4_pattern_allow. > See the Autoconf documentation. > configure.in:65: error: possibly undefined macro: AC_PROG_CC_G > configure.in:198: error: do not use LIBOBJS directly, use AC_LIBOBJ (see > section `AC_LIBOBJ vs LIBOBJS' > configure.in:310: error: possibly undefined macro: AC_PROG_CC_WORKS > autoreconf: /usr/autotool/devel/bin/autoconf failed with exit status: 1 > So, if this hasn't left your tree broken, I think it would test what I wanted. You should now have libtool 1.5 for the main ddd tree. I think it would fix this. New in 1.5: 2002-04-14; CVS version 1.4e, Libtool team: * Support auto-import patch to binutils on cygwin for much improved dll support. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: Cygwin crashed by emacs???
On Thu, 4 Dec 2003, Sergey Barabash wrote:
> My entire cygwin session CRASHES CONSISTENTLY
> ("XWin.exe has generated errors... log is being created")
>
This is XWin.exe, not your "entire cygwin session" (whatever that means).
As such, please use the [EMAIL PROTECTED] list. I have directed
this reply there.
> when I try using "ediff-buffers" in emacs.
>
> Details:
> I am running cygwin 1.3-4 under Windows 2000 (v.5.00.2195, s.p.4)
>
I don't know what Cygwin version 1.3-4 was/is.
I suggest you visit http://www.cygwin.com/problems.html to see how to form
a useful bug report with the proper supporting information.
I also suggest you use http://www.cygwin.com/setup.exe to update your
installation (especially the cygwin package, emacs package, and all
XFree86 packages) before soliciting further support. If you are not
up-to-date, you will not get much help.
--
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax: 314-551-8444
RE: DDD 3.3.8 (i686-pc-cygwin) gets `Segmentation fault WAS Re: c ompiling DDD
On Thu, 4 Dec 2003, Richard Campbell wrote: > Brian Ford wrote: > >What version of libtool is ddd-3.3.8 using? > > > Automatically generated by configure? > I checked. In ltmain.sh for ddd-3.3.8 it says VERSION=1.4.2. I don't know what it was in 3.3.7. The latest is 1.5. > >Does re-libtoolizing fix it? > > Could you try "autoreconf --install --force", re-configure, and report the results? It would be nice to know if the latest autotools are still broken. Thanks. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
RE: DDD 3.3.8 (i686-pc-cygwin) gets `Segmentation fault WAS Re: c ompiling DDD
On Thu, 4 Dec 2003, Richard Campbell wrote: > Arnaud Desitter wrote: > >Richard Campbell wrote: > >> Now, I guess, to try and walk back all of the automatic steps to figure > >> out why ddd ended up linking against that libimp-cygXm-2.a file. > >> > >Credit or blame libtool for that. > > What version of libtool is ddd-3.3.8 using? Does re-libtoolizing fix it? When these two questions are answered, it is probably time to move this to [EMAIL PROTECTED] or [EMAIL PROTECTED] where the Cygwin libtool experts are. > Specifically, the following two settings: > > # Whether or not to build static libraries. > build_old_libs=yes > > # Create a temporary old-style archive to link instead of a shared archive. > old_archive_from_expsyms_cmds="\$DLLTOOL --as=\$AS --dllname \$soname --def > \$output_objdir/\$soname-def --output-lib \$output_objdir/\$newlib" > > If commented out, everything works cleanly. > > Now, the bizarre part of the generated libtool is the following: > > # Whether or not to build shared libraries. > build_libtool_libs=yes > > # Whether or not to build static libraries. > build_old_libs=yes > > Why would you have both "shared" and "static" turned on? > To have the option of either, obviously. Some packages default this way as a courtesy. Static libs are useful when profiling, distributing binaries without worrying about associated libs, etc. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
INSTALL.html#compile_Windows was (Re: DDD 3.3.8 (i686-pc-cygwin) gets `Segmentation fault)
Arnaud Desitter wrote: > Harold L Hunt II wrote: >> Richard Campbell wrote: >>>Arnaud Desitter wrote: >>>>http://www.lesstif.org/INSTALL.html >>> >>> "On windows using Cygwin, U/WIN or Interix, LessTif must be built as >>> static libraries. Because, one of the biggest issues with X on Win32 >>> is the moronic DLL format. Specifically - it is not possible to export >>> data from a Win32 DLL in a form that can be used to statically initialize >>> another global variable. Data access from a DLL requires at least one >>> pointer indirection, and hence executable code. This is why X11R6 doesn't >>> have DLLs for Xt/Xmu/Xaw (and Motif) on Win32." >>> >>> If yes, these rules have been changing. Brian, isn't this what you >>> were specifically working on recently? >>> I was just trying to help pick up the pieces. Ralf Habacker and Harold L Hunt II fixed the shared Xt problem here: http://www.cygwin.com/ml/cygwin-xfree/2003-10/msg00173.html Then, Zhangrong Huang and Harold L Hunt II fixed lesstif here: http://www.cygwin.com/ml/cygwin-xfree/2003-10/msg00347.html > > The statement in quotes above is now misleading and completely > > incorrect. We are distributing *only* a shared version of LessTif on > > Cygwin now. The various problems mentioned in the quote all have > > work-arounds, some of which were already used by OS/2; we enabled those > > work-arounds and adding one or two more of our own and the shared > > LessTif library compiles and works fine now. > > I'll take an action item to push these changes back upstream to lesstif, but don't expect any particular time line. > Fill free to contact the lesstif guys to fix it. > I did, here: http://www.cygwin.com/ml/cygwin-xfree/2003-10/msg00291.html They have not, yet. I guess I need to supply an actual documentation patch. Again, I'll put it on my list. But, don't expect immediate action. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
RE: compiling DDD
On Wed, 3 Dec 2003, Richard Campbell wrote: > I reinstalled lesstif from setup. Same exact results. > WAG, try configuring with --without-athena. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: Running Windows on Linux (Re: How to configure a windows machine as an X client?)
On Wed, 3 Dec 2003, Jay Smith wrote: > On the linux server (or a linux workstation) you could run a program such > as Wine, Crossover, or VMWare which allow you to run linux programs on the ^Windows > linux server (and thus from any X client connected to the linux server). -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: How to configure a windows machine as an X client?
Please set the line wrap to something less than 80 characters in your mail client. Thanks. On Wed, 3 Dec 2003, Thai.Dang-Vu-1 wrote: > I have a question. Could I configure a Windows machine as an X client > so that from a Linux machine I can run Internet Explorer and have the IE > window on that Linux machine? If it is possible, could you tell me which > document I should read? > No. IIRC, a project to do this was discussed on this list about a year ago, but AFAIK, nothing came of it. Search the archives if you are interested. Google for VNC or rdesktop for other alternatives. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
RE: compiling DDD
On Wed, 3 Dec 2003, Richard Campbell wrote: Richard, I'm still very hit and miss with respect to finding time to look at this, but since you are the only one sending in solid information, could you post the output of cygcheck ddd.exe. Thanks. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: compiling DDD
This is an XFree86 issue, so please use the proper mailing list ([EMAIL PROTECTED]). On Wed, 3 Dec 2003 [EMAIL PROTECTED] wrote: > I used to be able to compile ddd fine, but something occurred when i recently > updated ddd. I'm getting static initialiation_construct_and_destructor errors. > Please post the exact (cut and paste) error messages you receive. > If I revert to an oldfer binary or older GCC(3.2.x) then it compiles fine, but > segfaults on startup. > What does an older binary mean? Please see http://www.cygwin.com/problems.html for the additional information we need to help. Also, search the cygwin-xfree mailing list archives to see several discussions on this topic. > *ddd log* > GNU DDD 3.3.8 (i686-pc-cygwin) > Copyright (C) 1995-1999 Technische Universit䴠Braunschweig, Germany. > Copyright (C) 1999-2001 Universit䴠Passau, Germany. > Copyright (C) 2001 Universit䴠des Saarlandes, Germany. > > Compiled with GCC 3.2 20020927 (prerelease) > Requires X11R6, Xt11R6, Motif 2.1 (GNU/LessTif Version 2.1 Release 0.93.91) > Includes XPM 3.4.11, Athena Panner (702L), DDD core > Built 2003-12-02 by me. > $ ddd > ! Segmentation fault > ** > It complains about getting an XT error. > Please post the exact XT error. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: DDD needs a porter [Was: DDD 3.3.8 segmentation error, relatedto Motif?]
On Wed, 26 Nov 2003 [EMAIL PROTECTED] wrote: > At a certain point I had a simular problem and solved it as follow: > - start Setup.exe > (used a more up to date mirror: ftp://ftp.easynet.be/cygwin) > I do believe my mirror is fine, and I am up to date. > - under all: select re-install > - under dev: select gcc 3.2-3 > I will NOT revert my gcc to 3.2. If it can not be done with the current gcc, then it is not worth fixing. Also, this should have nothing to do with the error I received. > - I removed my local copy of ddd.3.3.8 > - unzipped everything form ddd.3.3.8 > - under bash: ./configure > - under bash: make > - under bash: make check > I have done this many times without a change in symptom. > Result: still problems with Motif? > I don't doubt it. You are using old buggy software to compile/link with. Either use current stuff, or don't expect support. I will get back to this if/when I have time. But to the casual glance, my problem appears to be missing include files for libiberty in ddd (ie, a ddd bug). -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: Problem compiling Lesstif programs on latest Cygwin
On Wed, 26 Nov 2003, Brian Ford wrote: > Please see this thread and search the archives before posting. Thanks. > Sorry, I forgot the thread reference. http://www.cygwin.com/ml/cygwin-xfree/2003-11/msg00219.html -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: Problem compiling Lesstif programs on latest Cygwin
On Wed, 26 Nov 2003, Skeeter wrote: > Although I have been compiling and running Lesstif > programs on Cygwin successfully for the past year, > something in the latest Cygwin package seems to have > broken my ability to compile/link(?) new programs. > (I can still run previously compiled X/lestif > programs.) > Yes. It was the transition to a shared Xm/Xt, but you do NOT have the latest Cygwin packages of those if you are seeing the following error. You might need to choose a different mirror site. Please see this thread and search the archives before posting. Thanks. Additional comments follow. > $ gcc -I/usr/X11R6/include -L/usr/X11R6/lib memo_1.c > -lXm -lXt -lX11 -o memo_1 > Info: resolving _XtStrings by linking to > __imp__XtStrings (auto-import) > Info: resolving __XtInherit by linking to > __imp___XtInherit (auto-import) > Info: resolving __XtInheritTranslations by linking to > __imp___XtInheritTranslations (auto-import) > Info: resolving _XtShellStrings by linking to > __imp__XtShellStrings (auto-import) > ... > Info: resolving _overrideShellClassRec by linking to > __imp__overrideShellClassRec (auto-import) > Info: resolving _transientShellClassRec by linking to > __imp__transientShellClassRec (auto-import) > These are info messages, so they are not really errors. Can someone explain how we should fix these? I gather it is a mundane search and replace type task, but I haven't had time to look deeply at it. This is the error that indicates your lesstif/XFree86 packages are out of data: > $ memo_1 test > Warning: XmPrimitive ClassInitialize: XmeTraitSet > failed > Error: attempt to add non-widget child > "DropSiteManager" to parent "memo_1" which supports > only widgets > -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: DDD needs a porter [Was: DDD 3.3.8 segmentation error, related to Motif?]
I was going to try to look into this, but I stumbled early on and don't want to waste my time on known issues. Given that those involved in this thread seem to have gotten much further, I thought I'd ask if there is a known quick solution. Thanks. ddd-3.3.8: bash ./configure make gives: Making all in libiberty make[1]: *** No rule to make target `../include/xregex.h', needed by `regex.o'. Stop. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: DDD 3.3.8 segmentation error, related to Motif?
On Fri, 21 Nov 2003 [EMAIL PROTECTED] wrote: > bt08pm: /usr/X11R6/include/Xm/ ddd --lesstif-version 93 >Warning: This DDD requires a Motif 2.1 library (using Motif > -1617156.-609) > Could you post cygcheck `type ddd`? > bt08pm: /usr/bin/ ddd --configuration >GNU DDD 3.3.8 (i686-pc-cygwin) >Copyright (C) 1995-1999 Technische Universität Braunschweig, Germany. >Copyright (C) 1999-2001 Universität Passau, Germany. >Copyright (C) 2001 Universität des Saarlandes, Germany. > >Compiled with GCC 3.2 20020927 (prerelease) > Why not the current Cygwin gcc? -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: twm takes no control
On Thu, 20 Nov 2003, Harold L Hunt II wrote: > Dai, > > Dai Itasaka wrote: > > > It is not just Cygwin version of twm. Exactly the same symptom is > > observed when using a twm on a RedHat or SuSE box managing a cygwin > > display. > > > > It is obvious that it is not twm that is broken. > > So it is another little issue related to the shared Xt and Xaw > libraries. I did a search in the twm sources for "Vendor", "Shell", > "VendorShell", etc. but didn't find anything. I am sure that you can > probably find info on how the OS/2 guys handled this bug, but searching > for "OS2" turned up nothing in the twm sources either. > I don't think so, Harold. If this happens with twm run from other OSs, that eliminates twm itself and all its dlls, doesn't it? It must be internal to the Cygwin X server, or its dlls, right? Dai, could you test the inverse? Cygwin's twm controlling a RedHat or SuSE X server? I think that would definately rule out twm and its dlls. > I am at a loss. As I said, this is yours to debug further. If twm is > the only app that is broken by the shared libs, then I am still not > particularly concerned. If it turns out that every other app is broken, > or a significant number of other apps are broken, then I will certainly > become concerned. > I don't have any examples, but to me, the description implies the latter ought to be the case. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: DDD 3.3.8 segmentation error, related to Motif?
This is *still* a cygwin-xfree issue. Please do not CC [EMAIL PROTECTED] Also, please do not CC me, as I read cygwin-xfree. Thanks. On Wed, 19 Nov 2003 [EMAIL PROTECTED] wrote: > I gat a more recent version now, and I recompiled ddd. > Earlier problem solved, new problem pops up: > Did you update all of Cygwin, or just the following packages? An attached cygcheck.out as requested in http://www.cygwin.com/problems.html would be helpfull. > The executable ends with: >Warning: This DDD requires a Motif 2.1 library (using Motif > -1617156.-609) >Continue at own risk. > >Internal error (Segmentation fault). > WAG: Your cygwin1.dll is pre 1.5? > Brian Fordd wrote: > >On Mon, 17 Nov 2003 [EMAIL PROTECTED] wrote: > >>Ihe same problem with ddd 3.3.8 and GCC 3.3.1. > >>I was able to compile ddd with GCC 3.2.3, but > >>when launching ddd I gat following problem: > >>(btw ddd --help works fine) > >> > >>Warning: XmPrimitive ClassInitialize: XmeTraitSet failed > >>Error: attempt to add non-widget child "DropSiteManager" to parent "ddd" > >>which supports only widgets > >>Xt error (attempt to add non-widget child "DropSiteManager" to parent > >>"ddd" which supports only widgets). > >><<...>> > >> DDD 3.3.8 (i686-pc-cygwin) gets `Segmentation fault' signal > >><< > >This is an Xfree86 issue. Redirecting to the proper list > >([EMAIL PROTECTED]). > > > >The error above was caused by the transition to a shared libXt/lesstif. > >Please make sure your Xfree86 packages and lesstif are up to date. > > -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: DDD Compilation Fails using GCC 3.3.1
On Mon, 17 Nov 2003 [EMAIL PROTECTED] wrote: > Ihe same problem with ddd 3.3.8 and GCC 3.3.1. > I was able to compile ddd with GCC 3.2.3, but > when launching ddd I gat following problem: > (btw ddd --help works fine) > > >> > Warning: XmPrimitive ClassInitialize: XmeTraitSet failed > Error: attempt to add non-widget child "DropSiteManager" to parent "ddd" > which supports only widgets > Xt error (attempt to add non-widget child "DropSiteManager" to parent > "ddd" which supports only widgets). > <<...>> > DDD 3.3.8 (i686-pc-cygwin) gets `Segmentation fault' signal > << > This is an Xfree86 issue. Redirecting to the proper list ([EMAIL PROTECTED]). The error above was caused by the transition to a shared libXt/lesstif. Please make sure your Xfree86 packages and lesstif are up to date. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: wmaker
On Sat, 15 Nov 2003, Lorenzo Travaglio wrote: > > What message? It should produce an xterm. > No. the only message is "startxwin.bat - Starting on Windows 95/98/Me" > fisplayed into a DOS console, and nothing more > Have you edited startxwin.bat? Is there an X icon in the icon tray? Please look at /tmp/XWin.log for errors. Have you run it successfully as another user? If so, you may need to delete /tmp/.X11-unix/X0. Harold, we have this problem all the time. One user logs in, uses X, logs out, then the next user logs in and X won't start because they can't delete/open /tmp/.X11-unix/X0. Does anyone know how to fix this? Even if the second user has administrator privledges, the startxwin.bat script can not delete the unix socket. Only if the second user explicitly does a chown to themselves can they/startxwin.bat delete the file. > > X11 uses the loopback interface with IP address 127.0.0.1 and so need > > "Internet" access. This is normal. > OK. > > > > The third one starts an X window but nothing more. After "X&" from bash, > > > when I try to run "wmaker&" the answer is only an error. > > > > > What error? > - wmaker fatal error. Could not open display "". > Please note that there isn't $DISPLAY or $COMPUTERNAME or other sounds-like > environment variables (like in my office's installation) and even if I try > to set such variable nothing happens. I use all the batch files like > provided by the installation. I've not modified them because I don't known > what to do. > Yes, you need to set DISPLAY to something like :0.0 if you are going to start X manually from bash. If you use startxwin.bat, this will be taken care of for you. Please post the contents of /tmp/Xwin.log. Thanks. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: chmod
On Fri, 14 Nov 2003, Lorenzo Travaglio wrote: > The only interface with Cygwin that actually works is the bash console, I'm > sorry for the mistake. Looking at the sae file with Windows Explorer it is > possible, however, to change the attributes, but not with chmod, That's > looks strange, but I didn't found any way to solve the problem. > Ugh. Again, what OS and what filesystem, and: * http://www.cygwin.com/problems.html * > Brian Ford wrote: > > More likely, you are running an NT variant at work and 9x at home? See: > > > > http://cygwin.com/faq/faq_toc.html#TOC45 and > > http://cygwin.com/cygwin-ug-net/highlights.html#OV-HI-PERM > > > > In that case, this is not Xfree86 related, so next time please use the > > main [EMAIL PROTECTED] mailing list. Also, see: > > > > http://www.cygwin.com/problems.html > > > > for how to report this issue correctly so that someone can answer without > > guessing. Thanks. > > > -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: wmaker
On Fri, 14 Nov 2003, Lorenzo Travaglio wrote: > I know three ways to run X application, from startxwin.bat, from Windows > application bar and from inside a bash shell. > The first one produces only the message related to XWin.exe. > What message? It should produce an xterm. > The second one produces only the ZoneAlarm alerts and nothing more even if I > answer 'yes' to ZoneAlarm's request to allow the application to access the > Internet (why? I haven't such a LAN!). > X11 uses the loopback interface with IP address 127.0.0.1 and so need "Internet" access. This is normal. > The third one starts an X window but nothing more. After "X&" from bash, > when I try to run "wmaker&" the answer is only an error. > What error? -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: xterm switching problem
On Wed, 12 Nov 2003, Igor Pechtchanski wrote: > This problem was reported multiple times (latest at > <http://cygwin.com/ml/cygwin-xfree/2003-11/msg00131.html>), and is > apparently due to the new dynamic Xaw library. The workaround for now is > to use the older xterm binary. > > I take it the "proper" solution is known and is being worked on, right, > Harold? > I think the answer to that question is sort of known based on lesstif work arounds, but not currently being worked on because no one has volunteered? -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: chmod
On Wed, 12 Nov 2003, Lorenzo Travaglio wrote: > I've sent to myself from my office a little bash program. With Xterm it is > impossible to change the peremissions even if 'chmod -v' says that new > permissions have take place. I have no idea about, do you have one? > You mean you can change the permissions in a bash console window with chmod, but not with chmod from an Xterm? More likely, you are running an NT variant at work and 9x at home? See: http://cygwin.com/faq/faq_toc.html#TOC45 and http://cygwin.com/cygwin-ug-net/highlights.html#OV-HI-PERM In that case, this is not Xfree86 related, so next time please use the main [EMAIL PROTECTED] mailing list. Also, see: http://www.cygwin.com/problems.html for how to report this issue correctly so that someone can answer without guessing. Thanks. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: XFree86-bin-4.3.0-7 xterm keyboard focus problems
Igor, This has been reported several times before. Although, you have probably contributed a more detailed analysis. I don't know if xterm should depend on Xaw, but I do know that Xaw needs a hack similar to the lesstif one for VendorShell (from memory). Or maybe it was Xaw3d that needs that. Sorry to be so nebulous. I thought this info might tickle someones memory or fancy. On Tue, 11 Nov 2003, Igor Pechtchanski wrote: > Hi, all, > > I noticed that the xterm executable that comes with the 4.3.0-7 version of > XFree86-bin has problems with keyboard focus. After the mouse pointer > entered and left the window once, the keyboard input is ignored unless the > mouse pointer is in the window. The window apparently keeps the focus, > but no keyboard input is processed. Other executables don't suffer from > this problem, and extracting the xterm from XFree86-bin-4.3.0-4 fixes it. > I've tried running this with Exceed and also remotely on Linux through > ssh. FWIW, here are the relevant files: > > $ ls -l /usr/X11R6/bin/xterm-* > -r-xr-xr-x+ 1 igor Users 262656 Oct 30 11:14 > /usr/X11R6/bin/xterm-4.3.0-7.exe > -rwx--x--x1 igor Administ 804352 Sep 20 14:52 > /usr/X11R6/bin/xterm-4.3.0-4.exe > > The second file is manually extracted from the XFree86-bin-4.3.0-4 > tarball. The reported version numbers are identical: > > $ xterm-4.3.0-7.exe -version > XFree86 4.2.99.903(174) > $ xterm-4.3.0-4 -version > XFree86 4.2.99.903(174) > > The latter version seems to depend on three extra DLLs: > > $ cygcheck /usr/X11R6/bin/xterm-4.3.0-7.exe | sort -b > /tmp/a7 > $ cygcheck /usr/X11R6/bin/xterm-4.3.0-4.exe | sort -b > /tmp/a4 > $ diff -I xterm -w /tmp/a4 /tmp/a7 > 4a5 > > C:/cygwin/usr/X11R6/bin\cygXaw-7.dll > 6a8 > > C:/cygwin/usr/X11R6/bin\cygXmu-6.dll > 7a10 > > C:/cygwin/usr/X11R6/bin\cygXt-6.dll > > I think libXt used to be linked in statically, but I don't recall xterm > being dependent on libXaw before. > > xterm is the only executable that seems to have changed behavior in my > case (xev, for example, works fine, i.e., respects the window manager's > focus policy). I suspect this new dependence on libXaw is the culprit, as > other Xaw-enabled apps (xfig, editres, etc) are notorious for having a > mind of their own when it comes to keyboard focus. > > Can anyone confirm/deny this? If an unwanted dependence on libXaw was > introduced in the xterm build, can it please be removed somehow? > Thanks, > Igor > -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: obstacle running "cygwin" (communicating with Solaris 8, Sparc) ...
On Tue, 4 Nov 2003, Andreas (privat) wrote: > it's my intention to start a remote login-process at the solaris-pc via > cygwin. Unfortunately the > login-session is always interrupted. Cygwin is only able to depict a black > screen (including the mouse cursor). Nothing else occurs > http://xfree86.cygwin.com/docs/faq/cygwin-xfree-faq.html#q-solaris-fonts -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: Grabbing XFree86.org's xc/ tree using cvsup
On Sun, 2 Nov 2003, Harold L Hunt II wrote: > He suggested using cvsps to generate patch sets. He also suggested > doing our development on a branch, keeping HEAD more or less in sync > with XFree86.org CVS HEAD, and merge HEAD to our branch whenever > required (to get bug fixes, etc.). > Just a note here. This is what CVS's notion of "vendor branches" is for. Although I have limited experience with them, I suggest you read up a little here before making this decision. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: freetype2, fontconfig, and rebuild of dependent packages coming shortly
On Wed, 29 Oct 2003, Harold L Hunt II wrote: > Brian Ford wrote: > > Well, I sent this last night before the new lesstif release, but somehow > > it evaporated. > > > Nope, didn't evaporate... I even replied to it :) > Sorry, Harold. I should have checked the archives first. Strangely though, neither made it to my inbox. >From that (http://cygwin.com/ml/cygwin-xfree/2003-10/msg00375.html) reply: > > On Tue, 28 Oct 2003, Harold L Hunt II wrote: > >>I ran into an issue at the last minute when I looked at the LessTif > >>rebuild and realized that it was not using freetype and fontconfig > >>because it was looking in /usr/X11R6/bin for freetype-config and > >>fontconfig-config, when freetype-config has moved to /usr/bin and > >>fontconfig-config was will altogether. > >> > >I thought we had decided to disable this support. Did that change? > > >I'm sorry... Nicholas and I were talking about this off-list and he >enabled it and seemed to think it worked okay, so I took his word for it >and enabled it. I can always disable it if it turns out to be horribly >broken. > Yeah, it would be great to have those conversations on-list next time. I assume they were just inseparably mixed in with the shared lesstif conversion discussion, which I guess was ok to have off list (although it might have been nice to see that too). So, ok. I wasn't as worried about it being broken :) as I was this (from http://www.cygwin.com/ml/cygwin-xfree/2003-09/msg00348.html): > My other concern is the additional link time dependencies this will add. > (Obviously, we would need to add additional setup.hint dependencies > too.) libtool enabled applications should just get it right via the > libXm.la file, but non libtool aware applications might break at compile > time if their configure scripts or the like are not smart enough. [snip] > Current Cygwin 1.3.22/Xfree 4.2.x libXm.la (0.93.41): > > # Libraries that this one depends upon. > dependency_libs=' -L/usr/X11R6/lib -lSM -lICE -lXt -lXp -lXext -lX11' > > Possible new Cygwin 1.5.x/Xfree 4.3.x libXm.la (0.93.91): > > # Libraries that this one depends upon. > dependency_libs=' -L/usr/X11R6/lib -lSM -lICE -lXt -lXp -lXext -lX11 > -lfreetype -lXft -lXrender -lfontconfig' > Our apps happen to be examples of those who don't use libtool and don't yet have configure scripts smart enough to take this into account. No big deal here; I'll fix them. But, I'm sure this change will generate some list traffic when apps that used to compile OOTB now don't. We'll see... -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: freetype2, fontconfig, and rebuild of dependent packages coming shortly
Well, I sent this last night before the new lesstif release, but somehow it evaporated. -- Forwarded message -- Date: Tue, 28 Oct 2003 17:49:30 -0600 (CST) From: Brian Ford <[EMAIL PROTECTED]> To: cygx <[EMAIL PROTECTED]> Subject: Re: freetype2, fontconfig, and rebuild of dependent packages coming shortly On Tue, 28 Oct 2003, Harold L Hunt II wrote: > I ran into an issue at the last minute when I looked at the LessTif > rebuild and realized that it was not using freetype and fontconfig > because it was looking in /usr/X11R6/bin for freetype-config and > fontconfig-config, when freetype-config has moved to /usr/bin and > fontconfig-config was will altogether. > I thought we had decided to disable this support. Did that change? >From http://www.cygwin.com/ml/cygwin-xfree/2003-09/msg00441.html : Additionally, I have disabled the experimental Xft support for antialiased fonts using freetype/fontconfig that was enabled by default in this release. For details about this choice, see: http://www.cygwin.com/ml/cygwin-xfree/2003-09/msg00348.html Feedback about this issue is welcomed and should be directed to the cygwin-xfree mailing list mentioned at the end of this announcement. And: Changes: * configure.in (AC_FIND_XFT): Disable Keith Packard's experimental Xft support. Thanks. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: freetype2, fontconfig, and rebuild of dependent packages coming shortly
On Tue, 28 Oct 2003, Harold L Hunt II wrote: > I ran into an issue at the last minute when I looked at the LessTif > rebuild and realized that it was not using freetype and fontconfig > because it was looking in /usr/X11R6/bin for freetype-config and > fontconfig-config, when freetype-config has moved to /usr/bin and > fontconfig-config was will altogether. > I thought we had decided to disable this support. Did that change? >From http://www.cygwin.com/ml/cygwin-xfree/2003-09/msg00441.html : Additionally, I have disabled the experimental Xft support for antialiased fonts using freetype/fontconfig that was enabled by default in this release. For details about this choice, see: http://www.cygwin.com/ml/cygwin-xfree/2003-09/msg00348.html Feedback about this issue is welcomed and should be directed to the cygwin-xfree mailing list mentioned at the end of this announcement. And: Changes: * configure.in (AC_FIND_XFT): Disable Keith Packard's experimental Xft support. Thanks. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: http://lesstif.sourceforge.net/INSTALL.html#compile_Windows
Sorry, Harold. I've been really busy today, and I'm a DLL dunce. I've been trying to wrap my head around the problem so as to offer something useful. I understand the basic issues involved and could see the problem after the lesstif list responded with that FAQ entry. But, I don't know enough about how/why DLLs require all symbols to be resolved to offer a work around. I'll keep looking... In the mean time, if we could produce a list of the symbols involved, that would make things go smoother when we do find a solution. On Mon, 27 Oct 2003, Harold L Hunt II wrote: > Brian, > > Sounds like we are going to have more trouble with Xt and LessTif. > Torrey Lyons sent me a great description of the problem on OS X (I > believe I forwarded it to the list). It boils down to Xt having some > unresolved symobls that we resolve at link time by linking to ICE and SM > (these libraries provide the default functions). However, other > libraries are supposed to be able to override these functions with their > own implementations, which the linker is expected to figure out. As we > all know, DLLs cannot have unresolved symbols, thus this functionality > is lost. We would need to provide an alternative to this behavior or > attempt to modify the linker to provide this functionality. > > In the meantime this means that the shared build of Xt doesn't work. > This is probably causing some of the weird problems people have noticed > with keyboard focus. This also explains why some types of LessTif apps > don't work anymore. > > We should probably revert to a static Xt and LessTif for the time being. > I know, this is not desireable, but it is probably going to take > months for this to be fixed and we can't have broken libs and apps for > the duration. > > Thoughts? > -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: XFree86 for cygwin installation hanging
On Mon, 27 Oct 2003, Paul Thomas wrote: > Invoking XWin, with any combination of arguments results in the > background coming up but nothing else. > FYI, this is normal behavior. You need to launch a window manager (like twm) unless you are using the -multiwindow switch. Then, you might also want to launch a client or two (like xterm). -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: http://lesstif.sourceforge.net/INSTALL.html#compile_Windows
On Fri, 24 Oct 2003, Harold L Hunt II wrote:
> Brian Ford wrote:
> > IIRC, you first rebuilt lesstif without removing --disable-shared, then
> > you remembered and tried a rebuild with --enable-shared. But I think you
> > didn't supply all the correct linker flags and got unresolved symbols. So
> > you gave in temporarily and shipped the resulting static libs because mwm
> > worked for you with them?
> >
> > Thus, I thought you expected those static libs to work, at least until we
> > fixed the shared build issue.
>
> I can see how you would have thought that. What really happened was
> that I got confused about whether the build was successful or not,
> installed it, ran mwm, everything worked, so I shipped it. Then I
> looked in the package and noticed there were no DLLs. Upon inspecting
> the build log I saw that the missing link flags were preventing them
> from being build. Upon adding the missing link flags there were still
> lots of build problems that had to be resolved in order to build shared
> libraries. That is where Nicholas and I started working on it and he
> finished up getting the shared libraries built plus he included bug
> fixes from lesstif's CVS tree. The new version should work without
> problems.
>
Ok, understood.
Bad news though, maybe. I just tried the binary package you posted, and
assuming I didn't make an installation error, I still get those
XmeTraitSet errors with our apps.
I was in a rush though, and I am just about instantaneously headed out of
town for the weekend, so this is just a heads up. I'll restle with it
again on Monday.
> >>>BTW, I still can't reproduct the Close bug because I still can't get mwm
> >>>to let me move a window, or pop up a menu from the title bar. This is
> >>>strange because it happens to me with stock lesstif/XFree86 on both NT4
> >>>and XP. I guess nobody else see this?
> >>
> >>Hmm... I still can't reproduce the problem of not being able to move a
> >>window. You have tried running with both "-rootless" and without any
> >>flags at all right (which would run in windowed mode. You aren't using
> >>-multiwindow when testing mwm, right? That might cause the sort of
> >>problem you are describing.
> >>
> >
> > I didn't try "-rootless". Just:
> >
> > Xwin.exe& ; mwm&
> >
> > from a bash prompt.
>
> With all of the weirdness about bash lately, perhaps you should edit
> startxwin.bat and try from there instead? Or at least try it from a
> straight command prompt (after running 'set DISPLAY=127.0.0.1:0.0' and
> setting the PATH as in startxwin.bat).
>
Just tried your new shared linked mwm with a modified startxwin.bat run
from Start->Run. Same results. I'll look again on Monday.
One other note. cygcheck /usr/X11R6/bin/mwm:
[EMAIL PROTECTED] ~/v9win/util/host
$ cygcheck /usr/X11R6/bin/mwm.exe
G:/cygwin/usr/X11R6/bin/mwm.exe
G:/cygwin/usr/X11R6/bin\cygXm-2.dll
G:/cygwin/usr/X11R6/bin\cygX11-6.dll
G:\cygwin\bin\cygcygipc-2.dll
G:\cygwin\bin\cygwin1.dll
D:\WINNT\System32\KERNEL32.dll
D:\WINNT\System32\ntdll.dll
G:/cygwin/usr/X11R6/bin\cygXft-2.dll
G:/cygwin/usr/X11R6/bin\cygXext-6.dll
G:/cygwin/usr/X11R6/bin\cygfontconfig-1.dll
G:/cygwin/usr/X11R6/bin\cygfreetype-9.dll
G:\cygwin\bin\cygexpat-0.dll
G:/cygwin/usr/X11R6/bin\cygXp-6.dll
G:/cygwin/usr/X11R6/bin\cygXrender-1.dll
G:/cygwin/usr/X11R6/bin\cygXt-6.dll
G:/cygwin/usr/X11R6/bin\cygICE-6.dll
G:/cygwin/usr/X11R6/bin\cygSM-6.dll
Are those mixed slashes normal and ok?
--
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax: 314-551-8444
Re: http://lesstif.sourceforge.net/INSTALL.html#compile_Windows
On Fri, 24 Oct 2003, Harold L Hunt II wrote: > Brian Ford wrote: > > Um..., great! But..., I wasn't *just* trying to get a shared build, or > > *just* trying to fix mwm's Close bug. At least with your new static lib > > build (lesstif-0.93.91-2), none of our apps work anymore. They all die > > with error messages like I quoted below. > > The -2 build was borked. I linked the static versions of the libs > against the shared version of Xt, this is why it fails to work properly. > I got confused during the packaging and forgot to switch the libs to > shared. > IIRC, you first rebuilt lesstif without removing --disable-shared, then you remembered and tried a rebuild with --enable-shared. But I think you didn't supply all the correct linker flags and got unresolved symbols. So you gave in temporarily and shipped the resulting static libs because mwm worked for you with them? Thus, I thought you expected those static libs to work, at least until we fixed the shared build issue. > The new -3 build uses shared libs and everything should be fine again. > > > Any chance you/Nicholas did something to fix these too? Any chance of > > previewing that package to see if it WFU (that would be "Works For Us") > > :)? > > Yes, see above. > Good, that's all I wanted to know. I'm content to wait for the release now that I know there's a good chance it will fix my problem. I was just trying to debug something I didn't think was fixed before the next release. > As for a WFU, I don't want to publish Nicholas's package address, but I > have uploaded the binary and source packages here: > > http://www.msu.edu/~huntharo/cygwin/lesstif/lesstif-0.93.91-3.tar.bz2 > (3.1 MiB) > http://www.msu.edu/~huntharo/cygwin/lesstif/lesstif-0.93.91-3-src.tar.bz2 > (2.98 MiB) > Thanks. I guess I'll test them anyway since you have kindly posted them. It's the least I can do. > I am almost done with a rebuild of the source package on my machine. I > will post the packages afterwards if the build completes. > Ok. > > BTW, I still can't reproduct the Close bug because I still can't get mwm > > to let me move a window, or pop up a menu from the title bar. This is > > strange because it happens to me with stock lesstif/XFree86 on both NT4 > > and XP. I guess nobody else see this? > > Hmm... I still can't reproduce the problem of not being able to move a > window. You have tried running with both "-rootless" and without any > flags at all right (which would run in windowed mode. You aren't using > -multiwindow when testing mwm, right? That might cause the sort of > problem you are describing. > I didn't try "-rootless". Just: Xwin.exe& ; mwm& from a bash prompt. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: http://lesstif.sourceforge.net/INSTALL.html#compile_Windows
On Fri, 24 Oct 2003, Harold L Hunt II wrote: > Brian, > > Actually, Nicholas Wourms and I got a shared build working. He has > posted the package for me to review and I will try to upload it tonight > if I get a chance. He also included bug fixes that are in lesstif's > CVS, so mwm's 'Close' menu item seems to be working again. > Um..., great! But..., I wasn't *just* trying to get a shared build, or *just* trying to fix mwm's Close bug. At least with your new static lib build (lesstif-0.93.91-2), none of our apps work anymore. They all die with error messages like I quoted below. Any chance you/Nicholas did something to fix these too? Any chance of previewing that package to see if it WFU (that would be "Works For Us") :)? BTW, I still can't reproduct the Close bug because I still can't get mwm to let me move a window, or pop up a menu from the title bar. This is strange because it happens to me with stock lesstif/XFree86 on both NT4 and XP. I guess nobody else see this? > Brian Ford wrote: > > > As an intermediate step, I am trying a static lesstif build with the new > > shared Xt/Xmu, etc. I am getting the followin message on startup of an > > application that previously worked fine: > > This happens with your stock lesstif-0.93.91-2 package. > > Warning: XmManager ClassInitialize: XmeTraitSet failed > > > > Error: attempt to add non-widget child "DropSiteManager" to parent "he" > > which supports only widgets > > And then the app dies. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
http://lesstif.sourceforge.net/INSTALL.html#compile_Windows
> Windows > > On windows using Cygwin, U/WIN or Interix, LessTif must be built as > static libraries. Because, one of the biggest issues with X on Win32 is > the moronic DLL format. Specifically - it is not possible to export > data from a Win32 DLL in a form that can be used to statically > initialize another global variable. Data access from a DLL requires at > least one pointer indirection, and hence executable code. This is why > X11R6 doesn't have DLLs for Xt/Xmu/Xaw (and Motif) on Win32. > Not exactly true on Cygwin anymore because of the following hack: http://www.cygwin.com/ml/cygwin-xfree/2003-10/msg00173.html I am still trying to shake out a working lesstif DLL from this, but I thought I would ask two questions that might help speed this up. Does anyone remember what variables specifically this effects? Is _XtInherit() the only one? As an intermediate step, I am trying a static lesstif build with the new shared Xt/Xmu, etc. I am getting the followin message on startup of an application that previously worked fine: Warning: XmManager ClassInitialize: XmeTraitSet failed Error: attempt to add non-widget child "DropSiteManager" to parent "he" which supports only widgets Still digging in lesstif source to find out what this means and where to go from here, but any comments/suggestions would be greatly appreciated. Thanks. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: Installation Problems: XFree-icons-bin
On Thu, 24 Oct 2003, Brett Wildermoth wrote: > When installing the complete cygwin package, the install frezees at > XFree-icons-bin post install. > Please search the archives before posting. This issue has been beaten to death. If you are using a reasonably up to date mirror, it should already have the new version of bash that fixes this problem. See the following thread and its thread link for more information if you really want to: http://www.cygwin.com/ml/cygwin/2003-10/msg01309.html -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
