Hi all, I am planning to use fftw library for one of our project using Powerpc 744x running Windriver vxworks 6.x on it instead of a COTS signal processing library. Although it is little bit straightforward to build a generic library for x86 platform, there exist a problem in the vxworks case. The output of the cygwin is as follows. Any idea that to recover the problem will help a lot. Thanks in advance. Serkan --------------% test@test /cygdrive/d/fftw-3.3alpha1 $ ./configure CC=ccppc --host=powerpc-wrs-vxworks configure: WARNING: If you wanted to set the --build type, don't use --host. If a cross compiler is detected then cross compile mode will be used. checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /usr/bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for powerpc-wrs-vxworks-strip... no checking for strip... strip checking whether to enable maintainer-specific portions of Makefiles... no checking build system type... i686-pc-cygwin checking host system type... powerpc-wrs-vxworks checking for powerpc-wrs-vxworks-gcc... ccppc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... yes checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether ccppc accepts -g... yes checking for ccppc option to accept ISO C89... unsupported checking for style of include used by make... GNU checking dependency style of ccppc... gcc3 checking for C compiler vendor... gnu checking for ccppc option to accept ISO C99... unsupported checking for ccppc option to accept ISO C89... (cached) unsupported checking for ccppc option to accept ISO Standard C... (cached) unsupported checking for a BSD-compatible install... /usr/bin/install -c checking whether ln -s works... yes checking whether make sets $(MAKE)... (cached) yes checking for a sed that does not truncate output... /usr/bin/sed checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for fgrep... /usr/bin/grep -F checking for ld used by ccppc... c:/windriver35/gnu/3.4.4-vxworks-6.5/x86-win32/ powerpc-wrs-vxworks/bin/ld.exe checking if the linker (c:/windriver35/gnu/3.4.4-vxworks-6.5/x86-win32/powerpc-w rs-vxworks/bin/ld.exe) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... no checking for powerpc-wrs-vxworks-dumpbin... no checking for powerpc-wrs-vxworks-link... no checking for dumpbin... no checking for link... link -dump -symbols configure: WARNING: using cross tools not prefixed with host triplet checking the name lister (link -dump -symbols) interface... BSD nm checking the maximum length of command line arguments... 8192 checking whether the shell understands some XSI constructs... yes checking whether the shell understands "+="... yes checking for c:/windriver35/gnu/3.4.4-vxworks-6.5/x86-win32/powerpc-wrs-vxworks/ bin/ld.exe option to reload object files... -r checking for powerpc-wrs-vxworks-objdump... objdump checking how to recognize dependent libraries... unknown checking for powerpc-wrs-vxworks-ar... no checking for ar... ar checking for powerpc-wrs-vxworks-strip... strip checking for powerpc-wrs-vxworks-ranlib... no checking for ranlib... ranlib checking command to parse link -dump -symbols output from ccppc object... failed checking how to run the C preprocessor... /lib/cpp configure: error: in `/cygdrive/d/fftw-3.3alpha1': configure: error: C preprocessor "/lib/cpp" fails sanity check See `config.log' for more details. test@test /cygdrive/d/fftw-3.3alpha1 $
How to build fftw library for vxworks running on powerpc?
Started by ●April 8, 2009
Reply by ●April 9, 20092009-04-09
On Apr 8, 10:34�am, "zibifnik" <cey...@aselsan.com.tr> wrote:> checking how to run the C preprocessor... /lib/cpp > configure: error: in `/cygdrive/d/fftw-3.3alpha1': > configure: error: C preprocessor "/lib/cpp" fails sanity check > See `config.log' for more details.This is probably off-topic for comp.dsp; it's more a question on how to use GNU-style configure scripts. However, note that you can a) specify a particular C preprocessor (e.g. ccppc -E) by using ./ configure CPP="ccppc -E" on the command line to set the value of CPP b) look in config.log to find the specific error message that caused invocation of cpp to fail. Good luck! Regards, Steven G. Johnson