On Thu, 20 Jan 2005, Jonathan Woithe wrote: > > > Yup :). figured as much and started shooting at it with CC='gcc-3.3' > > > and CXX='g++-3.3', with a good about of success. the resulting error
The cvs verion of mplex has a build process that is the worst example automake hell I've ever seen. This is all you need to do to build CVS mplex, if you build the mjpeg library in the utils directory first. This works with both egcs-2.91.66 and gcc-3.2.2, and probably every other verion of g++ there is too. It doesn't matter which verions of automake, autoconf and libtool you have. # remove dead code that isn't used rm vector.cpp vector.hpp # remove Z/Alpha files rm zalphastrm.hpp zalphastrm_in.cpp zalphastrm_out.cpp # compile and link everything! g++ -DHAVE_CONFIG_H -I ../utils -I.. *.cpp ../utils/.libs/libmjpegutils.a That's it! You can compile and link mplex with one single g++ command! That's it, one command that fits on one line! For some reason autohell needs a ONE THOUSAND LINE Makefile to do this, and it doesn't even work! When a package that is so simple it doesn't even need a makefile has a build process so complex that people are told they need to switch distributions to build it, that's a sign autohell has gone seriously out of control. Getting mjpegtools CVS to build on my old system was 10 times harder than getting mplayer to, and given that mplayer is about 100 times more complex than mjpegtools, that says something about the mjpegtools build process, and that something isn't good. ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Mjpeg-users mailing list Mjpeg-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mjpeg-users
