On Wed, Oct 31, 2018 at 08:47:51PM -0500, Matthew D. Fuller wrote: > On Tue, Oct 30, 2018 at 03:38:59PM +0000 I heard the voice of > Yumekui Neru, and lo! it spake thus: > > > > I have been running into linking errors when trying to build > > versions after the inclusion of ctwmlib. The credit for this (fix?) > > is not mine, though it should be because of the linking of > > $(CTWMLIBS) to ctwm instead of the new ctwmlib: > > That is... very strange. How is it even meaningful to "link" a > shared lib into an archive? Can you run a build with VERBOSE=1 so we > can see exactly what it's trying to do that fails? > > > -- > Matthew Fuller (MF4839) | [email protected] > Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ > On the Internet, nobody can hear you scream.
The build fails when built using an ebuild with the portage package manager, though is successful if built "manually" with make (and in portage after changing the aforementioned line). Output resulting from 'emerge ctwm' (with a slightly modified ebuild to use git): https://bpaste.net/show/98feb0590de0 The output and verbosity from portage seems abouts the same as building with make VERBOSE=1 (up to the linking part). The errors are a lot of undefined references of the sort ctwm_main.c:(.text+0x27f): undefined reference to `XtToolkitInitialize'
