> What does config.log mention?
>
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
configure:591: checking for a BSD compatible install
configure:646: checking for apxs
configure:683: checking for gcc
configure:796: checking whether the C compiler (gcc -
L/usr/local/lib//lib) works
configure:812: gcc -o conftest -I/usr/local/lib//include -
L/usr/local/lib//lib conftest.c 1>&5
configure:838: checking whether the C compiler (gcc -
L/usr/local/lib//lib) is a cross-compiler
configure:843: checking whether we are using GNU C
configure:852: gcc -E conftest.c
configure:871: checking whether gcc accepts -g
configure:905: checking for /etc/mandrake-release
configure:937: checking for mgd_connect in -lmidgard
configure:956: gcc -o conftest -g -O2 -I/usr/local/lib//include -
L/usr/local/lib//lib conftest.c
-lmidgard 1>&5
/usr/local/lib/libmidgard.so: undefined reference to `g_string_free'
/usr/local/lib/libmidgard.so: undefined reference to `g_string_new'
/usr/local/lib/libmidgard.so: undefined reference to `g_string_assign'
/usr/local/lib/libmidgard.so: undefined reference to `g_byte_array_new'
/usr/local/lib/libmidgard.so: undefined reference to `g_byte_array_free'
/usr/local/lib/libmidgard.so: undefined reference to
`g_byte_array_set_size'
/usr/local/lib/libmidgard.so: undefined reference to
`g_byte_array_append'
collect2: ld returned 1 exit status
configure: failed program was:
#line 945 "configure"
#include "confdefs.h"
/* Override any gcc2 internal prototype to avoid an error. */
/* We use char because int might match the return type of a gcc2
builtin and then its argument prototype would still apply. */
char mgd_connect();
int main() {
mgd_connect()
; return 0; }
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
