Today was a frustrating one. Tried to get the latest CVS build of Cinelerra (cvs.cinelerra.org) compiled on my Dell 400SC running Fedora Core 4. No go. I'm not the best at compiling beyond "configure, make, make install", so the process of autogen, aclocal and autoreconf were new to me.
A couple things learned:
- running aclocal creates an aclocal.m4 file. In order to make sure you are pointing to the correct macros within the build files, you need to make sure to point to m4 using:
aclocal -I m4
- the aclocal.m4 file should be larger than /usr/share/aclocal/libtool.m4, because aclocal.m4 is a superset of /usr/share/aclocal/libtool.m4.
If you have trouble compiling Cinelerra, try running autoreconf -i --force.
That's about it for tonight. I'm off to see if my 48Khz audio will match to my 48Khz video! Yeehoo!
talk to you later!
Sunday, April 09, 2006
Unsuccessful compile from CVS source
If this post was useful to you..consider buying me a beer via PayPal!
Even a $1 Draft will keep the Mule happily working..and help pay for equipment upgrades!
Subscribe to:
Post Comments (Atom)
2 comments:
OH, don't get me started on trying to get things to compile under Linux. I just got threw complaining about a bunch of software woes I'm having with Fedora Core 5. It isn't Fedora's fault. I admit I don't know what I'm doing. I know enough to say that nothing will come of this Linux thing until a fair install wrapper is invented.
It never fails that something is wrong. It is like trying to balance wet noodles on the end of a worm's nose.
You track down nineteen missing libraries (and their missing references) only to find a problem in the C code that no one thought to test before inflicting a bad version out there for others to deal with.
I'll end this rant there. I could go on for hours.
Kelly
Kelly,
If you know of any good documentation on aclocal, autoconf, libtool or the compile process in general, please let me know. I don't know where to start in order to solve this one.
Right now, I've got all the libraries installed on my FC4 box, but I get hung up right at the start with these messages:
[root@computer hvirtual]# autoreconf -i --force
Copying file mkinstalldirs
cinelerra/data/Makefile.am:1: library used but `RANLIB' is undefined
cinelerra/data/Makefile.am:1:
cinelerra/data/Makefile.am:1: The usual way to define `RANLIB' is to add
`AC_PROG_RANLIB'
cinelerra/data/Makefile.am:1: to `configure.in' and run `autoconf'
again.
plugins/defaulttheme/data/Makefile.am:1: library used but `RANLIB' is
undefined
plugins/defaulttheme/data/Makefile.am:1:
plugins/defaulttheme/data/Makefile.am:1: The usual way to define
`RANLIB' is to add `AC_PROG_RANLIB'
plugins/defaulttheme/data/Makefile.am:1: to `configure.in' and run
`autoconf' again.
plugins/suv/data/Makefile.am:1: library used but `RANLIB' is undefined
plugins/suv/data/Makefile.am:1:
plugins/suv/data/Makefile.am:1: The usual way to define `RANLIB' is to
add `AC_PROG_RANLIB'
plugins/suv/data/Makefile.am:1: to `configure.in' and run `autoconf'
again.
quicktime/ffmpeg/libavcodec/Makefile.am:13: Libtool library used but
`LIBTOOL' is undefined
quicktime/ffmpeg/libavcodec/Makefile.am:13:
quicktime/ffmpeg/libavcodec/Makefile.am:13: The usual way to define
`LIBTOOL' is to add `AC_PROG_LIBTOOL'
quicktime/ffmpeg/libavcodec/Makefile.am:13: to `configure.in' and run
`aclocal' and `autoconf' again.
quicktime/ffmpeg/libavcodec/i386/Makefile.am:1: Libtool library used but
`LIBTOOL' is undefined
quicktime/ffmpeg/libavcodec/i386/Makefile.am:1:
quicktime/ffmpeg/libavcodec/i386/Makefile.am:1: The usual way to define
`LIBTOOL' is to add `AC_PROG_LIBTOOL'
quicktime/ffmpeg/libavcodec/i386/Makefile.am:1: to `configure.in' and
run `aclocal' and `autoconf' again.
autoreconf: automake failed with exit status: 1
Post a Comment