#134 Compilation errors SVN 661

open
nobody
None
5
2010-01-18
2010-01-18
George Boddey
No

This is in relation to the following Bug:

http://sourceforge.net/tracker/?func=detail&aid=2929819&group_id=141999&atid=751213

I have performed the same build process on SVN 661 and i get the following error:

libtool: link: gcc -shared .libs/libmetadata_libavformat_la-metadata_libavformat.o -L/usr/local/lib -lavformat -lavcodec -lz -lbz2 /usr/lib/libfaac.so /usr/lib/libfaad.so /usr/lib/libmp3lame.so /usr/lib/libtheora.so -logg -lx264 -lm -lxvidcore -ldl /usr/lib/libasound.so -lavutil -pthread -pthread -pthread -Wl,-soname -Wl,libmetadata_libavformat.so.0 -o .libs/libmetadata_libavformat.so.0.0.0
make[1]: Leaving directory `/home/george/src/fuppes/src/plugins'

i have attached the config.log and make.log

Discussion

  • George Boddey
    George Boddey
    2010-01-18

    config.log

     
    Attachments
  • I think that you forgot to pipe the error of the make into your make.log; i just searched it for error and came up with nothing. So you can pipe it using:

    make 2>&1 > make.log

    And I just tried this on my server (Ubuntu Karmic) and I had no problems so I suspect you may be having a dependancy problem. Could you please make sure that the make log contains the errors? Thanks.

     
  • George Boddey
    George Boddey
    2010-01-18

    Make.log (re-upload)

     
    Attachments
  • George Boddey
    George Boddey
    2010-01-18

    sorry about that, i thought i'd copied the error from the log! what dependencies do you think i am likely to be missing?

     
  • Lol. The error still did not come through for some reason but not to worry. I think that I have fixed this problem already in development. If you know how to apply a simple diff then go here: http://massaioli.homelinux.com/~robert/smalldiff.diff

    P.S. That link will only be good for a day or so max.

     
  • George Boddey
    George Boddey
    2010-01-18

    Haha! sorry about that! i did just try to run ./configure with no arguments and still got the error, i will apply the patch and try again.

     
  • George Boddey
    George Boddey
    2010-01-18

    make-patched.log

     
    Attachments
  • George Boddey
    George Boddey
    2010-01-18

    i've tried the patch, and it still caused the error. i've attached another log which i know has the error in! (i checked this time!)

    coudl the version of ffmpeg/avformat be causing the problem? would it be worth trying to build the latest version of that from source?

     
  • I can honestly say that I have not seen that problem before. Weird...hmm. I would suggest two things before we do some serious digging.

    1) Check out the Ubuntu Page on the fuppes wiki and make sure you have the required dependancies: http://fuppes.ulrich-voelkel.de/wiki/index.php?title=Dependencies (there is an apt-get on the bottom of that page if you use a debian / ubuntu based system)
    2) Open the file /usr/include/libavformat/avformat.h and tell me what the major, minor and micro version numbers are.

     
  • George Boddey
    George Boddey
    2010-01-18

    Ok, i ran the apt-get line and all my dependencies were installed and up-to-date, the following is from avformat.h:

    #define LIBAVFORMAT_VERSION_MAJOR 52
    #define LIBAVFORMAT_VERSION_MINOR 31
    #define LIBAVFORMAT_VERSION_MICRO 0

    its really strange, because i am running version 0.646 that i compiled on jaunty with no problems, but after i succesfully built 0.646 i haven't been able to build any other version!

     
  • Hmm okay, so your running the exact same version of libavformat as I am but a different Ubuntu distribution. I am not sure where the problem lies...I'll take a look around and see if I can pinpoint it. Other than that does a pure ./configure && make work?? And you typed in autoreconf -vfi before you tried to configure? Anyway, it's not on my todo list.

     
  • No sorry, I am running an up-to-date karmic server x64, but the version of fuppes I am running was compiled on jaunty!

    When I get home tonight I will try a pure configure & make on a clean source tree, and let you know how it goes!

     
  • George Boddey
    George Boddey
    2010-01-19

    i tried to build fuppes with a clean download of the source code and the build failed with a different error (related to libogg.la) but i will open a new bug for that. removing the simage package allowed me to build fuppes!

     
  • Don't worry about opening a new bug for that. We already know about that problem (I debugged it myself) That one is caused in the simage package but will be fixed in the lucid release of Ubuntu. Yay. But In karmic you cannot compile fuppes with simage. Since you were able to build fuppes can I consider this bug closed?

     
  • Yea of course, sorry for the hassle!

     
  • No Problems. I'm happy to help at any time. :) If you have another problem please feel free to ask and I'll be happy to help.