[Xastir] OSX 10.15.7 Macports: configure: error: **** MOTIF LIBRARIES NOT FOUND ****

[f1mhv]

Hi Tom,

Is that the part (or complete log needed?):

1 error generated.
configure:8765: $? = 1
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME "xastir"
| #define PACKAGE_TARNAME "xastir"
| #define PACKAGE_VERSION "2.1.7"
| #define PACKAGE_STRING "xastir 2.1.7"
| #define PACKAGE_BUGREPORT "xastir at xastir.org"
| #define PACKAGE_URL ""
| #define PACKAGE "xastir"
| #define VERSION "2.1.7"
| #define PACKAGE "xastir"
| #define VERSION "2.1.7"
| #define XASTIR_TOCALL "APX217"
| #define STDC_HEADERS 1
| #define HAVE_SYS_TYPES_H 1
| #define HAVE_SYS_STAT_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_STRING_H 1
| #define HAVE_MEMORY_H 1
| #define HAVE_STRINGS_H 1
| #define HAVE_INTTYPES_H 1
| #define HAVE_STDINT_H 1
| #define HAVE_UNISTD_H 1
| #define __EXTENSIONS__ 1
| #define _ALL_SOURCE 1
| #define _GNU_SOURCE 1
| #define _POSIX_PTHREAD_SEMANTICS 1
| #define _TANDEM_SOURCE 1
| #define TNC_PORT "none"
| #define GPS_PORT "none"
| #define HAVE_PTHREAD 1
| #define XASTIR_SYSTEM "Darwin"
| #define HAVE_CONVERT 1
| #define CONVERT_PATH "/opt/local/bin/gm convert"
| #define HAVE_LPR 1
| #define LPR_PATH "/usr/bin/lpr"
| #define STIPPLE 1
| #define HAVE_LIBXEXT 1
| #define HAVE_LIBXT 1
| #define HAVE_LIBXM 1
| #define HAVE_SED 1
| #define SED_PATH "/usr/bin/sed"
| #define HAVE_MV 1
| #define MV_PATH "/bin/mv"
| #define HAVE_XFONTSEL 1
| #define XFONTSEL_PATH "/opt/X11/bin/xfontsel"
| #define HAVE_LIBCURL 1
| /* end confdefs.h.  */
| 
| int
| main ()
| {
| XmGetDestination()
|   ;
|   return 0;
| }
configure:8826: error: **** MOTIF LIBRARIES NOT FOUND **** Install Motif development headers/libraries or use --with-motif-libraries to specify path to libXm.a


73 de Cyril - DF1CHB/AM - F1MHV/M



> Le 31 janv. 2021 à 19:06, Tom Russo <russo at bogodyn.org> a écrit :
> 
> Look in config.log and see what the actual failure is.
> 
> Configure finds libraries not simply by looking for the file, but by actually
> trying to link them into a small program.  If that fails, it says it can't
> find them.  There are often reasons for the failure other than the file not
> existing --- for example, the library can be broken in some way, or require
> dependencies that don't exist.
> 
> Look in config.log and try to find the spot where it actually claims it can't
> find libXm.a, and the error message from the linker should help to explain
> why it doesn't work.  But the solution to whatever that problem may be might
> not be obvious at first.
> 
> On Sun, Jan 31, 2021 at 07:03:28PM +0100, we recorded a bogon-computron collision of the <f1mhv at free.fr> flavor, containing: