>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 <snip many lines of .o files> 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 <snip many lines of .o files> 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.
