Re: Compiling PicoGUI on Skiffclusters
Eric Heinemann <[email protected]>
| Newsgroups | gmane.comp.video.picogui.devel |
|---|---|
| Message-ID | <[email protected]> |
I did install the server. I also tried pointing cli_c directly to the headers. The result was the same. Any other ideas? Thanks,Eric Philippe Ney <[email protected]> wrote:> I am trying to compile PicoGUI on the iPAQ skiffclusters. I am continuosly > getting an error when trying to configure cli_c about not being able to link > the test program. > > Here is everything outputted when running configure for cli_c: > > guest@ipaq7:~/[email protected]/picogui-0.45/cli_c$ ./configure > --prefix=/h ome/guest/[email protected]/independent > --exec-prefix=/home/guest/[email protected]/dependent loading cache > ./config.cache checking for a BSD compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking whether make sets ${MAKE}... yes > checking for working aclocal-1.4... found > checking for working autoconf... found > checking for working automake-1.4... found > checking for working autoheader... found > checking for working makeinfo... found > checking host system type... armv4l-unknown-linux-gnu > checking for previous host... armv4l-unknown-linux-gnu > checking for gcc... gcc > checking whether the C compiler (gcc ) works... yes > checking whether the C compiler (gcc ) is a cross-compiler... no > checking whether we are using GNU C... yes > checking whether gcc accepts -g... yes > checking how to run the C preprocessor... gcc -E > checking for ranlib... ranlib > checking for ar... ar > checking for nm... nm > checking for Cygwin environment... no > checking for mingw32 environment... no > checking build system type... armv4l-unknown-linux-gnu > checking for ld used by GCC... /usr/bin/ld > checking if the linker (/usr/bin/ld) is GNU ld... yes > checking for /usr/bin/ld option to reload object files... -r > checking for BSD-compatible nm... nm > checking for a sed that does not truncate output... /bin/sed > checking whether ln -s works... yes > checking how to recognise dependent libraries... file_magic ELF > [0-9][0-9]*-bit[LM]SB (shared object|dynamic lib ) > checking for object suffix... o > checking for executable suffix... no > checking command to parse nm output... ok > checking for dlfcn.h... yes > checking for file... /usr/bin/file > checking for ranlib... (cached) ranlib > checking for strip... strip > checking for objdir... .libs > checking for gcc option to produce PIC... -fPIC > checking if gcc PIC flag -fPIC works... yes > checking if gcc static flag -static works... yes > checking if gcc supports -c -o file.o... yes > checking if gcc supports -c -o file.lo... yes > checking if gcc supports -fno-rtti -fno-exceptions... yes > checking whether the linker (/usr/bin/ld) supports shared libraries... yes > checking how to hardcode library paths into programs... immediate > checking whether stripping libraries is possible... yes > checking dynamic linker characteristics... GNU/Linux ld.so > checking if libtool supports shared libraries... yes > checking whether to build shared libraries... yes > checking whether to build static libraries... yes > checking whether -lc should be explicitly linked in... no > creating libtool > checking for dirent.h that defines DIR... yes > checking for opendir in -ldir... no > checking for ANSI C header files... yes > checking for fcntl.h... yes > checking for malloc.h... yes > checking for sys/time.h... yes > checking for working const... yes > checking for size_t... yes > checking whether time.h and sys/time.h may both be included... yes > checking whether struct tm is in sys/time.h or time.h... time.h > checking for working alloca.h... yes > checking for alloca... yes > checking return type of signal handlers... void > checking for vprintf... yes > checking for socket... yes > checking for strtol... yes > configure: error: cannot link a test picogui program. > > Please let me know if you have any suggestions. Configure don't find the headers. Either you have to 'make install' the server or tell the client where the headers are. Have a look at the last of : $ ./configure --help -philippe --------------------------------- Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo.