Thanks also for the reference to Fedora, I will take a look at the
packages there and see if I can figure out what the difference is.
The problem was fixed during the merger, I recall it being an incorrect
type of escape character. But bug's we find don't automatically create
a new release upstream, and this is actually a build-system bug, which
we have completely replaced and used automake, autoconf etc..
Bob
Pierre Marc Dumuid wrote:
That bug is know but this mail list is dedicated to cinelerraCV not
cinelerra from HW. (P.S. it made fine on Fedora which is what HW uses)
You must be behind a firewall as I could checkout today myself using
the command described at cvs.cinelerra.org.
Pierre
Bob McGowan wrote:
I've downloaded the Cinelerra source from:
http://heroinewarrior.com/download.php3
I run configure without any issues. When I run make, I get the
following error:
$ make
make -f build/Makefile.cinelerra
sh: -c: line 1: syntax error: unexpected end of file
make[1]: Entering directory
`/home/rmcgowan/src/multimedia/cinelerra-2.0'
gcc -c -O2 -fomit-frame-pointer -falign-loops=2 -falign-jumps=2
-falign-functions=2 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
-D_FILE_OFFSET_BITS=64 -I../../freetype-2.1.4/include -I../../
-DHAVE_OSS -DHAVE_FIREWIRE soundtest.c -o i686/soundtest.o
Assembler messages:
FATAL: can't create i686/soundtest.o: No such file or directory
make[1]: *** [i686/soundtest.o] Error 1
make[1]: Leaving directory
`/home/rmcgowan/src/multimedia/cinelerra-2.0'
make: *** [all] Error 2
The reason is that the directory 'i686' does not exist. On
investigation, I find this line in the file 'global_config':
$(shell sh -c 'if ! test -d $(OBJDIR)\; then mkdir $(OBJDIR)\; fi' )
Which, as far as I can tell, is supposed to create directory. The
value of OBJDIR may be 'i686', based on an 'if' test near the
beginning of the file that sets the value of PLUGINDIR.
Note that the first error is in regard to 'sh: -c: ...', so I've
experimented with this type of line in a test makefile. If I remove
the backslashes, and actually assign the non-existent output to a
variable, and so on, I can eventually get it to create a directory.
It would seem to me that this is such an obvious problem that it
would have been found and fixed quickly. Since it hasn't, I wonder
if the build setup is designed for use with some other 'make'
program than the standard Gnu make?
As it happens in a half dozen different places and I've not been
able to grep out the locations of all of them, I'm stuck.
Any suggestions welcome.
FYI, I thought if I could get the source from SVN, I might be able
to get around this, but my connection to the svn server is
rejected. This may be a firewall problem so I'll be trying to do
the same checkout of source later from a different system that
hopefully has no firewall problems. Meaning this may become moot
for me. ;-)
Thanks,
Bob
_______________________________________________
Cinelerra mailing list
[email protected]
https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
_______________________________________________
Cinelerra mailing list
[email protected]
https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
