Yet Another Bulletin Board

Welcome, Guest. Please Login or Register.
10/31/14 at 15:40:15

Home Home Help Help Search Search Members Members Login Login Register Register
iLab Forum How to compile the code?


   iLab Forum
   C++ Neuromorphic Vision Toolkit
   Bugs
(Moderators: Forum Admin, Laurent Itti)
   How to compile the code?
« No topic | Next topic »
Pages: 1 2  Reply Reply Notify of replies Notify of replies Send Topic Send Topic Print Print
   Author  Topic: How to compile the code?  (Read 16622 times)
Rob Peters
YaBB Senior Member
****






  rjpcal  
WWW

Gender: male
Posts: 398
Re: How to compile the code?
« Reply #15 on: 05/05/08 at 13:22:24 »
Quote Quote Modify Modify

on 04/23/08 at 01:10:54, Rasha wrote:
Another error:  
 
Error:  used '../' at beginning of path
make: *** [build/alldepends-v2] Error 1
 
I don not understand what is problem....
 

 
What options did you give to the configure script when you ran it? Please run the configure script without --enable-quietcompile, then run 'make core' and post the result here.
 
Cheers,
Rob
Logged
LisaYan
YaBB Newbie
*



I love YaBB 1G - SP1!

   


Posts: 1
compiling errors
« Reply #16 on: 12/02/08 at 10:50:11 »
Quote Quote Modify Modify

Hi,  
 
I'm compiling the code under linux. It has some errors and the message as follows. please advise me.  
indigo 337 % ./configure --enable-quietcompile  
checking for source directory... src/
checking for object file directory... build/obj/
checking for build scripts directory... ./devscripts
checking for plugin directory... /cs/research/jtfarm/LisaYan/itti/saliency/lib/invt/plugins
checking for runtime-library directory... /cs/research/jtfarm/LisaYan/itti/saliency/lib/invt
checking for OS... Linux
checking for CPU type... i686
checking for CPU model... pentium4
checking whether pentium4 CPU is x86-compatible... yes
checking whether pentium4 CPU supports Intel MMX instructions... yes
checking whether pentium4 CPU supports Intel SSE instructions... yes
checking whether pentium4 CPU supports Intel SSE2 instructions... yes
checking whether pentium4 CPU supports Intel SSE3 instructions... no
checking whether pentium4 CPU supports Intel SSSE3 instructions... no
checking whether pentium4 CPU supports Intel SSE41 instructions... no
checking whether pentium4 CPU supports AMD 3Dnow instructions... no
checking whether pentium4 CPU supports 64 bit instructions... no
checking whether to use a lib64 directory... checking for location of tcl >= 8.4... /usr/lib
checking for location of tk >= 8.4... /usr/lib
checking whether to enable Intel MMX optimizations... no
checking whether to enable Intel SSE optimizations... no
checking whether to enable Intel SSE2 optimizations... no
checking whether to enable Intel SSE3 optimizations... no
checking whether to enable Intel SSE/2/3 debayer optimizations... no
checking whether to use cpu-tailored aggressive optimizations... no
checking whether to use non-IEEE non-ISO fast math optimization... no
checking whether to use arc profiles for optimizations... no
checking whether to use profile generate for optimizations... no
checking whether to compute branch probabilities... no
checking whether to use branch profiles... no
checking whether to use SSA Single Static Assignment form optimizations... no
checking whether to use prefetch on loop arrays optimization... no
checking whether to use loop vectorization on tree optimization... no
checking whether to use induction variable optimization... no
checking whether to use unsafe loop optimization... no
checking whether to force 32 bit code under 64 bit CPU... no
checking whether to enable memory debug checks... no
checking whether to enable debug information with -g... yes
checking whether to enable profiling with -pg... no
checking whether to enable GVX_TRACE statements... yes
checking whether to enable compiler warnings... yes
checking for desired optimization level... -O3
checking whether to use dynamic linking, with most objects built as shared libraries... no
checking whether to be quiet during compilation... yes
checking whether to use Fink packages, if available... yes
checking whether the Linker will use relax for global optimizations... no
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...  
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for gcc version... 3.4.6
checking for autoconf-2.5x... no
checking for autoconf-2.53... no
checking for autoconf... /cs/local/bin/autoconf
checking for autoconf version... OK, 2.62 >= 2.53
checking whether to enable matlab mex files... yes
checking for mex... /cs/local/bin/mex
configure: WARNING: Use of Matlab and Mex shared libs forces Position Independant Code via -fPIC option
checking for python... /cs/local/bin/python
checking for tclsh... /cs/local/bin/tclsh
checking for env... /usr/bin/env
checking for mpeg_encode... no
checking for ppmtompeg... /cs/local/bin/ppmtompeg
checking for less... /cs/local/bin/less
checking whether g++ can generate usable precompiled headers... yes
checking whether to use precompiled headers... yes
checking whether to force compiler warnings to be errors... yes
checking whether the c++ std library compiles without warnings... yes
checking how to run the C++ preprocessor... g++ -E
checking for X... libraries /usr/X11R6/lib, headers /usr/X11R6/include
checking QTDIR... /cs/local/packages/qt
checking Qt version... unknown (no such file: /cs/local/packages/qt/include/qglobal.h)
checking for moc... /cs/local/packages/qt/bin/moc
checking for uic... /cs/local/packages/qt/bin/uic
configure: error: couldn't find any Qt libraries in /cs/local/packages/qt/lib
Logged
lengoanhcat
YaBB Newbie
*



I love YaBB 1G - SP1!

   


Posts: 9
Re: How to compile the code?
« Reply #17 on: 10/06/09 at 00:32:35 »
Quote Quote Modify Modify

Hi everyone,
 
I have errors when trying to run ./configure --enable-quietcompiling.
Code:

configure: VPATH_LIBDIRS=/usr/local/lib
configure: status of optional features:
* libpng       missing    png image reading/writing will be disabled
* libjpeg      ok    
* libqwt       missing    qwt plotting will be disabled
* libpopt      missing    no worries, libpopt isn't used currently
* libbz2       missing    transparent bzip2 compression/decompression will be disabled
* libomniORB4  disabled   (use ./configure --enable-omniORB4 to enable)
* libIce       missing    associated functionality will be disabled
* libliveMedia      missing    associated functionality will be disabled
* libfftw3     ok    
* libsvm       missing    svm support will be disabled
* libgslcblas  missing    gsl-based optimizations will be disabled
* libgsl       missing    gsl-based optimizations will be disabled
* libraw1394   missing    firewire support via libdc1394 1.x will be disabled
* libdc1394_control missing    firewire support via libdc1934 1.x will be disabled
* libdc1394    missing    firewire support via libdc1934 2.x will be disabled
* libSDL_mixer      missing    associated functionality will be disabled
* libSDL_gfx   missing    associated functionality will be disabled
* libSDL_image      missing    associated functionality will be disabled
* libGL   missing    associated functionality will be disabled
* libGLU       missing    associated functionality will be disabled
* libglut      missing    associated functionality will be disabled
* libOSMesa    missing    no worries, this is not currently used
* libpthread   ok    
* libgd   missing    no worries, this is not currently used
* libeyelink_core   missing    EyeLink-related programs will be disabled
* libcv   missing    OpenCV-dependent features will be disabled
* libcvaux     missing    OpenCVaux-dependent features will be disabled
* libode       missing    associated functionality will be disabled
* libserial    missing    associated functionality will be disabled
* libirobot-create  missing    associated functionality will be disabled
* libbluetooth      missing    associated functionality will be disabled
* libcwiimote  missing    associated functionality will be disabled
* liblwpr      missing    associated functionality will be disabled
* libxclib     missing    associated functionality will be disabled
* libSurf      missing    SURF-dependent features will be disabled
* libpmk       missing    pmk-dependent features will be disabled
* libtorch     missing    torch-dependent features will be disabled
* liburg       missing    liburg-dependent features will be disabled
configure: WARNINGS:
* Qt executables will not be built (QTDIR must be defined, or --with-qtdir option given)
* libX11 missing
* libXext missing
* libXtst missing
* could not find tclConfig.sh in /usr/lib
* could not find tkConfig.sh in /usr/lib
* libavcodec missing
* libavformat missing
* libSDL missing
* mpic++/mpiCC program missing; MPI programs won't be able to be built
* OpenSceneGraph Was Disabled; This is OK

 
All of my libraries locate in the /usr/lib not /usr/local/lib but the VPATH_LIBDIRS refers to the /usr/local/lib. I have tried to use ./configure --libdirs=/usr/lib/ but I have not solved the problem. Please give me advice how to configure VPATH_LIBDIRS.  
 
Regards
 
Cat Le
Logged
Kirus
YaBB Newbie
*



I love YaBB 1G - SP1!

   


Posts: 7
Re: How to compile the code?
« Reply #18 on: 04/27/12 at 03:40:51 »
Quote Quote Modify Modify

I'm getting this error after make core:
 
Compiling C++ file   src/GUI/XWinManaged.C
src/GUI/XWinManaged.C: In member function &#8216;Point2D<int> XWinManaged::getLastMouseClick()&#8217;:
src/GUI/XWinManaged.C:286:16: error: &#8216;ev.XButtonEvent::y&#8217; may be used uninitialized in this function [-Werror=uninitialized]
src/GUI/XWinManaged.C:286:16: error: &#8216;ev.XButtonEvent::x&#8217; may be used uninitialized in this function [-Werror=uninitialized]
cc1plus: all warnings being treated as errors
 
make: *** [build/obj/GUI/XWinManaged.o] Error 1
 
 
any ideas what might be wrong?
Logged
Laurent Itti
YaBB Moderator
YaBB God
*****




iLab rocks!

   
WWW

Gender: male
Posts: 551
Re: How to compile the code?
« Reply #19 on: 05/07/12 at 15:37:57 »
Quote Quote Modify Modify

well, I guess those variables may indeed get used un-initialized, probably this is something that older compilers did not catch but your newer one is now detecting the problem.
 
as we are moving to ubuntu 12.04 here we should soon post corrections to this type of problem in SVN
 
in the meantime, you can edit that file and around line 286 make sure the variable ev gets fully initialized with default values
 
best
 
  -- laurent
Logged
Kirus
YaBB Newbie
*



I love YaBB 1G - SP1!

   


Posts: 7
Re: How to compile the code?
« Reply #20 on: 05/09/12 at 06:01:41 »
Quote Quote Modify Modify

Thanks for the answer.
 
Initializing at line 286 worked for that particular problem, but I have some new ones now.  
 
src/Media/FfmpegDecoder.C: In function &#8216;AVCodec* {anonymous}::findVideoCodec(const char*, AVInputFormat*)&#8217;:
src/Media/FfmpegDecoder.C:142:31: error: &#8216;CODEC_TYPE_VIDEO&#8217; was not declared in this scope
src/Media/FfmpegDecoder.C: In constructor &#8216;FfmpegDecoder::FfmpegDecoder(const char*, int, const char*, bool)&#8217;:
src/Media/FfmpegDecoder.C:190:30: error: &#8216;first_iformat&#8217; was not declared in this scope
src/Media/FfmpegDecoder.C: In member function &#8216;const AVFrame* FfmpegDecoder::readRawFrame()&#8217;:
src/Media/FfmpegDecoder.C:410:53: error: &#8216;avcodec_decode_video&#8217; was not declared in this scope
Command exited with non-zero status 1
<<time>> 1.38 user, 0.08 sys, 0:01.47 elapsed, 99% CPU : build/obj/Media/FfmpegDecoder.o
make: *** [build/obj/Media/FfmpegDecoder.o] Error 1
 
Do you think it would be best for me to just wait for the new version?
 
K
Logged
Laurent Itti
YaBB Moderator
YaBB God
*****




iLab rocks!

   
WWW

Gender: male
Posts: 551
Re: How to compile the code?
« Reply #21 on: 05/09/12 at 09:22:25 »
Quote Quote Modify Modify

Hi -
 
yes, the new error comes from the new version of FFMPEG. Unfortunately the FFMPEG folks keep changing their API and code all the time, so each time you upgrade to a new version you can be sure that some ffmpeg functions have disappeared, or changed names, etc
 
best
 
  -- laurent
Logged
prarobo
YaBB Newbie
*



I love YaBB 1G - SP1!

   


Posts: 11
Re: How to compile the code?
« Reply #22 on: 07/01/12 at 13:40:42 »
Quote Quote Modify Modify

Hey,
 
I have a Ubuntu 11.10
When I try to install with
make core
 
I get the following errors:-
 
Code:
src/Media/FfmpegDecoder.C: In function &#8216;AVCodec* {anonymous}::findVideoCodec(const char*, AVInputFormat*)&#8217;:
src/Media/FfmpegDecoder.C:116:62: error: &#8216;av_open_input_file&#8217; was not declared in this scope
src/Media/FfmpegDecoder.C: In constructor &#8216;FfmpegDecoder::FfmpegDecoder(const char*, int, const char*, bool)&#8217;:
src/Media/FfmpegDecoder.C:187:16: error: &#8216;avcodec_init&#8217; was not declared in this scope
make: *** [build/obj/Media/FfmpegDecoder.o] Error 1

 
I have ffmpeg - 0.11 (latest version)
 
I tried finding patches, but still unsuccessful.
Any advise?
 
Thanks
« Last Edit: 07/01/12 at 13:41:45 by prarobo » Logged
rajat3
YaBB Newbie
*



I love YaBB 1G - SP1!

   
WWW

Gender: male
Posts: 2
Re: How to compile the code?
« Reply #23 on: 04/21/14 at 05:11:14 »
Quote Quote Modify Modify

did you find a solution to it?
Logged

iLab.usc.edu
Pages: 1 2  Reply Reply Notify of replies Notify of replies Send Topic Send Topic Print Print

« No topic | Next topic »

iLab Forum » Powered by YaBB !
YaBB 2000-2002,
Xnull. All Rights Reserved.