-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Graham Evans schrieb: > Hermann or someone else - perhaps you can help me here. > > As a test I installed Vales debian x86_64 packages and that went without > a hitch. I think that means my external dependencies are okay... or > not? Perhaps building is one thing and executing a binary is another. > > The pre-built packages are: cinelerra, libmpeg3hv and libquicktimehv > > Does success in running the pre-build eliminates any of the things I > need to look for in resolving my build problems?
Hi Graham, actually, success in running can help a bit. Am I asuming right you are trying to install on debian or ubuntu? Well, I'm more familiar with that then with RPMs :-) Some random thoughts -- If you want to investigate further on debian/ubuntu, the next step after "successfully running" would be to re-compile the bin package you just successfully installed. Ideally this would give you a working compile (for further investigation different switches or for getting things like opengl running). Basically, the version in Cinelerra-SVN is a valid debian package. So it could be feesible to take a diff between vale's package and the Cinelerra-SVN. For this to work you would need the same SVN-revision which was used to create vale's package. That's the way I am doing my Cinelerra hacking: Some time ago, I created a patch containing all steps I needed to transform the current SVN into a working debian package. Every time I when I load a new version, I apply this patch and voila! I can build the current SVN als *.deb and install it cleanly into my system. At times, I have even two differen versions lying around, one built with -O3 (wich I use for real cutting) and the same source code built with -O1 and -g to be used with gdm, so if there is a bug (probably caused by my own hacking), i just switch over to the "debug" with one dpkg -i command, reload the session which showed the problem and attach gdm to the PID. Do you know the tools available for building on debian? -- see below for sort of a short version "how to build on debian". I'm attaching this just in case it may be helpful. The point is: because building on debian is almost completely automatic, you can always recompile for your specific system if only you can get hold of a debian source package. In most cases it is worth the effort trying to find a debian package instead of just using the upstream tarball of some library. Some time ago I hat a -fPIC problem with some lib (I think it was libavcodec), so I just grabbed the corresponding source, adapted the debian/rules to add the -fPIC switch and recompiled a custom version for my system. Some of the multimedia packages are not in the normal debian repos because of patent issues (liblame, or lbavcodec, libfaac). A good source is allways "debian-multimedia", http://debian-multimedia.org/ the former "debian marilat repo", which has several mirrors round the globe) hopefully, some of this informations answer your question.... Cheers, Hermann PS: In the "checkbuilddeps" phase there are often different problems depending on the current verson of the libs. (collision between liblame0-dev und liblame-dev, problems getting libavcodeccvs-dev. Further, I allways get a -fPIC problem with x264 and have to... ln -s /usr/lib/libx264_pic.a /usr/lib/libx264.a ========================================================================= If you got your packages form a debian/ubuntu repository configured for apt (or synaptic etc.), then you can just step into a new directory owned by you, and type apt-get source PACKAGENAME If you directly downloaded the packages (and installed them with dpkg -i), then you should be able to find the corresponding source packages at the same location (its a *.dsc file and a tar and maybe an additional patch to debianize the tar). you can just unpack the tar (and apply a patch if necessary) or use dpkg-source -x <PACKAGE>.dsc (Note, for building you may need to install packages "build-essential" and "fakeroot" first) then you step into the root of the source tree and run the command.. dpkg-checkbuilddeps ...to check for build-dependencies. This will point out all the -dev packages you need to install in order do build. (Contrary to the bin packages, those dev packages contain static libs to link against and/or header files; they allways depend on the corresponding bin package of the exact same version and it can be sometimes difficult to get both of the same version without breaking other dependencies in the system. But in most cases, this just works "magically"). You could even use APT to direcly install all dependencies apt-get build-deb PACKAGENAME After that you should be ready to build. Start the build with dpkg-buildpackage -rfakeroot helpfull additional swithes: -b :build only the binary package and - -nc : "no clean", just recompile; usefull if you are hacking the source. append " 2>&1 | tee proto.txt " to get the output of make into a file And another hint: the makefile in control of the whole build process is called "rules" and can be found in the debian subdirectory of the package. That's the place where you can tweek compiler options for the whole build process. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGM3D0ZbZrB6HelLIRAtpJAKDCIEK9TclSt5U9wdhA81+8yFJD8gCgmVhH BbtuIYYYUS6C56wGkM5Ccy8= =9D7h -----END PGP SIGNATURE----- _______________________________________________ Cinelerra mailing list [email protected] https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
