James McCoy wrote:
> On Mon, Apr 10, 2023 at 09:29:52AM +0200, Tony Mechelynck wrote: > > On Sun, Apr 9, 2023 at 11:02 PM Bram Moolenaar <b...@moolenaar.net> wrote: > > > > > > > > > Tony wrote: > > > > > > > Recently (but I'm not sure when) my supposedly Motif gvim started > > > > getting compiled without GUI. Examination of the config log showed the > > > > following lines: > > > > > > > > checking --enable-gui argument... Motif GUI support > > > > checking for pkg-config... /usr/bin/pkg-config > > > > checking for location of Motif GUI includes... in default path > > > > checking --with-motif-lib argument... no > > > > checking for location of Motif GUI libs... <not found> > > > > > > > > After some trial and error, I found out that by changing just one line > > > > in my environment settings, as follows: > > > > > > > > from: export CONF_OPT_GUI='--enable-gui=motif' > > > > to: export CONF_OPT_GUI='--enable-gui=motif --with-motif-lib=-lXm' > > > > > > > > (and doing no other changes), then sourcing the configure script again > > > > in the same shell to overwrite the environment values set by the > > > > previous version of the same script, and running "make reconfig", its > > > > --version output told me this time "Tiny version with X11-Motif GUI". > > > > The relevant lines in the config log are now > > > > > > > > checking --enable-gui argument... Motif GUI support > > > > checking for pkg-config... /usr/bin/pkg-config > > > > checking for location of Motif GUI includes... in default path > > > > checking --with-motif-lib argument... -lXm > > > > > > > > Is this expected? If just specifying that the Motif lib is named libXm > > > > (without mentioning a directory) makes configure find it, I would have > > > > expected it to already know that. Or is that name nonstandard? > > > > > > It's not about the lib name, it's about finding the library to link > > > with. A sequence of directories are checked for: > > > libXm.a > > > libXm.dll.a > > > libXm.so* > > > libXm.sl > > > libXm.dylib > > > > > > Perhaps the name of the library changed? On my system I can find > > > /usr/lib/x86_64-linux-gnu/libXm.a > > > > > > The check hasn't changed for a long time. It can be found in > > > src/configure.ac around line 2960. > > > > According to the YaST installer, openSUSE Tumbleweed package libXm4 > > titled "Motif runtime library" installs (only) files > > /usr/lib64/libXm.so.4 and /usr/lib64/libXm.so.4.0.4 > > Most shared library packages on Linux are split into the runtime package > (which contains only the SONAME-versioned library names) and the > development package (which includes the header files and the unversioned > library name -- libXm.so -- which is used when building). It sounds > like you only have the runtime package installed. However, that it works by adding "--with-motif-lib=-lXm" suggests that the development packages can be found by the compiler. It's the configure script that can't find them and assumes Motif wasn't installed. -- Q: What's orange and sounds like a parrot? A: A carrot /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ /// \\\ \\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/20230410212551.35A211C03DE%40moolenaar.net.
