RE: non-widget child DropSiteManager error (WAS: RE: Grace (xmgrace) 5.1.12-1 ... )
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 packagerelease.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.
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.
# print a brief help message
help(){
echo Cygwin installation script $0
echo special instructions for this particular package if necessary?
echo Options:
echohelp: Print this message.
echoprep: Prepare the Cygwin patched version of the source.
echomkdirs: Make the directory heirarchy needed. ?...
echoconf: Run the configure script with suggested options for
Cygwin
echobuild: Compile the package from the source code
echocheck:
echoclean: Remove files produced by configuring and building
echoinstall:
echostrip: Remove extra symbols from the compiled package
echopackage:
echopkg:
echomkpatch:
echosrc-package:
echospkg:
echofinish:
echosigfile:
echochecksig:
echoall:
}
# end
case $1 in
help) help; STATUS=$?;;
prep) prep ; STATUS=$? ;;
mkdirs) mkdirs; STATUS=$? ;;
conf) conf ; STATUS=$? ;;
build)build ; STATUS=$? ;;
check)check ; STATUS=$? ;;
clean)clean ; STATUS=$? ;;
install) install ; STATUS=$? ;;
strip)strip ; STATUS=$? ;;
package) pkg ; STATUS=$? ;;
pkg) pkg ; STATUS=$? ;;
mkpatch) mkpatch ; STATUS=$? ;;
src-package) spkg ; STATUS=$? ;;
spkg) name=$0 text=SCRIPT sigfile; spkg ; STATUS=$? ;;
finish) finish ; STATUS=$? ;;
sigfile) sigfile ; STATUS=$? ;;
checksig) checksig ; STATUS=$? ;;
all) prep conf build install \
strip pkg name=$0 text=SCRIPT sigfile spkg \
finish echo All finished! ; \
STATUS=$? ;;
*) echo Error: bad arguments ; exit 1 ;;
esac
RE: non-widget child DropSiteManager error (WAS: RE: Grace (xmgrace) 5.1.12-1 ... )
Can you tell me the date/title of the announcement? I think it was a while before I started reading this list, and Harold is so active that I so far could not find it in the archives. ** 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
RE: non-widget child DropSiteManager error (WAS: RE: Grace (xmgrace) 5.1.12-1 ... )
To ask a simple question: When are the dll supposed to get created during the build/install process? *duh* okay -- I did not look in the *-announce archives. But I did see this same text in the lesstif.README of the distribution. Maybe I did not understand it... I interpret these points (Port notes) as referring to things that Harold has already done for this version, not something that the user has to do. Is this incorrect? It seemed to work for Harold anyways, he has generated a package. Why are you trying to build it yourself? Obviously I must be a masochist with a need to waste time. :-D See the following reference for some details: http://sources.redhat.com/ml/cygwin-xfree/2003-10/msg00401.html Okay, that explains something. Did you make sure that this step from Harold's lesstif announcement worked? No, in fact I am sorry but I still don't understand what you are asking. I do have the up-to-date build tools, as of that day that Harold posted 0.93.91-6 , unless I am completely missign something. There were no complaints from the confiure/build script though. dlltool is installed, the command for creating dll seems to be located in ltmain.sh , I don't see any messages saying that it failed. I just don't get dll's How should one 'check if (all these steps) worked'? I would expect it to fail with certain messages if it didn't work. Is there any other step *necessary* besides: 1 change the script to have --enable-debug --enable-shared --disable-static flags 2 ./lesstif-0.93.91-6.sh prep 3 ./lesstif-0.93.91-6.sh conf 4 ./lesstif-0.93.91-6.sh build 5 ./lesstif-0.93.91-6.sh install 6 then using the result in the .install directory? I used ./lesstif-0.93.91-6.sh all the first time I tried it, with identical results (except I had to untarbz the results, and debug was not enabled) I have not looked into creating a setup.ini, is this where the .dll get created? Or to ask a very uncomplicated question: When are the dll supposed to get created in the build/install process? Given this information I may be able to see why it is not happening on my system. I am going to move this question to the top of this message so maybe people will see it instead of having to read down to this point! Thanks, Robert -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Fraser Sent: 21 January 2004 12:56 To: [EMAIL PROTECTED] Subject: Re: non-widget child DropSiteManager error (WAS: RE: Grace (xmgrace) 5.1.12-1 ... ) Atwood, Robert C wrote: Can you tell me the date/title of the announcement? I think it was a while before I started reading this list, and Harold is so active that I so far could not find it in the archives. Updated: lesstif-0.93.91-6 01/16/2004 07:13 AM ** 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
RE: non-widget child DropSiteManager error (WAS: RE: Grace (xmgrace) 5.1.12-1 ... )
Well, I believe that something like 'You have to directly edit the package.sh script in order to alter the configuration options, which are passed to the configure script, such as --enable-debug or --enable/disable-static' would/should be included there. Also since ./configure --help ususally provides information about what options/environment variables are available or used, and the Cygwin build script makes this step essentially opaque to the user, I feel that the responsibility for providing this also gets transferred to the Cygwin build script. Perhaps the 'help' function would also simply call the configure script for the package and echo back the help options from it. I will see if I can do this at least before sending a patch to the address you mention. I though you meant 'what does documentation mean', like very sarcastic! Method 2 link: I see what you mean, and I did glance at this before -- but not in great detail because it is mostly about how to create the package but not much about how to use the package once it is created. In the 'canned instructions' it only mentions using the 'all' option , it does not mention the sub-options such as prep, build,conf ... only because Harold mentioned it did I get the idea that these other options exist. (then trying to read the script ) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brian Ford Sent: 21 January 2004 16:09 To: [EMAIL PROTECTED] Subject: 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 packagerelease.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 ... )
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. Is there another way to get a debug-compiled version other than building it myself? 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. Please see the archived thread on 'Grace (xmgrace) 5.1.12-1 ... ' for much greater detail on this (including backtraces, etc) 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? 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) 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.) Thanks for your help Robert -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brian Ford Sent: 19 January 2004 22:45 To: [EMAIL PROTECTED] Subject: 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: non-widget child DropSiteManager error (WAS: RE: Grace (xmgrace) 5.1.12-1 ... )
No huge rush, I am getting the graphing I want done using Grace on a linux box, no reason other than a bit of convenience to do it on a window/cygwin installation.. 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 package.sh all 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) 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. 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?) 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 -lXp -lXmu -lXt -lXext -lX11 -lSM -lICE -lXft -lfontconfig -lXrender ../cephes/libcephes.a ../T1lib/libt1.a -ltiff -ljpeg -lpng -lz -lm Thanks again. Dr. Robert Atwood Research Associate Dept. of Materials Imperial College London London, UK -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brian Ford Sent: 20 January 2004 17:24 To: [EMAIL PROTECTED] Subject: 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
RE: non-widget child DropSiteManager error (WAS: RE: Grace (xmgrace) 5.1.12-1 ... )
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. At first I tried buildign the lesstif by manually runing ./configure and make but this did not work. This is a list all the files called Xm that got installed : /usr/X11R6$find . -name '*Xm\.*' ./lib/libXm.la ./lib/libXm.a ./include/Xm/Xm.h Thanks again Robert -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brian Ford Sent: 20 January 2004 18:54 To: [EMAIL PROTECTED] Subject: 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 package.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 package.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 ... )
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. I am trying again with the --enable-static removed ; or do you actually have to specify --disable-static? Is this documented somewhere? 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.
non-widget child DropSiteManager error (WAS: RE: Grace (xmgrace) 5.1.12-1 ... )
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? Thanks Robert -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Atwood, Robert C Sent: 19 January 2004 11:20 To: [EMAIL PROTECTED] Subject: RE: Grace (xmgrace) 5.1.12-1 graph program -- building under cygwin -- possibly LessTif bug from 0.93.91 ? Thanks again Harold -- This is getting to be a steadily decreasing priority for me so don't rush to solve my problems at the expense of those interviews. I can easily transfer the data to a Linux box and use my patched Grace from there to get the tick marks -- at this point the only reason to pursue this is to learn how, maybe I can even locate the bug ( with a little help) ... I imagine that several other people also know the answers to these questions as they are getting more general. I have had no problem doing the same things on a Linux box, so it seems that it is the differences between Linux (Red Hat 9, Red Hat 8, and Slackware 8.1) and Cygwin that are messing me up. You need at least the following packages to build grace and lesstif: fontconfig libfontconfig1 libfontconfig-devel XFree86-prog Harold I have those, but I cannot figure out how to get Configure to pick them up. That is, I can compile the little test routine (as used by configure to test the M*tif installation) from the command line by including all the -l flags for these libraries directly but graceversion/configure always fails because it is not including those flags. ( I figured this out since last time I posted here...the libraries were all there,somewhere, just not referenced by -l flags ) -lXft -lfontconfig -lXrender in addition to those mentioned by default I tried adding them in the environment variable LDFLAGS but that didn't work either -- possibly they are in the wrong order. The LDFLAGS seems to get put before the -I flags and before the other libraries. Is there some cygwin equvalent of ldconfig or ld.so.conf that I am missing out here? Or does the grace-version/configure script need some changes to use a compiled LessTif instead of packaged binaries? (this is what I will probably try next) I have had some confusion in the past about this, on Cygwin certain libraries getting automatically referenced .. when does a library not explicitly referenced by a -l flag get automatically referenced? --Robert -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Harold L Hunt II Sent: 16 January 2004 20:41 To: [EMAIL PROTECTED] Subject: Re: Grace (xmgrace) 5.1.12-1 graph program -- building under cygwin -- possibly LessTif bug from 0.93.91 ? Robert, You need at least the following packages to build grace and lesstif: fontconfig libfontconfig1 libfontconfig-devel XFree86-prog Harold
rcs-id tags in Cygwin source differ from the source code ? (Was: RE: Grace (xmgrace) 5.1.12-1 graph program -- building under cygwin -- possibly LessTif bug from 0.93.91 ?)
Even stranger ... the LessTif 0.93.91-6 source seems to contain the fix in SeparatoG.c but the cvs / rcsid tag does not agree with the number for the version that contains this fix. This does not explain why it does not work. Still it is a source of confusion -- defeating the purpose of the rcs id tags. Apologies for the misunderstanding engendered by my reading the tag numbers for this file. -- Robert -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Atwood, Robert C Sent: 16 January 2004 13:41 To: [EMAIL PROTECTED] Subject: RE: Grace (xmgrace) 5.1.12-1 graph program -- building under cygwin -- possibly LessTif bug from 0.93.91 ? In fact, it took about 8 hours; Well I am not going to even begin to discuss how much time I have just spent trying to get the minor tick marks to point the other way from the major tick marks, of which only the first 10 minutes was actually changing the tick marks code in the Grace source. Who said debugging free software was a thankless task? 0.93.91-6 - Nope. doesn't work. Since I had to go looking for a mirror with newer updates (mirror.ac.uk doesn't have the new stuff yet) I also found a newer build of Grace, 5.1.14-1 and the stock install crashes (where the old one did not) The internal help shows it was built with 0.93.91 Something I would really like to understand: why should the 5.1.12 build with the older LessTif NOT crash when running with the newer LessTif libraries installed? If the bug is in the LessTif function and the (shared object? dll?) is the buggy one, shouldn't it crash? 0.93.94-1 - Grace Compiles but does not run. The error: Error: attempt to add non-widget child DropSiteManager to parent xmgrace which supports only widgets Warning: XmManager ClassInitialize: XmeTraitSet failed Harold: Hope you are feeling better soon and good luck with the degree; thanks for trying the build. Detective work of my own: According to the source package I downloaded from cygwin.matrix.com.br (only one I found that seems to be updated with the source) for lesstif-0.93.91-6, the file where the bug happens (SeparatorG.c) has only been patched up to 1.25 (October 6) but the bug was not fixed until 1.26 (Nov. 27) (see copied messages below) I am going to try patching the source and building 0-93-91(patched) myself, but I have not had very good luck so far building any packages under Cygwin (Grace is the only one I tried so far!) , so it may take even more than 8 hours. All for those stupid little tick marks :-() --Robert ** Revision 1.26 - (download), view (text) (markup) (annotate) - [select for diffs] Thu Nov 27 19:13:06 2003 UTC (7 weeks ago) by dannybackx CVS Tags: release_0_93_94, HEAD Changes since 1.25: +3 -3 lines Diff to previous 1.25 Auch - this bug was not yet fixes. Fixes bug # 849599. ** Date: 2003-11-27 11:16 Sender: dannybackx Logged In: YES user_id=39146 Auch. I was wrong. I missed one case. The bug was still in CVS until a couple of minutes ago. I'll create a new release of LessTif shortly to address this. Apologies for the confusion. ** -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Harold L Hunt II Sent: 16 January 2004 05:20 To: [EMAIL PROTECTED] Subject: Re: Grace (xmgrace) 5.1.12-1 graph program -- building under cygwin -- possibly LessTif bug from 0.93.91 ? Robert, Atwood, Robert C wrote: Dear Harold and others: lesstif is the stock version. Also, I reinstalled all my Cygwin earlier today. $cygcheck -c lesstif Package Version Status lesstif 0.93.91-5 OK Comparing the backtrace from this problem and the other problem, it really looks like the same bug to me. Can the 'stock' lesstif be updated to 0.93.94? I thought I had seen the last of that bug a couple of months ago :~O Well, it wasn't simple. In fact, it took about 8 hours; granted, probably 4 of that was for making clean ups that the lesstif package has needed for a long time. I built lesstif-0.93.94, but it doesn't work well. nedit crashes when opening file dialogs. I'm trying a rebuild of it now to see if having 0.93.91 installed while building 0.93.94 was causing problems. The alternative solution I came up with was to apply the patch for the bug number you listed to my 0.93.91 source. That seems to be stable. However, you'll have to report whether it fixes your bug or not. I am going to post my 0.93.94 package as a 'test' release, even if it does not work
RE: Grace (xmgrace) 5.1.12-1 graph program -- building under cygwin -- possibly LessTif bug from 0.93.91 ?
Sorry, I guess you missed the more detailed description, gdb backtraces, etc? I shouldn't have change the subject to BACKTRACE: When certain dialog boxes are opened, including (but not only) 'Plot|Axis properties ...' the program crashes. Opening some other boxes eg 'Plot|Plot appearance ... ' does not cause the crash. Double-clicking the axis causes the crash. The console in which it was running reports that it got SIGSYS and says it may have something to do with the graphic (but I think that is because the signal numbers are different? GDB says it gets SIGSEGV segmentation fault) The back trace with 5-1-12-1 rebuilt with debug (-g) is copied below. But LessTif seems not to have been build with -g and I am having trouble building this myself. The same behaviour occurs with the new 5-1-14 package and the new LessTif-0-93-91-6 , so my guess that it was the same bug in XGetCValues that I encountered in November may be totally wrong. Which LessTif did you install and get it to work? Did you try opening some dialog boxes or just start the test routine? The test routine works because it never opens those dialog boxes. --Robert Program received signal SIGSEGV, Segmentation fault. 0x10032103 in cygX11-6!XGetGCValues () from /usr/X11R6/bin/cygX11-6.dll (gdb) bt #0 0x10032103 in cygX11-6!XGetGCValues () from /usr/X11R6/bin/cygX11-6.dll #1 0x00773946 in cygXm-2!_XmArrowBG_TraitAddCallback () from /usr/X11R6/bin/cygXm-2.dll #2 0x009f5ecc in cygXt-6!XtSetSensitive () from /usr/X11R6/bin/cygXt-6.dll #3 0x009f64cb in cygXt-6!XtSetValues () from /usr/X11R6/bin/cygXt-6.dll #4 0x00a09fb8 in cygXt-6!XtVaSetValues () from /usr/X11R6/bin/cygXt-6.dll #5 0x0047f6ab in _fu59___XmStrings () at motifutils.c:734 #6 0x004aaeae in create_axes_dialog (axisno=-1) at tickwin.c:212 #7 0x004aa6f2 in create_axes_dialog_cb (data=0x0) at tickwin.c:135 #8 0x0047fddc in button_int_cb_proc (w=0x1013d098, client_data=0x1013d500, call_data=0x22f8c0) at motifutils.c:962 #9 0x009d26b3 in cygXt-6!XtCallCallbackList () from /usr/X11R6/bin/cygXt-6.dll #10 0x007d0377 in cygXm-2!XmSetWMProtocolHooks () #11 0x00a06f41 in cygXt-6!_XtMatchAtom () from /usr/X11R6/bin/cygXt-6.dll #12 0x00a073e9 in cygXt-6!_XtMatchAtom () from /usr/X11R6/bin/cygXt-6.dll #13 0x00a0797b in cygXt-6!_XtTranslateEvent () from /usr/X11R6/bin/cygXt-6.dll #14 0x009e0165 in cygXt-6!XtDispatchEventToWidget () from /usr/X11R6/bin/cygXt-6.dll #15 0x009e0c6f in cygXt-6!_XtOnGrabList () from /usr/X11R6/bin/cygXt-6.dll #16 0x009e0ebf in cygXt-6!XtDispatchEvent () from /usr/X11R6/bin/cygXt-6.dll #17 0x009e13e4 in cygXt-6!XtAppMainLoop () from /usr/X11R6/bin/cygXt-6.dll #18 0x004b7006 in _fu1053__XtShellStrings () at xmgrace.c:1187 #19 0x00403b5f in main (argc=1, argv=0x100f2538) at main.c:717 (gdb) Program received signal SIGSEGV, Segmentation fault. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Volker Quetschke Sent: 16 January 2004 15:21 To: [EMAIL PROTECTED] Subject: Re: Grace (xmgrace) 5.1.12-1 graph program -- building under cygwin -- possibly LessTif bug from 0.93.91 ? Hi! 0.93.91-6 - Nope. doesn't work. Since I had to go looking for a mirror with newer updates (mirror.ac.uk doesn't have the new stuff yet) I also found a newer build of Grace, 5.1.14-1 and the stock install crashes (where the old one did not) The internal help shows it was built with 0.93.91 Yes, I made the package yesterday, and I didn't write an announcement yet. I could just recreate your crash, it said cygXm-2.dll is missing. After installing lesstif it works. I'm sorry for that, I'll report to cygwin-apps now and add the dependency to the setup.hint file. Besides this small problem xmgrace seems to work. For me. Something I would really like to understand: why should the 5.1.12 build with the older LessTif NOT crash when running with the newer LessTif libraries installed? If the bug is in the LessTif function and the (shared object? dll?) is the buggy one, shouldn't it crash? Can you describe what crash you are seeing? It doesn't sound like an alert box saying a dll is missing. Volker -- If you like my work consider: http://www.scytek.de/donations.html PGP/GPG key (ID: 0x9F8A785D) available from wwwkeys.de.pgp.net key-fingerprint 550D F17E B082 A3E9 F913 9E53 3D35 C9BA 9F8A 785D
How do I build LessTif packagef?
How do I build the LessTif package myself?
I have tried:
./lesstif-0.93.91-6 all
followed by
tar -jxvf /usr/src/lesstif-0.93.91-6.tar.bz2
still the configure for another program (Grace) cannot find the M*tif
libraries
It seems the dll's are not created, just .a files? I followed the
instructions in CYGWIN-PATCHES/lesstif.README but it does not mention
anything beyond running
{package}.sh all
, which creates the {package}.tar.bz2 file, what is supposed to happen
next? How do I get the dll from the library files?
Which part of the FAQ didn't I read? Maybe I just didn't understand it?
Also how do I build it with debugging (-g) and not stripping the
binaries?
I also tried:
./lesstif-0.93.91-6 prep
configure
make
... that did not work!
Thanks,
Robert
RE: Grace (xmgrace) 5.1.12-1 graph program -- building under cygwin -- possibly LessTif bug from 0.93.91 ?
Thanks for the info. I am guessing that these stages are all rolled into
{package}.sh all
Is my problem something else entirely??? I think perhaps it is.
The problem is: when I configure Grace it exits on
Error: M*tif has not been found.
Looking at config.log, there are several 'undefined reference' errors
from libXm.a that seem to have something to do with fonts eg.
_FcPatternCreate
_XftFontOpenPattern
_XftFontClose
So it IS fiding libXm.a, but not certain other libraries needed by this
library. I am guessing that Xft* functions are in libXft,
I have cygXft-[12].dll and libXft-[12].dll.a located in
/usr/X11R6/[bin,lib] , but no *.a version of these librarys, is this the
problem? How can configure locate/use these correctly?
Thanks!
Robert
You build lesstif as follows:
1) cd /usr/src
2) ./lesstif-0.93.94-1.sh prep
3) ./lesstif-0.93.94-1.sh conf conf.log 21
4) ./lesstif-0.93.94-1.sh build build.log 21
5) ./lesstif-0.93.94-1.sh install install.log 21
6) ./lesstif-0.93.94-1.sh strip
7) ./lesstif-0.93.94-1.sh pkg
8) ./lesstif-0.93.94-1.sh spkg
You will then have a new lesstif package that you can install by
creating a new setup.ini file. You'll have to ask or search for help on
that. You will need some scripts called upset to do this.
Harold
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Harold L Hunt II
Sent: 16 January 2004 17:59
To: [EMAIL PROTECTED]
Subject: Re: Grace (xmgrace) 5.1.12-1 graph program -- building under
cygwin -- possibly LessTif bug from 0.93.91 ?
Oh, and your line to install manually via tar is missing a -C /:
tar xjf -C / lesstif-0.93.91-6.tar.bz2
I think that will tell it to extract in the root of your Cygwin
installation so the files will go to the correct place.
Harold
RE: Grace (xmgrace) 5.1.12-1 graph program -- building under cygwin -- possibly LessTif bug from 0.93.91 ?
Dear Harold and others: lesstif is the stock version. Also, I reinstalled all my Cygwin earlier today. $cygcheck -c lesstif Package Version Status lesstif 0.93.91-5 OK Comparing the backtrace from this problem and the other problem, it really looks like the same bug to me. Can the 'stock' lesstif be updated to 0.93.94? I thought I had seen the last of that bug a couple of months ago :~O -- Robert backtrace from this problem * Program received signal SIGSEGV, Segmentation fault. 0x10032103 in cygX11-6!XGetGCValues () from /usr/X11R6/bin/cygX11-6.dll (gdb) bt #0 0x10032103 in cygX11-6!XGetGCValues () from /usr/X11R6/bin/cygX11-6.dll #1 0x00773946 in cygXm-2!_XmArrowBG_TraitAddCallback () from /usr/X11R6/bin/cygXm-2.dll #2 0x009f5ecc in cygXt-6!XtSetSensitive () from /usr/X11R6/bin/cygXt-6.dll * backtrace from previous problem in November 2003 Program received signal SIGSEGV, Segmentation fault. 0x402f1319 in XGetGCValues () from /usr/X11R6/lib/libX11.so.6 Current language: auto; currently c (gdb) bt #0 0x402f1319 in XGetGCValues () from /usr/X11R6/lib/libX11.so.6 #1 0x400d02f7 in set_values (old=0xbfffe8e0, request=0xbfffe5c0, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Harold L Hunt II Sent: 15 January 2004 19:54 To: [EMAIL PROTECTED] Subject: Re: Grace (xmgrace) 5.1.12-1 graph program -- building under cygwin -- possibly LessTif bug from 0.93.91 ? Robert, Please send in the results of cygcheck -c lesstif and report on whether you have built lesstif yourself or if you are using the stock lesstif package for Cygwin. I get the following output (which is the latest version): $ cygcheck -c lesstif Cygwin Package Information Package VersionStatus lesstif 0.93.91-5 OK Harold Atwood, Robert C wrote: Dear Cygwin-xfree people : I am trying to compile xmgrace with a few of my own (very minor) modifications and to run under Cygwin. I have already compiled it successfully on a Linux machine. However, I could not get it to run on Cygwin. So , I tried the basic source without my modifications -- even then, the executable I compile under Cygwin gives a SIGSYS (Signal 6) when trying to open certain (but not all) dialog boxes. The binary installed from Cygwin setup does not give this problem. This is the Grace-5.1.12 version. I had a similar problem with ddd on Linux using LessTif 0.93.91, and Danny fixed the problem in November. Is it possible that the same bug is causing this? Can the default LessTif be upgraded (or downgraded? ) The bug was #849599 and was fixed in version 0.93.94 (see LessTif bug database and forwarded reply below) However, if this were the problem, I still don't see why the downloaded binary should work but the compiled binary should not? They use shared libraries for LessTif, don't they? I used the following procedure: 1. use Cygwin setup to obtain the source archives 2. ./grace-5.5.12-1.sh prep 3. cd grace-5.5.12 4. ./configure 5. make 6. make tests during tests, opening the dialog boxes causes the fault 7. make install 8. make links 9. /usr/local/bin/xmgrace the same fault occurs. Here is some relevant information: Host: CYGWIN_NT-5.1 2003-09-20 16:31 1.5.5(0.94/3/2) i686 Time: Thu Jan 15 18:18:44 2004 GUI toolkit @(#)GNU/LessTif Version 2.1 Release 0.93.91 Xbae version: 4007 T1lib: 1.2.1p1-grace libpng:1.2.5 libjpeg:62 gcc 3.3.1 (cygming special) Thanks Robert Atwood -Original Message- From: Danny Backx [mailto:[EMAIL PROTECTED] Sent: 30 November 2003 09:22 To: [EMAIL PROTECTED] Subject: RE: Segfault when a gnuplot graph is closed? I've just released LessTif 0.93.94 to fix this bug. Download at http://sf.net/projects/lesstif Danny
