protux-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Protux-devel] Autostuff migration : Done :-)


From: booker
Subject: Re: [Protux-devel] Autostuff migration : Done :-)
Date: Sun, 16 Feb 2003 22:26:35 +0100
User-agent: KMail/1.4.3

Am Sonntag 16 Februar 2003 03:34 nachmittags/abends schrieb Martin Herren:
> On Sun, 16 Feb 2003 12:12:55 +0100
>
> address@hidden (booker) wrote:
> > Note:
> > Some days ago configure works proper (just make failes), so probably one
> > of the last commits caused this problem?
>
> i commited again my initial configure and Makefile.in... but with the one
> that was online it still found moc for me...


Ooops ... very strange!

I've updated the cvs sources and got this error when running configure:

address@hidden mustuxlib]$ c
./configure: line 3: syntax error near unexpected token `<<<'
./configure: line 3: `<<<<<<< configure'
address@hidden mustuxlib]$


Now I did a clean checkout and configure runs fine:

...
...
...
checking for QT headers... /usr/lib/qt3/include
checking if a small qt application compiles and links fine... ok
configure: creating ./config.status
config.status: creating Makefile
config.status: creating mustux-config
config.status: creating config.h
config.status: executing default-1 commands
address@hidden mustuxlib]$


But now look at the make output below:

address@hidden mustuxlib]$ make
cd . && /bin/sh /home/booker/cvs/mustux/mustuxlib/missing --run aclocal
cd . && \
  /bin/sh /home/booker/cvs/mustux/mustuxlib/missing --run automake --gnu  
Makefile
configure.ac: 6: required file `./[config.h].in' not found
Makefile.am:25: invalid unused variable name: `nodist_libmustux_la_SOURCES'
WARNING: `automake' is missing on your system.  You should only need it if
         you modified `Makefile.am', `acinclude.m4' or `configure.ac'.
         You might want to install the `Automake' and `Perl' packages.
         Grab them from any GNU archive site.

<QUOTE>
No it's there!

address@hidden mustuxlib]$ automake --version
automake (GNU automake) 1.4-p6

(I use mandrake 9.0)

</QUOTE>


cd . && /bin/sh /home/booker/cvs/mustux/mustuxlib/missing --run autoconf
/bin/sh ./config.status --recheck
running /bin/sh ./configure  --prefix /usr/local  --no-create --no-recursion
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... missing
checking for g++... g++
checking for C++ compiler default output... 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 a BSD-compatible install... /usr/bin/install -c
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for gcc... gcc
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
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 dependant libraries... pass_all
checking command to parse /usr/bin/nm -B output... ok
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 for ranlib... 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... no
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 ALSA CFLAGS...
checking for ALSA LDFLAGS...  -lasound -lm -ldl -lpthread
checking for libasound headers version >= 0.9.0... found.
checking for snd_ctl_open in -lasound... yes
checking for moc... no
configure: error: moc could not be found, please install first
make: *** [config.status] Error 1
address@hidden mustuxlib]$


I hope you know what's going on here! ;-)


> when you say it worked some days ago, was that already with the new
> autotool code ?


Yes.


greetings
Reinhard


PS - I'm still very limited in having time :-( , so please be patient when I 
miss something!




reply via email to

[Prev in Thread] Current Thread [Next in Thread]