No rule to make target `/mnt/prog/lib/libpython3.3m.so'

Compiling, libraries, modules, coding guidelines and porting

Moderators: jesterKing, stiv

Post Reply
vanangamudi
Posts: 0
Joined: Mon Nov 26, 2012 7:12 pm

No rule to make target `/mnt/prog/lib/libpython3.3m.so'

Post by vanangamudi » Sat Mar 02, 2013 1:22 pm

Everything goes fine(just a guess!)
but when the compilation finished, it says no rule to make libpython3.3m.so, which is already built shared object(I compiled it separately from the blender). what is actually going on??

-----------------------------------------------------------------------------------------------------------
Scanning dependencies of target blender
[100%] Building C object source/creator/CMakeFiles/blender.dir/creator.c.o
[100%] Building C object source/creator/CMakeFiles/blender.dir/buildinfo.c.o
make[2]: *** No rule to make target `/mnt/prog/lib/libpython3.3m.so', needed by `bin/blender'. Stop.
make[1]: *** [source/creator/CMakeFiles/blender.dir/all] Error 2
make: *** [all] Error 2
-----------------------------------------------------------------------------------------------------------

here is the full screenshot of the output
http://paste.ubuntu.com/5579080/
~vanangamudi
I gotta admit. blender is awesome in both dimensions. before and after compilation.

stiv
Posts: 0
Joined: Tue Aug 05, 2003 7:58 am
Location: 45N 86W

Post by stiv » Sat Mar 02, 2013 5:29 pm

Is that the actual location of the library?

Did you add that path to your build config?

vanangamudi
Posts: 0
Joined: Mon Nov 26, 2012 7:12 pm

YAML::functions() not available

Post by vanangamudi » Sat Mar 02, 2013 7:19 pm

this I got solved with help of @plasmasolutions from #blendercoders. I mistyped $PROGB(correct) as $PROG(wrong).
but after reconfiguring and compiling, the dependencies of OpenColorIO, TinyXML (which I didn't installed at the time) was used as a problem to throw errors on my face.
and I installed TinyXML development package. and it got solved too. now another dependency YAML is being reported "not found" and I installed yaml development package but this problem is not solved. it again shows
----------------------------------------------------------------------------------------------------------------------
/usr/lib/gcc/x86_64-linux-gnu/4.6/../../../../lib/libOpenColorIO.a(OCIOYaml.cpp.o): In function `void YAML::operator>><float>(YAML::Node const&, std::vector<float, std::allocator<float> >&)':
(.text._ZN4YAMLrsIfEEvRKNS_4NodeERSt6vectorIT_SaIS5_EE[void YAML::operator>><float>(YAML::Node const&, std::vector<float, std::allocator<float> >&)]+0x3a7): undefined reference to `YAML::Iterator::~Iterator()'
/usr/lib/gcc/x86_64-linux-gnu/4.6/../../../../lib/libOpenColorIO.a(OCIOYaml.cpp.o): In function `void YAML::operator>><float>(YAML::Node const&, std::vector<float, std::allocator<float> >&)':
(.text._ZN4YAMLrsIfEEvRKNS_4NodeERSt6vectorIT_SaIS5_EE[void YAML::operator>><float>(YAML::Node const&, std::vector<float, std::allocator<float> >&)]+0x410): undefined reference to `YAML::Iterator::~Iterator()'
collect2: ld returned 1 exit status
make[2]: *** [bin/blender] Error 1
make[1]: *** [source/creator/CMakeFiles/blender.dir/all] Error 2
make: *** [all] Error 2
-------------------------------------------------------------------------------------------------------------------

or Can I disable OpenColorIO for now. If so, how??
~vanangamudi
I gotta admit. blender is awesome in both dimensions. before and after compilation.

ldo
Posts: 0
Joined: Sun Nov 07, 2010 11:30 pm
Location: Hamilton, New Zealand

Post by ldo » Tue Mar 05, 2013 1:20 am

I built OpenColorIO from source. It wasn’t hard, as I recall.

vanangamudi
Posts: 0
Joined: Mon Nov 26, 2012 7:12 pm

how to pass the path of OCIO to blender

Post by vanangamudi » Tue Mar 05, 2013 3:23 am

ldo wrote:I built OpenColorIO from source. It wasn’t hard, as I recall.
I do like to build softwares from source. I will try it with OCIO. but after building how to pass the path to blender, while building it. is there any variables like OPENCOLOR_IO_PATH simlar to PYTHON_LIBRARY ???
~vanangamudi
I gotta admit. blender is awesome in both dimensions. before and after compilation.

ldo
Posts: 0
Joined: Sun Nov 07, 2010 11:30 pm
Location: Hamilton, New Zealand

Post by ldo » Tue Mar 05, 2013 5:40 am

Yes, you can pass all that kind of thing in CMake variables. I have a wrapper script I use to build Blender, here is the line in it that does the CMake setup (notice all the explicit OPENCOLORIO_xxx and OPENIMAGEIO_xxx definitions):

Code: Select all

cmake \
    -D WITH_PLAYER=ON \
    -D WITH_PYTHON_INSTALL=OFF -D PYTHON_VERSION=3.3 \
    -D PYTHON_INCLUDE_DIR=/usr/include/python3.3m \
    -D PYTHON_LIBRARY=/usr/lib/x86_64-linux-gnu/libpython3.3m.so \
    -D WITH_FFTW3=ON -D WITH_MOD_OCEANSIM=ON \
    -D OPENCOLORIO_INCLUDE_DIR=/usr/local/OpenColorIO/include \
    -D OPENCOLORIO_OPENCOLORIO_LIBRARY=/usr/local/OpenColorIO/lib/libOpenColorIO.so \
    -D OPENCOLORIO_TINYXML_LIBRARY=/usr/local/OpenColorIO/lib/libtinyxml.a \
    -D OPENCOLORIO_YAML-CPP_LIBRARY=/usr/local/OpenColorIO/lib/libyaml-cpp.a \
    -D OPENIMAGEIO_INCLUDE_DIR=/usr/include \
    -D OPENIMAGEIO_LIBRARY=/usr/lib/libOpenImageIO.so \
    -D WITH_OPENCOLLADA=ON \
    -D WITH_CODEC_FFMPEG=ON -D FFMPEG=/usr/local -D WITH_JACK=ON \
    -D FFMPEG_LIBRARIES="avdevice;avfilter;avformat;avcodec;avutil;swscale;swresample;postproc;nut;bz2;faac;faad;gsm;jack;modplug;mp3lame;opencore-amrnb;opencore-amrwb;rtmp;schroedinger-1.0;speex;theoraenc;theoradec;vpx;x264;xvidcore" \
    -D WITH_CODEC_SNDFILE=ON \
    ../"$SRCDIR"
(../"$SRCDIR" is the Blender source directory,)

vanangamudi
Posts: 0
Joined: Mon Nov 26, 2012 7:12 pm

I did so. and compiled blender succesfully

Post by vanangamudi » Fri Mar 08, 2013 8:58 am

ldo wrote:Yes, you can pass all that kind of thing in CMake variables. I have a wrapper script I use to build Blender, here is the line in it that does the CMake setup (notice all the explicit OPENCOLORIO_xxx and OPENIMAGEIO_xxx definitions):

Code: Select all

cmake \
    -D WITH_PLAYER=ON \
    -D WITH_PYTHON_INSTALL=OFF -D PYTHON_VERSION=3.3 \
    -D PYTHON_INCLUDE_DIR=/usr/include/python3.3m \
    -D PYTHON_LIBRARY=/usr/lib/x86_64-linux-gnu/libpython3.3m.so \
    -D WITH_FFTW3=ON -D WITH_MOD_OCEANSIM=ON \
    -D OPENCOLORIO_INCLUDE_DIR=/usr/local/OpenColorIO/include \
    -D OPENCOLORIO_OPENCOLORIO_LIBRARY=/usr/local/OpenColorIO/lib/libOpenColorIO.so \
    -D OPENCOLORIO_TINYXML_LIBRARY=/usr/local/OpenColorIO/lib/libtinyxml.a \
    -D OPENCOLORIO_YAML-CPP_LIBRARY=/usr/local/OpenColorIO/lib/libyaml-cpp.a \
    -D OPENIMAGEIO_INCLUDE_DIR=/usr/include \
    -D OPENIMAGEIO_LIBRARY=/usr/lib/libOpenImageIO.so \
    -D WITH_OPENCOLLADA=ON \
    -D WITH_CODEC_FFMPEG=ON -D FFMPEG=/usr/local -D WITH_JACK=ON \
    -D FFMPEG_LIBRARIES="avdevice;avfilter;avformat;avcodec;avutil;swscale;swresample;postproc;nut;bz2;faac;faad;gsm;jack;modplug;mp3lame;opencore-amrnb;opencore-amrwb;rtmp;schroedinger-1.0;speex;theoraenc;theoradec;vpx;x264;xvidcore" \
    -D WITH_CODEC_SNDFILE=ON \
    ../"$SRCDIR"
(../"$SRCDIR" is the Blender source directory,)
I compiled blender successfully.
more elaborate sequence:
http://niralaakam.blogspot.in/2013/03/b ... der3d.html
~vanangamudi
I gotta admit. blender is awesome in both dimensions. before and after compilation.

ldo
Posts: 0
Joined: Sun Nov 07, 2010 11:30 pm
Location: Hamilton, New Zealand

Post by ldo » Fri Mar 08, 2013 9:06 am

Glad you figured it out so easily.

You should see the trouble I had with OpenCollada. :)

Post Reply