> | After setting some environment variables (CC, etc.) and correcting a DJGPP
> | specific bug in Bash 2.04, the test went well with one minor and one major
> | exception.
>
> Could you give more details on these steps? What can be done to have
> it right without tuning by hand?
What I set is:
PATH_SEPARATOR=:
TEST_FINDS_EXE=Y
CC=gcc
LD=ld
The first two are neccessary to so DJGPP's Bash can deal with the Unix-isms
(':' is path separator, executables don't have an extension). Some linking
tests assume 'cc' is the C compiler probably because they don't check for the
C compiler first, so CC gets set.
>
> | The test for AC_PATH_XTRA in macros.m4 did fail, but it better since DJGPP
> | doesn't use X Windows. Either the test should be fixed somehow or this
> | expected failure should be mentioned in the docs.
>
> Please, send the config.log from this test.
>
Here it is:
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by configure 2.14a, executed with
> ./configure
configure:616: checking how to run the C preprocessor
configure:638: gcc -E conftest.c >/dev/null 2>conftest.out
configure:691: result: gcc -E
configure:693: checking for X
configure:757: gcc -E conftest.c >/dev/null 2>conftest.out
configure:753: X11/Intrinsic.h: No such file or directory (ENOENT)
configure: failed program was:
#line 752 "configure"
#include "confdefs.h"
#include <X11/Intrinsic.h>
configure:831: gcc -o conftest.exe conftest.c -lXt >&5
c:/djgpp/bin/ld.exe: cannot find -lXt
collect2: ld returned 1 exit status
configure: failed program was:
#line 821 "configure"
#include "confdefs.h"
int
main ()
{
XtMalloc()
;
return 0;
}
configure:901: result: no
Cache variables:
| ac_cv_have_x=have_x=no
| ac_cv_prog_CPP='gcc -E'
| ac_cv_prog_LN_S='cp -p'
confdefs.h:
|
| #define X_DISPLAY_MISSING 1
