patrick wrote:
hey guys,

anyone can help me with this:


make[2]: Leaving directory `/home/pat/11h11/yeux/cinelerra-2.1/libsndfile-1.0.11'
make -C quicktime
/bin/sh: -c: line 1: syntax error: unexpected end of file
/bin/sh: i686/c_flags: No such file or directory
/bin/sh: i686/lame_flags: No such file or directory
/bin/sh: i686/objs: No such file or directory
make[2]: Entering directory `/home/pat/11h11/yeux/cinelerra-2.1/quicktime'
make[2]: *** No rule to make target `i686', needed by `all'.  Stop.
make[2]: Leaving directory `/home/pat/11h11/yeux/cinelerra-2.1/quicktime'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/pat/11h11/yeux/cinelerra-2.1'
make: *** [all] Error 2


what should i do?
pat


_______________________________________________
Cinelerra mailing list
[email protected]
https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra

Pat,

This looks a lot like one of the problems I had when I tried to compile on my Debian system using the source code from the Heroine Virtual Ltd web page at: http://heroinewarrior.com/

The problem has to do (I think) with versions of the make program itself. The one in Debian does not handle the form of shell access being used.

So I'd first suggest that you get the source from cvs.cinelerra.org.

But, if you've already got that source, you could take a look in the Makefile at the line involved to see what it's trying to do. I believe it's making a directory called 'i686', and because the 'mkdir' failed, later access to that location also fails. If this is true, just make the directory by hand and comment out the offending line in the Makefile, and see if that fixes the issue.

Be aware that I found this problem with almost every Makefile in the Heroine Virtual source package.

And, if the source you're using is from cvs.cinelerra.org, I'd suggest also filing a bug (but *only* in that case - the source from Heroine Virtual works OK with the make used Red Hat/Fedora, so it's not a bug in that environment).

Bob

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to