RE: What happened to xwinclip
Sterling Baker wrote: > I just installed to a new box and am unable to find 'xwinclip' in the available packages list. > Is this part of another package now or has it been replaced with something else? Part of the main XWin executable now. Make sure XWin is invoked (usually from startxwin.bat or startxwin.sh) with -clipboard. I still show an xwinclip package from the cygwin package search tool, though: http://cygwin.com/packages/ (enter xwinclip) but it's not necessary. -Richard Campbell. -- 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: port existing x windows application to win32
> Oh, please don't. This is a simple concept. There is nothing complicated here. > > If you build your program using Cygwin's gcc then your program is GPLed regardless of whether it is using X11 libraries. -m-no-cygwin? http://www.gnu.org/licenses/gpl-faq.html#CanIUseGPLToolsForNF -Richard Campbell. -- 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: port existing x windows application to win32
Michel Bardiaux wrote: > > Thomas Dickey wrote: > > > > (Perhaps you should discuss this on the regular cygwin mailing list). > > Not really possible, the trafic there is way too much for the time I have. Perhaps you should discuss this on the cygwin-licensing list, which is: 1) Designed specifically for cygwin-licensing discussions. 2) Extremely low volume (~16 messages in 2005). See http://cygwin.com/cygwin/lists.html and http://cygwin.com/ml/cygwin-licensing/ -Richard Campbell. -- 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: Firefox on cygwinX
Alan Hourihane wrote: On Wed, 2005-10-19 at 08:14 -0700, Charles Li wrote: > I look through the setup and can not find cl, I have all the gcc installed. What else do I need? Sounds like you have Visual C++ (or equivalent) installed and that's where the program 'cl' comes from. It will be in your environment. This is not right. The Firefox configure file ends up hardcoding cl if it detects a windows platform. You have to export CC/CXX/CPP variables to override cl. See http://citations.mozdev.org/mozilla-build-win32.html Cygwin-X is not a supported build target. Gerrit Haase was working on supporting Firefox on Cygwin-X. See this thread: http://www.cygwin.com/ml/cygwin-xfree/2005-08/msg00071.html -Richard Campbell. -- 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: X11 becomes unresponsive. VERY unresponsive.
> I don't recall any reported problems with Cygwin/X per se, but there is a > HUGE hyperthreading-related thread on the main Cygwin list -- you might do > well to check there. Here's an executive summary for the impatient: > unless someone tracks down the problem and fixes it, or donates a > hyperthreaded system that exhibits the problem to CGF, this won't get > fixed. You don't have to donate a whole system yourself - just send money to CGF through Paypal, (CGF address: me -at- cgf -dot- cx), and when/if there's enough, he'll get a hyperthreaded system. -Richard Campbell.
RE: emacs crash under X on XP
> However, I just reinstalled "all" last week and emacs still crashes >routinely. > >Here's what I get out of the setup.log for versions: > >current (crashes ongoing): >cygwin-1.5.7-1 >XFree86-bin-4.3.0-15 >XFree86-xserv-4.3.0-55 Have you tried updating to 1.5.8-1 or a snapshot? I was having crashes in 1.5.7-1 that went away when I upgraded to a pre-1.5.8 snapshot. The mailing list archives may also be helpful as I recall others having emacs problems that went away with pre-1.5.8 snapshots. -Richard Campbell.
RE: xwin not working for some with latest snapshot -- people with debugging skills needed
>The problem that is reported is that xwin won't start with the snapshot but >works with 1.5.7. Specifically, it was XFree86-xserv-4.3.0-44 && cygwin1-200402[05-18,21].dll fails. XFree86-xserv-4.3.0-44 && cygwin1-1.5.7-1.dll succeeds. In addition: XFree86-xserv-4.3.0-46 && cygwin1-20040221.dll fails. XFree86-xserv-4.3.0-46 && cygwin1-1.5.7-1.dll succeeds. But gdb also fails to start on the box with the cygwin1-200402[05-18,21].dll, making this problem somewhat difficult to track down. -Richard Campbell.
Re: #pragma inteface - was - RE: DDD 3.3.8 recipe - was - RE: lib tool created import libs broken? was RE: DDD 3.3.8 (i686-pc-cygwin) get s `Segmentation fault
>Related to "#pragma interface" and gang, could you submit a bug report >to the gcc folks ? Related to "#pragma interface", It appears to be a known problem: http://sources.redhat.com/ml/cygwin/2003-11/msg01066.html I do intend to push on it somewhat, as I agree that "#ifndef __CYWIN__" is certainly not a good long term plan (and even in the short term, it should be only done in the cygwin-specific package). Just haven't gotten the energy yet. -Richard Campbell.
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
>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... -Richard Campbell.
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
Resend - got denied because of attachment size, so I've uploaded my diffs to a web page. Ok, I think this is the quickest way to get a working (as far as I can tell, and I didn't play with it all that much, although I did load up the cxxtest.exe, set a breakpoint, run through, etc.) DDD 3.3.8 on cygwin: 1. Get the DDD 3.3.8 source and a gcc 3.3.x source. 2. Copy the gcc/include contents into ddd-3.3.8/include 3. Edit ddd-3.3.8/configure to remove the "old_archive_from_expsyms_cmds" variable (patch below, which is just in the cygwin section of configure): bash-2.05b$ diff -u ddd-3.3.8-orig/configure ddd-3.3.8/configure --- ddd-3.3.8-orig/configure2003-10-22 15:29:40.0 -0400 +++ ddd-3.3.8/configure 2003-12-05 11:34:05.948423800 -0500 @@ -9492,7 +9492,8 @@ else $CC -o impgen impgen.c ; fi)~ $output_objdir/impgen $dir/$soroot > $output_objdir/$soname-def' -old_archive_from_expsyms_cmds='$DLLTOOL --as=$AS --dllname $soname --def $output_objdir/$soname-def --output-lib $output_objdir/$newlib' +#old_archive_from_expsyms_cmds='$DLLTOOL --as=$AS --dllname $soname --def $output_objdir/$soname-def --output-lib $output_objdir/$newlib' +old_archive_from_expsyms_cmds= # cygwin and mingw dlls have different entry points and sets of symbols # to exclude. 4. bash ./configure 5. Edit all of ddd/*.C ddd/*.h to remove or guard all "#pragma interface" and "#pragma implementation" lines. 6. make 7. make install 8. run as normal. The usual disclaimers apply. I have included the output of: diff -u -r -N ddd-3.3.8-orig/ ddd-3.3.8 Available at: http://bellsouthpwp.net/u/l/ulvester/iffs.gz Feel free to play with it if the prospect of handediting 500 .C and .h files doesn't thrill you. -Richard Campbell.
RE: DDD 3.3.8 (i686-pc-cygwin) gets `Segmentation fault WAS Re: c ompiling DDD
bash-2.05b$ autoreconf --install --force 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. 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 bash-2.05b$ autoreconf --version autoreconf (GNU Autoconf) 2.59
RE: DDD 3.3.8 (i686-pc-cygwin) gets `Segmentation fault WAS Re: c ompiling DDD
Almost. When I figure out the minimum number of changes, I'll repost, and then test on the current (3.3.8) build. -Richard Campbell. >Does this result in a working version of ddd? If so, I can package it >up for Cygwin's setup.exe.
RE: DDD 3.3.8 (i686-pc-cygwin) gets `Segmentation fault WAS Re: c ompiling DDD
bash ./configure --disable-static Only got me halfway - if old_archive_from_expsyms_cmds has a value, it will override the "build_old_libs=no" option in libtool. Strange. -Richard Campbell.
RE: DDD 3.3.8 (i686-pc-cygwin) gets `Segmentation fault WAS Re: c ompiling DDD
>What version of libtool is ddd-3.3.8 using? Automatically generated by configure? I reconfigured with: bash ./configure --disable-static And libtool now has the settings I had hoped for - I'm running a make now, and I'm pretty confident that will work. Which would boil my steps down to (for 3.3.7): 1. Remove all "#pragma interface" and "#pragma implementation" lines. 2. Configure with: "bash ./configure --disable-static". 3. Make as usual. (For 3.3.8, add the following: 0. Copy gcc/include into libiberty/include, or whatever exactly Arnaud said ) -Richard Campbell.
RE: DDD 3.3.8 (i686-pc-cygwin) gets `Segmentation fault WAS Re: c ompiling DDD
>> 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. 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? Now, to configure, I suppose... -Richard Campbell.
RE: ddd compilation
Please keep replies on the cygwin-xfree mailing list. >I was wondering if you could send me the changes to the makefile needed to get >it to compile. What version of gcc are you using? 3.3.1? 3.3.1. I have described all the changes I have made. 1. If using ddd 3.3.8, get the include files from gcc as mentioned by Arnaud. I haven't done this, as I downgraded to ddd 3.3.7 for testing purposes. 2. Remove all "#pragma interface" and "#pragma implementation" lines. 3. Run make. Save off the output. You now have a segfaulting ddd.exe file. 4. Edit the last g++ line to remove the .libs/libcyg*.a libraries and to add -Xm, -Xt, etc., where appropriate. 5. Run that last g++ line again. -Richard Campbell.
RE: DDD 3.3.8 (i686-pc-cygwin) gets `Segmentation fault WAS Re: c ompiling DDD
>But first, I'll run that last g++ linking step for ddd after editing it to >remove those .libs >links. Yep. The following edited line produces a segfaulting binary: g++ -DNDEBUG -O2 -g -W -Wall -trigraphs -o ddd.exe ddd.o basename.o compare.o cook.o cwd.o glob.o UndoBuffer.o UndoBE.o WhatNextCB.o configinfo.o -L/usr/X11R6/lib .libs/libimp-cygXm-2.a -lXft -lXrender .libs/libimp-cygfontconfig-1.a .libs/libimp-cygfreetype-6.a -lz .libs/libimp-cygexpat-0.a -lXt -lXpm -lXp -lXext -lX11 -lSM -lICE -lncurses -ly ../libiberty/libiberty.a -Wl,--rpath -Wl,/usr/X11R6/lib -Wl,--rpath -Wl,/usr/X11R6/lib And the following edited line produces a running (at least for simple test, breakpoint, step through, browse source, etc.) binary: g++ -DNDEBUG -O2 -g -W -Wall -trigraphs -o ddd.exe ddd.o basename.o compare.o cook.o cwd.o glob.o UndoBuffer.o UndoBE.o WhatNextCB.o configinfo.o -L/usr/X11R6/lib -lXm -lXt -lXpm -lXp -lXext -lX11 -lSM -lICE -lncurses -ly ../libiberty/libiberty.a -Wl,--rpath -Wl,/usr/X11R6/lib -Wl,--rpath -Wl,/usr/X11R6/lib That line, the bugged one anyway, was produced by libtool. So the question becomes, what is libtool doing wrong? Which will probably require shifting over to the main cygwin list and delving into hideous problems, but C'est la vie. Thanks muchly, Arnaud. -Richard Campbell.
RE: DDD 3.3.8 (i686-pc-cygwin) gets `Segmentation fault WAS Re: c ompiling DDD
>So I guess that it should be something along the lines: >gcc -Wall -I/usr/X11R6/include Xmcheck.c -L/usr/X11R6/lib >.libs/libimp-cygXm-2.a >using whather .libs/libimp-cygXm-2.a points to. Ok, yeah, that seems to be the problem. bash-2.05b$ gcc -Wall -I/usr/X11R6/include Xmcheck.c -L/usr/X11R6/lib -lXm Info: resolving _xmUseVersion by linking to __imp__xmUseVersion (auto-import) bash-2.05b$ ./a.exe xmUseVersion=2001 XmVersion=2001 bash-2.05b$ gcc -Wall -I/usr/X11R6/include Xmcheck.c -L/usr/X11R6/lib ddd/.libs/libimp-cygXm-2.a bash-2.05b$ ./a.exe xmUseVersion=1089480191 XmVersion=2001 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. But first, I'll run that last g++ linking step for ddd after editing it to remove those .libs links. -Richard Campbell.
RE: DDD 3.3.8 (i686-pc-cygwin) gets `Segmentation fault WAS Re: c ompiling DDD
>Please try on Cygwin:
>>cat Xmcheck.c
>#include
>#include
>int main(void){
> printf("xmUseVersion=%d XmVersion=%d\n",
> xmUseVersion, XmVersion);
> return 0;
>}
>>gcc -Wall -I/usr/X11R6/include Xmcheck.c -L/usr/X11R6/lib -lXm
>>./a.out
>xmUseVersion=2002 XmVersion=2002
>
>If it gives different numbers, there is a good chance that your lesstif
>library won't work properly.
bash-2.05b$ gcc -Wall -I/usr/X11R6/include Xmcheck.c -L/usr/X11R6/lib -lXm
Info: resolving _xmUseVersion by linking to __imp__xmUseVersion
(auto-import)
bash-2.05b$ ./a.exe
xmUseVersion=2001 XmVersion=2001
Same numbers.
-Richard Campbell.
RE: DDD 3.3.8 (i686-pc-cygwin) gets `Segmentation fault WAS Re: c ompiling DDD
>That is a bug in gcc on cygwin related to "#pragma interface". >Please look for help on the cygwin mailing list. Arnaud, the problem is with both "#pragma interface" and "#pragma implementation". http://www.cygwin.com/ml/cygwin/2003-07/msg00463.html Guarding all "#pragma interface" and "#pragma implementation" calls with ifndef __CYGWIN__ allows everything to compile cleanly - is this something that could be applied to the main baseline? >Modifying ddd/config.h will not help. There is a problem with the >lesstif distribution on cygwin. See: >http://www.lesstif.org/INSTALL.html Is the following what you are referring to? "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? -Richard Campbell.
RE: DDD 3.3.8 (i686-pc-cygwin) gets `Segmentation fault WAS Re: c ompiling DDD
>The problem is not with Cygwin's LessTif... the problem is in how DDD is >detecting LessTif on Cygwin. It must be assuming that the file name for >the import library with be of the format foo.a whereas the name is of >the format foo.dll.a on Cygwin. This would be detection inside the actual execution, then? The link step is libtoolized and ends up being: g++ -DNDEBUG -O2 -g -W -Wall -trigraphs -o ddd.exe ddd.o basename.o compare.o cook.o cwd.o glob.o UndoBuffer.o UndoBE.o WhatNextCB.o configinfo.o -L/usr/X11R6/lib .libs/libimp-cygXm-2.a -lXft -lXrender .libs/libimp-cygfontconfig-1.a .libs/libimp-cygfreetype-6.a -lz .libs/libimp-cygexpat-0.a -lXaw -lXmu -lXt -lXpm -lXp -lXext -lX11 -lSM -lICE -lncurses -ly ../libiberty/libiberty.a -Wl,--rpath -Wl,/usr/X11R6/lib -Wl,--rpath -Wl,/usr/X11R6/lib Which looks sorta automagic for the dlls, right? -Richard Campbell.
RE: compiling DDD
>WAG, try configuring with --without-athena. Doesn't build, then. make[2]: Entering directory `/cygdrive/c/ddd-3.3.7/ddd' source='PannedGE.C' object='PannedGE.o' libtool=no \ depfile='.deps/PannedGE.Po' tmpdepfile='.deps/PannedGE.TPo' \ depmode=gcc3 /bin/sh ../depcomp \ g++ -DHAVE_CONFIG_H -I. -I. -I. -I./.. -isystem /usr/X11R6/include -DNDEBUG - O2 -g -W -Wall -trigraphs -c -o PannedGE.o `test -f 'PannedGE.C' || echo './'`P annedGE.C PannedGE.C: In function `_WidgetRec* createPannedGraphEdit(_WidgetRec*, const char*, Arg*, unsigned int)': PannedGE.C:400: error: `cerr' undeclared (first use this function) PannedGE.C:400: error: (Each undeclared identifier is reported only once for each function it appears in.) make[2]: *** [PannedGE.o] Error 1 make[2]: Leaving directory `/cygdrive/c/ddd-3.3.7/ddd' make[1]: *** [all] Error 2 make[1]: Leaving directory `/cygdrive/c/ddd-3.3.7/ddd' make: *** [all-recursive] Error 1 That line is: cerr << "Warning: panned graph editors are not supported " "in this configuration.\n"; Checking a little further, iostream isn't included on that side of the configuration, which seems odd. Added an iostream include and it successfully built. And then failed in much the same way (different specific error in the version of Motif it didn't find): Warning: This DDD requires a Motif 2.1 library (using Motif 1275340.287) Continue at own risk. Internal error (Segmentation fault). -Richard Campbell.
RE: compiling DDD
I reinstalled lesstif from setup. Same exact results. -Richard Campbell.
RE: compiling DDD
This appears to be the ultimate link line run: g++ -DNDEBUG -O2 -g -W -Wall -trigraphs -o ddd.exe ddd.o basename.o compare.o cook.o cwd.o glob.o UndoBuffer.o UndoBE.o WhatNextCB.o configinfo.o -L/usr/X11R6/lib .libs/libimp-cygXm-2.a -lXft -lXrender .libs/libimp-cygfontconfig-1.a .libs/libimp-cygfreetype-6.a -lz .libs/libimp-cygexpat-0.a -lXaw -lXmu -lXt -lXpm -lXp -lXext -lX11 -lSM -lICE -lncurses -ly ../libiberty/libiberty.a -Wl,--rpath -Wl,/usr/X11R6/lib -Wl,--rpath -Wl,/usr/X11R6/lib Why is it that cygXm-2 is linked in as ".libs/libimp-cygXm-2.a"? Is that to be expected? -Richard Campbell.
RE: compiling DDD - "cygcheck ddd.exe" attached.
If the attachment doesn't fly, I'll resend as text. This particular cygXm-2.dll it mentions I built myself, using the script from the lesstif source package, when I was trying to run some other problem (specifically, I was concerned about mixing 3.2 build libraries based on some other mailing list posts) down - I can reinstall the default from setup, but it should be the same. -Richard Campbell. ddd_cygcheck Description: Binary data
RE: compiling DDD
"make check" segfaults at the make check for ddd in just the same way as the main program does (same output, same ~/.ddd/log output). -Richard Campbell. bash-2.05b$ /usr/local/bin/ddd Warning: This DDD requires a Motif 2.1 library (using Motif 1324099.71) Continue at own risk. Warning: No type converter registered for 'String' to 'Orientation' conversion. Warning: No type converter registered for 'String' to 'Orientation' conversion. Warning: No type converter registered for 'String' to 'Orientation' conversion. Internal error (Segmentation fault). Oops! You have found a bug in DDD. If you can reproduce this bug, please send a bug report to <[EMAIL PROTECTED]>, giving a subject like DDD 3.3.7 (i686-pc-cygwin) gets `Segmentation fault' signal To enable us to fix the bug, you should include the following information: * What you were doing to get this message. Report all the facts. * The contents of the `~/.ddd/log' file as generated by this session. Please read also the section "Reporting Bugs" in the DDD manual. Looking at the ~/.ddd/log output is rather bizarre: GNU DDD 3.3.7 (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.3.1 (cygming special) 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-01 by (unknown). $ /usr/local/bin/ddd ! Segmentation fault ! Interrupt (because that lesstif version is the one I'm using). I'm going back and doing some "make check" and looking at config.log to see what's going on with the lesstif linking and discussion. -Richard Campbell.
RE: compiling DDD
>> 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. Brian, piggybacking a bit here - this is with ddd-3.3.7 source, compiling with g++ (GCC) 3.3.1 (cygming special), everything else up to date: Agent.o(.text+0x3fb6): In function `GLOBAL(int10_t, long double, char, short, int, double)': /usr/include/c++/3.3.1/iostream:438: undefined reference to `__static_initialization_and_destruction_0(int, int)' Agent.o(.text+0x3fd6): In function `_GLOBAL__D_Agent_rcsid': /usr/include/c++/3.3.1/iostream:438: undefined reference to `__static_initialization_and_destruction_0(int, int)' AgentM.o(.ctors+0x0): In function `_ZN12AgentManagerpLEP5Agent': /cygdrive/c/ddd-3.3.7/ddd/AgentM.C:62: undefined reference to `_GLOBAL(int10_t, long double, char, short, int, double)' I looked here: http://www.cygwin.com/ml/cygwin/2003-07/msg00463.html And cut out all pragma interface and pragma implementations I could find. After that, ddd compiles. If I run it, the following segmentation fault: bash-2.05b$ /usr/local/bin/ddd Warning: This DDD requires a Motif 2.1 library (using Motif 1324099.71) Continue at own risk. Warning: No type converter registered for 'String' to 'Orientation' conversion. Warning: No type converter registered for 'String' to 'Orientation' conversion. Warning: No type converter registered for 'String' to 'Orientation' conversion. Internal error (Segmentation fault). Oops! You have found a bug in DDD. If you can reproduce this bug, please send a bug report to <[EMAIL PROTECTED]>, giving a subject like DDD 3.3.7 (i686-pc-cygwin) gets `Segmentation fault' signal To enable us to fix the bug, you should include the following information: * What you were doing to get this message. Report all the facts. * The contents of the `~/.ddd/log' file as generated by this session. Please read also the section "Reporting Bugs" in the DDD manual. Looking at the ~/.ddd/log output is rather bizarre: GNU DDD 3.3.7 (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.3.1 (cygming special) 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-01 by (unknown). $ /usr/local/bin/ddd ! Segmentation fault ! Interrupt (because that lesstif version is the one I'm using). I'm going back and doing some "make check" and looking at config.log to see what's going on with the lesstif linking and discussion. -Richard Campbell.
RE: All packages refreshed with build scripts and source code (we ll, almost all)
>I have just finished rebuilding almost all of the Cygwin/X packages. >The prime reasons of the rebuilding and repackaging were: > >1) Provide source for all packages. >2) Provide a build script for all packages. >3) Provide a Cygwin-specific README file for all packages. >4) Include the setup.hint files in each package, so others can modify >and maintain them. >5) Refresh the build of any packages that predated the new shared >library naming convention. Harold, were the source packages ever released for XFree86-*? -Richard Campbell.
RE: DDD needs a porter [Was: DDD 3.3.8 segmentation error, relate dto Motif?]
>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). There is at least one other problem. I tried with ddd 3.3.8 (latest everything, as far as I can tell, certainly gcc 3.3), and got the same missing xregex include errors for libiberty. I tried with ddd 3.3.7, and got an ld error at the very end of the make routine. I'm going to look at it again, but I'm traveling until Monday. -Richard Campbell.
RE: DDD needs a porter [Was: DDD 3.3.8 segmentation error, relate d to Motif?]
>Somebody needs to take it upon themself to port DDD and make appropriate >fixes to make it work on Cygwin/X. This has not been done to date, as >far as I can recall, and it is likely to need to be done before ddd will >"just work". I don't see a lot happening with DDD until someone steps >forward to port it properly. In previous versions (cygwin, xfree, ddd), DDD did compile and run out of the box. I believe that is why no one took it upon themselves previously. see http://www.cygwin.com/ml/cygwin/2003-09/msg00241.html -Richard Campbell.
RE: ssh x forwarding
This probably should have been on the xfree list. >From: Patrick Nelson [mailto:[EMAIL PROTECTED]] > >In ssh you get x forwarding. But, I can't seem to get it working. A >command like: > > ssh -l > >always responds with something like: > > Gtk-WARNING **: cannot open display: > >Is there some configuration that needs to take place in cygwin first? Yes I >can log in by dropping the part and yes the is available. >Tried running the above from a terminal that displayed after doing a >"startx" too... same result. So I have to figure I just don't have >something setup correctly. At a minimum, you need to have the DISPLAY variable set before you execute the ssh, and you need to use the X forwarding (-X) option to ssh so: export DISPLAY=localhost:0.0 ssh -X -l -Richard Campbell.
RE: Possible bug of the M$ windows manager ? or, XFree bug ?
>Did you hide the mouse cursor when you took the screenshots? There's not a >mouse cursor anywhere in any of those screenshots... I need to see that >Cygwin/XFree86 is indeed hiding/unhiding the mouse cursor correctly. In the first column (cygwin/xfree86) there is a mouse cursor in the 2nd and 3rd shots...twm just kinda sucks that way (in the 2nd shot, look at the large x just above the "fermer" tool tip). -Richard Campbell.
RE: telnet or ssh
Actually, it may only be a problem if you respond to something not in latin-1 or ascii, as your last 2 messages seem fine - only the responses to [EMAIL PROTECTED] seem strange. Now, I see [EMAIL PROTECTED]'s messages just fine... -Richard Campbell.
Re: Remote client cannot display on local xfree-cygwin
>I would like to start an xterm client on a >remote machine and have it display on my >local cygwin-xfree86 X server. However, this >does not work. It appears that the X server >is not even listening to port 6000. If you can start a local xterm, but can't display remotely, have you checked the security settings (xfree86 is pretty restrictive by default)? Have you tried starting a local xterm, running "xhost +", then starting a remote session (without closing down the first local xterm)? What is the error message you see when trying to connect? -Richard. __ Do You Yahoo!? Send your FREE holiday greetings online! http://greetings.yahoo.com
