Re: Problem finding TPO dependency file

[John Ling]

Hi Ralf,

I am running on an IBM P690 SMP PowerPC64 running Linux 2.6.9-34.0.2.EL.

The dependency style selected during configure was gcc3 (see output of 
configure below).  There are no other errors prior to the one I sent.  I 
have tested with 1.9.6 and the problem also shows up with that version 
of automake.  The latest automake and aclocal version that work is 
1.8.5.  I only have one Libtool install (version 1.5.22).  I copy this 
Libtool's libtool.m4 and ltdl.m4 into each of the automake install's 
automake/share/aclocal directories.  This is the only "customization" 
that I do to the autotool's setup.  Don't think this is an issue though.

checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for g++... g++
checking for C++ compiler default output file name... a.out
checking whether the C++ compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for style of include used by make... GNU
checking dependency style of g++... gcc3
checking build system type... powerpc64-unknown-linux-gnu
checking host system type... powerpc64-unknown-linux-gnu
checking for gcc... gcc
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
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... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking how to run the C++ preprocessor... g++ -E
checking for g77... g77
checking whether we are using the GNU Fortran 77 compiler... yes
checking whether g77 accepts -g... yes
checking the maximum length of command line arguments... 32768
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if gcc supports -fno-rtti -fno-exceptions... no
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 whether the gcc linker (/usr/bin/ld -m elf32ppclinux) supports 
shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/bin/ld -m elf32ppclinux
checking if the linker (/usr/bin/ld -m elf32ppclinux) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld -m elf32ppclinux) supports 
shared libraries... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/bin/ld -m elf32ppclinux) supports 
shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
appending configuration tag "F77" to libtool
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for g77 option to produce PIC... -fPIC
checking if g77 PIC flag -fPIC works... yes
checking if g77 static flag -static works... yes
checking if g77 supports -c -o file.o... yes
checking whether the g77 linker (/usr/bin/ld -m elf32ppclinux) supports 
shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking for library containing gethostbyname... none required
checking for library containing socket... none required
checking for library containing compress... -lz
checking whether gcc and cc understand -c and -o together... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: executing depfiles commands


Thanks,

--
John Ling
Software developer, UBC Bioinformatics Centre & UBC Proteomics Centre


Ralf Wildenhues wrote:
> Hello John,
>
> * John Ling wrote on Thu, Sep 28, 2006 at 08:13:56PM CEST:
>
> > Using automake 1.9.1 and higher, I get the following error below.  I do 
> > not get this error if I switch to automake 1.8.5.  So what is the change 
> > between 1.8.5 and 1.9.1 that causes it to be unable to generate this TPO 
> > file?  What do I have to do to resolve this problem?
> >
> > shared/cpp/src/fasta/Fasta.cpp:192: fatal error: opening dependency file 
> > shared/cpp/src/fasta/.deps/Fasta.Tpo: No such file or directory
> > compilation terminated.
> > make[1]: *** [shared/cpp/src/fasta/Fasta.lo] Error 1
> > make[1]: Leaving directory `/space1/home/jling/atlas2/ubic'
> > make: *** [all-recursive] Error 1
>
>
> Which compiler on which system, what dependency mode does configure
> compute, are there more warnings or errors before the above, does this
> also happen when you use automake-1.9.6?
>
> Cheers,
> Ralf