OK,
What is the issue now? I do not remember the problem.

Suhaib

> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Wolfgang
> Braun
> Sent: Tuesday, May 16, 2000 3:28 PM
> To: [email protected]
> Subject: RE: [opendx-users] compilation on SuSE 6.4 fails
>
>
> On Tue, 16 May 2000, you wrote:
> > Delete config.cache file first.
> >
> > Suhaib
> sorry. Here's the 'original'. It should be the same, though,
> since I did not change anything.
> <snip>
> creating cache ./config.cache
> checking for a BSD compatible install... /usr/bin/ginstall -c
> checking whether build environment is sane... yes
> checking whether make sets ${MAKE}... yes
> checking for working aclocal... found
> checking for working autoconf... found
> checking for working automake... found
> checking for working autoheader... found
> checking for working makeinfo... found
> checking architecture type... linux
> checking architecture specific stuff... done
> checking for csh... 1
> checking for a BSD compatible install... /usr/bin/ginstall -c
> checking for ranlib... ranlib
> checking for c++... c++
> checking whether the C++ compiler (c++  ) works... yes
> checking whether the C++ compiler (c++  ) is a cross-compiler... no
> checking whether we are using GNU C++... yes
> checking whether c++ accepts -g... yes
> checking for gcc... gcc
> .
> .
> .
> checking for popen... yes
> checking for vfork... yes
> checking for trunc... yes
> checking for _popen... no
> checking for spawnvp... no
> checking for _spawnvp... no
> checking for regcomp... yes
> checking for sysmp... no
> checking for sysconf... yes
> checking for bison... yacc
> checking for CC/libc.h... no
> checking for CC/osfcn.h... no
> checking for DPS/XDPSlib.h... no
> checking for DPS/dpsXclient.h... (cached) no
> checking for DPS/psops.h... no
> checking for GL/gl.h... yes
> <snap>
> --
> Dr. Wolfgang Braun
> Paul-Drude-Institut für Festkörperelektronik
> Hausvogteiplatz 5-7
> D-10117 Berlin
> Germany
>
> email: [EMAIL PROTECTED]
> phone: +49-(0)-30-20377-366
> fax: +49-(0)-30-20377-201

Reply via email to