Hi Hannes, Did you actually look into config.log? You will see the compiler command > that > was used. In my case, there is no -I/something because I have the library > installed in standard locations. > > :)
==== config.log on x264 lines ============== configure:25874: checking for LIBX264 configure:25900: $PKG_CONFIG --exists --print-errors "x264" configure:25903: $? = 0 configure:25939: result: yes configure:25953: checking x264.h usability configure:25965: gcc -c -g -O2 conftest.c >&5 conftest.c:66:18: error: x264.h: No such file or directory configure:25971: $? = 1 configure: failed program was: | /* confdefs.h. */ | | #define PACKAGE_NAME "Cinelerra" | #define PACKAGE_TARNAME "cinelerra" > Perhaps you should do that, too? (/usr/local is sufficiently standard these > days, I think.) > > you are right.... my problem now is, I have to run/compile it on a government system that I can only restart X, mount certain ISO files, and reboot the machine. If I have access to /usr/local that would be awesome and we won't have a problem. > > > > 2. How do I let the configure knows I have liba52 installed at > > > > > > > /local/home/tools/liba52/liba52-0.7.4/sms.Linux-2.6.18-194.26.1.el5.x86_6 > > >4. > > > > > > >gcc-4.1.2.release > > > > > > Setting the environment as above should be sufficient. > > > > and for liba52, digging around the configure file generated, I don't even > > have a way to provide a hook into the configuration process to let the > > configuration knows where liba52 installation is located. Any thoughts on > > this? what environment variable to set? liba52 doesn't support pkg-config > > method and the configure.in is also not using pkg-config to get the > headers > > and the library files. > > You can always say > > xxx=/that/long/path/name > ./configure CC="gcc -I$xxx -L$xxx" CXX="g++ -I$xxx -L$xxx" > > good idea... let me give it a try.... if not, I guess the system admin will have to be the one compiling the package for me since they tie my hands..... thanks -simon > -- Hannes > > _______________________________________________ > Cinelerra mailing list > [email protected] > https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra >
