PDA

View Full Version : Avisynth 3.0 for Linux


Amnon82
8th November 2006, 23:54
Avisynth 3.0 is in the early development (alpha state). Use it if you can use it ;)

Avisynth 3.0 is a powerful frameserver for Windows and Linux. It aims at editing and processing videos in a non linear manner.

http://img376.imageshack.us/img376/7644/avsoutput167ho9.th.png (http://img376.imageshack.us/my.php?image=avsoutput167ho9.png) http://img376.imageshack.us/img376/8477/avs3gtkmain187dr1.th.jpg (http://img376.imageshack.us/my.php?image=avs3gtkmain187dr1.jpg) http://img393.imageshack.us/img393/4337/avs3gtkinfo138xm9.th.png (http://img393.imageshack.us/my.php?image=avs3gtkinfo138xm9.png)

Aviysnth 3.0 is a complete rewrite of Avisynth 2.5, written from scratch by Bidoche (David Pierre). Its advantages compared to Avisynth 2.5 are the following:

* Abstract core layer that allows it to run on Windows and Linux.
* Better cache managing.
* More powerful script langage.
* Some more internal improvements.

On the other hand, the bad news is that the plugins of Avisynth 2.5 are not compatible with the 3.0 version.

Avisynth 3.0 for Linux Homepage (http://avisynth3.unite-video.com/download.html)

____________________________________________________________

AVISynth 3.0 is supported by followed Distros:


Gentoo
Paldo GNU/Linux - How to install AVS (http://forum.paldo.org/index.php?action=topic&topicnr=112&pagenr=1#post617) - Wie man AVS installiert (http://www.phpbbplanet.com/paldo/viewtopic.php?t=21&mforum=paldo)

mod
9th November 2006, 00:19
Ahhh.. it will be a nice weekend..

Amnon82
9th November 2006, 00:26
The bin is not there. If you do a compile or even a deb-file let me know ;) - hate to compile it. atm no time for it.

cya Phil

p.s. I can compile :)

cd ../linux
./booststrap.sh
./configure
make
sudo make install

... or not :(

amnon@amnon-desktop:/media/sda5/Downloads/avisynth-3.0/build/linux$ ./bootstrap.sh
+ Checking autotools versions
+ OS: Linux
./bootstrap.sh: 156: autoconf: not found

Error: autoconf >= 2.50 required (found )
amnon@amnon-desktop:/media/sda5/Downloads/avisynth-3.0/build/linux$ ./bootstrap.sh
+ Checking autotools versions
+ OS: Linux
+ autoconf: autoconf 2.60
./bootstrap.sh: 156: aclocal: not found

Error: aclocal >= 1.7 required (found )
amnon@amnon-desktop:/media/sda5/Downloads/avisynth-3.0/build/linux$


Where do I get aclocal >= 1.7 ?!?

danpos
9th November 2006, 04:29
Where do I get aclocal >= 1.7 ?!?

Ubuntu: Synaptic -> search -> automake (there are several options, I did choose 1.8 ;) ).

Regards,

Amnon82
9th November 2006, 08:55
I'm now in contact with d'Oursse, the one how ported AVISynth 3.0 to linux. In couple of days the bin-files will be fixed. Seems I'll start to help him with avisynth 3.0 :)

Here some news:

AutoQ4 will be a linux release using AVISynth 3.0 as base. Stay tuned for the first alpha release ...

d'Oursse
9th November 2006, 09:06
no no no, I'm not the lead dev of avisynth 3.0 :D It's Bidoche. I'm the commercial guy and did the linux port, that's all. All the great ideas are from Bidoche.

see http://forum.doom9.org/showthread.php?t=75409 for informations about the development.

What I would need are people who know how to create spec and deb files for installing avs3 as a package. ParadoxHeart has already written an ebuild for gentoo.

and of course testers :) I can't test it on all platforms. Right now, avs3 works on my computer (old mandrake, x86) and gentoo (x86 and amd64).

about your error, install autoconf and automake (aclocal comes with the latter).

In addition, I remark that when a autofoo prog is not found, i don't display the correct message. Bug found :D

mod
9th November 2006, 09:34
Ready to test on Ubuntu64 Core2Duo :)

Kurtnoise
9th November 2006, 09:50
Correct me if I'm wrong, avs 3.0 is not stable, right ?

d'Oursse
9th November 2006, 10:15
kurt: no, it's not yet stable. Why ? Did I miss something ? It's not alpha yet. We'll see with Bidoche if we release an alpha with the new parser.

Kurtnoise
9th November 2006, 10:20
No you didn't miss something it's because I read on Amnon's blog that's stable.That's why I was surprised. :D

Sharktooth
9th November 2006, 16:18
No, Avisynth 3 is not stable at all...

Lokean
9th November 2006, 17:45
ParadoxHeart has already written an ebuild for gentoo.
Link please?

Amnon82
9th November 2006, 18:24
@d'Oursse & Kurtnoise13: It was my fault. I reedited my blog and my post above. I thougth it was stable. I won't confuse somebody here. I'm happy that there is a port of AVISynth for linux, so I can start developing AutoQ4. ... I think I forgot automake. Hope I can compile it then. Maybe I'll come up with some debs.

@Lokean: ebuilds of Avisynth 3.0 early alpha (pkg_avisynth3-20060702.tar.bz2) (http://www.unite-video.com/phpbb/download.php?id=2009)

@mod: If you did a compile that works, let me know. (maybe step by step) ;)

Amnon82
9th November 2006, 18:31
Sorry, it is french. I can't french. It is a simple copy-post-add:

C'est assez basique, mais ça vous permettra de vous faire une idée de l'avancement d'avisynth sans trop de difficultés, enfin noramlement Wink

le tar est à décompresser dans votre PORT_DIR_OVERLAY par defautl /usr/local/portage
si necessaire décommentez la variable de /etc/make.conf

tar -xjvf pkg_avisynth3-20060624.tar.bz2 -C /usr/local

ds /etc/portage/package.keywords rajoutez

media-video/avisynth -*


si vous n'êtes pas en ~x86, il vous faut aussi (resp ~amd64):

dev-libs/boost ~x86
dev-libs/STLport ~x86
media-libs/freetype ~x86
media-libs/fontconfig ~x86
dev-libs/liboil ~x86
media-libs/gstreamer ~x86
media-libs/gst-plugins-base ~x86
media-libs/gst-plugins-good ~x86
media-libs/gst-plugins-bad ~x86
media-libs/gst-plugins-ugly ~x86
media-plugins/gst-plugins-ffmpeg ~x86
media-libs/x264-svn-20060618 ~x86
dev-lang/nasm ~x86
sys-devel/gcc ~x86


ensuite dans /etc/portage/package.use

dev-libs/boost bjam threads threadsonly
media-libs/x264-svn gtk

commencez par installer la dernière version de gcc. n'oubliez pas de switcher votre ancienne version après l'installation d'avisynth, si vous ne désirez plus vous servir de gcc 4 pour compiler le reste de votre system (eselect appartient à gentootoolkit)

emerge -av gcc
eselect compiler list
eselect compiler set i686-pc-linux-gnu-4.1.1/vanilla

puis compilez les dépendances d'avisynth :

emerge -avD avisynth

normalement tout devrait compiler sauf avisynth.
je vous laisse créer à la main un lien et faire une copy

ln -s /usr/lib/preloadable_libintl.so /usr/lib/libintl.so


et copier ce qui se trouve ds circular_buffer.zip dans /usr/include/boost

cd ~/
wget http://www.iecn.u-nancy.fr/~torri/files/circular_buffer_v3.7.tar.bz2
tar -xjvf cd circular_buffer
cp -R circular_buffer* /usr/include/boost

et enfin

emerge -av avisynth

pour tester
prener un avi ou un mkv et faites un .avs

GstreamerSource("blood.avi",0,0)

lancez avisynth_test et ouvrez votre .avs vous pouvez ensuite voir les informations de la vidéo et sauvegarder en mkv.

J'espère ne rien avoir oublié vu l'heure tardive

edit : petite erreur da,s le script.

Hope it helps you.

alec_robertson
9th November 2006, 18:57
I tried to compile the latest cvs on debian unstable and get the following error:
../../src/core/block/block.cpp:36: error: specialization of 'avs::block_<align>::block_(int, bool) [with int align = 16]' after instantiation
../../src/core/block/block.cpp:36: error: invalid function declaration
../../src/core/block/block.cpp:41: error: specialization of 'avs::owned_block<align>::owned_block(const avs::PEnvironment&, int, bool) [with int align = 16]' after instantiation
../../src/core/block/block.cpp:41: error: invalid function declaration
make: *** [core/block/block.o] Error 1

My compile sequence is (using gcc-4.1, autoconf-2.60a):
cvs -q -d:pserver:anonymous@avisynth2.cvs.sourceforge.net:/cvsroot/avisynth2 co -r avisynth_3_0 avisynth
cd avisynth/build
tar xvjf circular_buffer_v3.7.tar.bz2 # circular buffer patch
cd circular_buffer
sudo cp -R * /usr/include/boost/
sudo chmod -R a+rx /usr/include/boost/circular*
cd ../linux
sh ./bootstrap.sh
./configure --with-stlport-path=/usr \
--with-boost-includedir-path=/usr/include/boost
make

d'Oursse
9th November 2006, 20:18
amnon: that ebuild is from another guy. There's a better one.

alec_rebertson: strange. I've tried with g++ 4.1 and I don't remember any problem with it. I'll try again.

edit: It compiles here without problem with g++ 4.1.1. Do you have a 64bits computer ?

d'Oursse
9th November 2006, 22:30
amnon82: for circular_buffer, in the doc, you should have read:


cd avisynth/build
tar jxvf circular_buffer_v3.7.tar.bz2
cd circular_buffer
su (give your root password)
cp -R circular_buffer* /usr/local/include/boost-1_33_1/
[ctrl-D] (to return to user mode)


change /usr/local/include/boost-1_33_1/ to /usr/local/include/boost-1_33

For the problem with stlport, it's always the same problems with packagers, who install the files where they want. I'll add some configure options to set the include path of stlport

Thank you for the report.

Amnon82
9th November 2006, 22:37
Here's the link for circular_buffer_v3.7.tar.bz2 (http://avisynth2.cvs.sourceforge.net/*checkout*/avisynth2/avisynth/build/circular_buffer_v3.7.tar.bz2?revision=1.1.2.3&pathrev=avisynth_3_0)

Amnon82
10th November 2006, 00:02
first, the gui will not be built because gtk+ >= 2.8, with -dev packages) is not installed
second, there's an error:

make: *** No rule to make target `sources.inc'. Stop.

but I don't understand it. Verify that, in build/linux/, you have the file sources.inc available

1. Ok, I've to install gtk+ >=2.8 incl dev
2. sources.inc seems to be ok

I rebooted my machine and tried again with a fresh extracted avisynth-3.0.tar.bz2:

amnon@amnon-desktop:/media/sda5/Downloads/avisynth-3.0/build/linux$ /media/sda5/Downloads/avisynth-3.0/build/linux/bootstrap.sh
+ Checking autotools versions
+ OS: Linux
+ autoconf: autoconf 2.60
+ aclocal: aclocal 1.9
+ Creating ./configure
/usr/share/aclocal/glib.m4:8: warning: underquoted definition of AM_PATH_GLIB
run info '(automake)Extending aclocal'
or see http://sources.redhat.com/automake/automake.html#Extending-aclocal
+ Removing files that are not needed
amnon@amnon-desktop:/media/sda5/Downloads/avisynth-3.0/build/linux$ ./configure
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking whether to use default CFLAGS... yes
checking whether to use default CXXFLAGS... yes
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 how to run the C preprocessor... gcc -E
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking how to run the C++ preprocessor... g++ -E
checking whether g++ supports -fvisibility=hidden... "yes"
checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln -s works... yes
checking for ranlib... ranlib
checking for whether to use assembly code... yes
checking for architecture type... ia32
checking for build extensions... .so .a .o
checking for platform specific LDFLAGS/CFLAGS... ok
checking for nasm... yes
checking for nasm patch version... 38
checking for nasm object format... elf
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for FREETYPE... yes
checking for FONTCONFIG... yes
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking malloc.h usability... yes
checking malloc.h presence... yes
checking for malloc.h... yes
checking assert.h usability... yes
checking assert.h presence... yes
checking for assert.h... yes
checking pthread.h usability... yes
checking pthread.h presence... yes
checking for pthread.h... yes
checking time.h usability... yes
checking time.h presence... yes
checking for time.h... yes
checking for clock_gettime in -lrt... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for dlopen in -ldl... yes
checking for dlclose in -ldl... yes
checking for dlsym in -ldl... yes
checking stl/_config.h usability... yes
checking stl/_config.h presence... yes
checking for stl/_config.h... yes
checking for main in -lstlport... yes
checking boost/shared_ptr.hpp usability... yes
checking boost/shared_ptr.hpp presence... yes
checking for boost/shared_ptr.hpp... yes
checking boost/thread/mutex.hpp usability... yes
checking boost/thread/mutex.hpp presence... yes
checking for boost/thread/mutex.hpp... yes
checking boost/circular_buffer.hpp usability... yes
checking boost/circular_buffer.hpp presence... yes
checking for boost/circular_buffer.hpp... yes
checking boost/spirit/phoenix/functions.hpp usability... yes
checking boost/spirit/phoenix/functions.hpp presence... yes
checking for boost/spirit/phoenix/functions.hpp... yes
checking for main in -lboost_thread-gcc-mt-1_33... no
configure: WARNING: Boost library not in /usr/local/lib
checking for boost/shared_ptr.hpp... (cached) yes
checking for boost/thread/mutex.hpp... (cached) yes
checking for boost/circular_buffer.hpp... (cached) yes
checking for boost/spirit/phoenix/functions.hpp... (cached) yes
checking for main in -lboost_thread-gcc-mt-1_33_1... yes
checking for GST... checking for GSTBASE... yes
checking pluginsdir for gstreamer-0.10... /usr/lib/gstreamer-0.10
configure: checking if the gui program can be compiled
checking for GTK... configure: WARNING: Test application not built (gtk+ 2.8 missing)
checking whether the gui program can be compiled... no
configure: creating ./config.status
config.status: creating platform.inc
config.status: creating gen_sources.sh
config.status: creating avisynth-3.0.pc

------------------------------------------------------------------------
Avisynth 3.0 avisynth
------------------------------------------------------------------------

OS..................: linux-gnu

Visibility feature..:
Core debug mode.....: no
ASM support.........: yes

Gui program.........: no

Install path........: /usr/local
binaries..........: ${exec_prefix}/bin
libraries.........: ${exec_prefix}/lib
headers...........: ${prefix}/include/avisynth-3.0
gst-plugins.......: /usr/lib/gstreamer-0.10

Compilation.........: make
Installation........: make install

Make sure that Gst-FFmpeg is installed. Without it, most of
the usual video streams will not be decoded (huffyuv, xvid,
divx, x264 for example). We recommend that you install it

amnon@amnon-desktop:/media/sda5/Downloads/avisynth-3.0/build/linux$ make
D: build
C: ext/gstreamer/gstavs3videosink.c
In file included from ../../src/ext/gstreamer/gstavs3videosink.c:33:
../../src/ext/gstreamer/gstavs3videosink.h:26:21: error: gst/gst.h: No such file or directory
../../src/ext/gstreamer/gstavs3videosink.h:27:34: error: gst/base/gstbasesink.h: No such file or directory
In file included from ../../src/ext/gstreamer/gstavs3videosink.c:33:
../../src/ext/gstreamer/gstavs3videosink.h:44: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘typedef’
../../src/ext/gstreamer/gstavs3videosink.h:53: error: expected specifier-qualifier-list before ‘GstBaseSink’
../../src/ext/gstreamer/gstavs3videosink.h:69: error: expected specifier-qualifier-list before ‘GstBaseSinkClass’
../../src/ext/gstreamer/gstavs3videosink.h:75: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘gst_avs3_video_sink_get_type’
../../src/ext/gstreamer/gstavs3videosink.c:38: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘static’
../../src/ext/gstreamer/gstavs3videosink.c:47: warning: data definition has no type or storage class
../../src/ext/gstreamer/gstavs3videosink.c:47: warning: parameter names (without types) in function declaration
../../src/ext/gstreamer/gstavs3videosink.c:50: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘gst_avs3_video_sink_details’
../../src/ext/gstreamer/gstavs3videosink.c:74: warning: data definition has no type or storage class
../../src/ext/gstreamer/gstavs3videosink.c:74: warning: parameter names (without types) in function declaration
../../src/ext/gstreamer/gstavs3videosink.c:77: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘gst_avs3_video_sink_signals’
../../src/ext/gstreamer/gstavs3videosink.c:88: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘gst_avs3_video_sink_change_state’
../../src/ext/gstreamer/gstavs3videosink.c:91: error: expected ‘)’ before ‘*’ token
../../src/ext/gstreamer/gstavs3videosink.c:95: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
../../src/ext/gstreamer/gstavs3videosink.c:97: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘gst_avs3_video_sink_setcaps’
../../src/ext/gstreamer/gstavs3videosink.c:99: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘gst_avs3_video_sink_preroll’
../../src/ext/gstreamer/gstavs3videosink.c:101: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘gst_avs3_video_sink_render’
../../src/ext/gstreamer/gstavs3videosink.c:113: error: expected ‘)’ before ‘*’ token
../../src/ext/gstreamer/gstavs3videosink.c:125: error: expected ‘)’ before ‘g_class’
../../src/ext/gstreamer/gstavs3videosink.c: In function ‘gst_avs3_video_sink_class_init’:
../../src/ext/gstreamer/gstavs3videosink.c:137: error: ‘GObjectClass’ undeclared (first use in this function)
../../src/ext/gstreamer/gstavs3videosink.c:137: error: (Each undeclared identifier is reported only once
../../src/ext/gstreamer/gstavs3videosink.c:137: error: for each function it appears in.)
../../src/ext/gstreamer/gstavs3videosink.c:137: error: ‘gobject_class’ undeclared (first use in this function)
../../src/ext/gstreamer/gstavs3videosink.c:138: error: ‘GstElementClass’ undeclared (first use in this function)
../../src/ext/gstreamer/gstavs3videosink.c:138: error: ‘gstelement_class’ undeclared (first use in this function)
../../src/ext/gstreamer/gstavs3videosink.c:139: error: ‘GstBaseSinkClass’ undeclared (first use in this function)
../../src/ext/gstreamer/gstavs3videosink.c:139: error: ‘gstbase_sink_class’ undeclared (first use in this function)
../../src/ext/gstreamer/gstavs3videosink.c:141: error: expected expression before ‘)’ token
../../src/ext/gstreamer/gstavs3videosink.c:142: error: expected expression before ‘)’ token
../../src/ext/gstreamer/gstavs3videosink.c:143: error: expected expression before ‘)’ token
../../src/ext/gstreamer/gstavs3videosink.c:145: error: ‘gst_avs3_video_sink_change_state’ undeclared (first use in this function)
../../src/ext/gstreamer/gstavs3videosink.c:147: error: ‘gst_avs3_video_sink_signals’ undeclared (first use in this function)
../../src/ext/gstreamer/gstavs3videosink.c:150: error: ‘G_SIGNAL_RUN_LAST’ undeclared (first use in this function)
../../src/ext/gstreamer/gstavs3videosink.c:151: error: expected expression before ‘GstAvs3VideoSinkClass’
../../src/ext/gstreamer/gstavs3videosink.c:152: error: ‘NULL’ undeclared (first use in this function)
../../src/ext/gstreamer/gstavs3videosink.c:154: error: ‘g_cclosure_marshal_VOID__UINT_POINTER’ undeclared (first use in this function)
../../src/ext/gstreamer/gstavs3videosink.c:155: error: ‘G_TYPE_NONE’ undeclared (first use in this function)
../../src/ext/gstreamer/gstavs3videosink.c:156: error: ‘G_TYPE_INT’ undeclared (first use in this function)
../../src/ext/gstreamer/gstavs3videosink.c:156: error: ‘G_TYPE_POINTER’ undeclared (first use in this function)
../../src/ext/gstreamer/gstavs3videosink.c:158: error: ‘gst_avs3_video_sink_getcaps’ undeclared (first use in this function)
../../src/ext/gstreamer/gstavs3videosink.c:159: error: ‘gst_avs3_video_sink_setcaps’ undeclared (first use in this function)
../../src/ext/gstreamer/gstavs3videosink.c:161: error: ‘gst_avs3_video_sink_preroll’ undeclared (first use in this function)
../../src/ext/gstreamer/gstavs3videosink.c:162: error: ‘gst_avs3_video_sink_render’ undeclared (first use in this function)
../../src/ext/gstreamer/gstavs3videosink.c:164: error: ‘GstAvs3VideoSinkClass’ has no member named ‘seek’
../../src/ext/gstreamer/gstavs3videosink.c:164: error: ‘gst_avs3_video_sink_seek’ undeclared (first use in this function)
../../src/ext/gstreamer/gstavs3videosink.c: At top level:
../../src/ext/gstreamer/gstavs3videosink.c:169: error: expected ‘)’ before ‘*’ token
../../src/ext/gstreamer/gstavs3videosink.c:202: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
../../src/ext/gstreamer/gstavs3videosink.c:213: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘gst_avs3_video_sink_setcaps’
../../src/ext/gstreamer/gstavs3videosink.c:232: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘gst_avs3_video_sink_preroll’
../../src/ext/gstreamer/gstavs3videosink.c:272: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘gst_avs3_video_sink_render’
../../src/ext/gstreamer/gstavs3videosink.c:278: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘gst_avs3_video_sink_change_state’
../../src/ext/gstreamer/gstavs3videosink.c:308: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘plugin_init’
../../src/ext/gstreamer/gstavs3videosink.c:314: error: expected declaration specifiers or ‘...’ before numeric constant
../../src/ext/gstreamer/gstavs3videosink.c:315: error: expected declaration specifiers or ‘...’ before numeric constant
../../src/ext/gstreamer/gstavs3videosink.c:316: error: expected declaration specifiers or ‘...’ before string constant
../../src/ext/gstreamer/gstavs3videosink.c:317: error: expected declaration specifiers or ‘...’ before string constant
../../src/ext/gstreamer/gstavs3videosink.c:318: error: expected declaration specifiers or ‘...’ before ‘plugin_init’
../../src/ext/gstreamer/gstavs3videosink.c:318: error: expected declaration specifiers or ‘...’ before string constant
../../src/ext/gstreamer/gstavs3videosink.c:318: error: expected declaration specifiers or ‘...’ before string constant
../../src/ext/gstreamer/gstavs3videosink.c:318: error: expected declaration specifiers or ‘...’ before string constant
../../src/ext/gstreamer/gstavs3videosink.c:318: error: expected declaration specifiers or ‘...’ before string constant
../../src/ext/gstreamer/gstavs3videosink.c:318: warning: data definition has no type or storage class
make: *** [ext/gstreamer/gstavs3videosink.o] Error 1
amnon@amnon-desktop:/media/sda5/Downloads/avisynth-3.0/build/linux$

I don't know why this happen now, cos in the first try I got until the make install. Now I don't reach that. I'm stuck in "make". So I'm not Jack Bauer, thats why I go to bed now. Hope mod come up with something ;)

Lokean
10th November 2006, 04:55
amnon: that ebuild is from another guy. There's a better one.
Where? Could you please find it for me? I would be really interested in trying it out.

d'Oursse
10th November 2006, 08:03
It was an ebuild from ParadoxHeart. But I don't see her on irc anymore :/

d'Oursse
11th November 2006, 17:18
amnon: Usually, gstreamer is installed in /usr/include. Check if he file gst.h is in /usr/include/gst or not.

Zep
13th November 2006, 10:28
Avisynth 3.0 is in the early development (not even alpha). Use it if you can use it ;)

Avisynth 3.0 is a powerful frameserver for Windows and Linux. It aims at editing and processing videos in a non linear manner.


and Mac OSX

IIRC one of the coders is coding on a OSX box.

Amnon82
13th November 2006, 10:28
I'll do a clean install of Ubuntu 6.06 right now. After a backup of the partition with partimage I'll play again with compiling AVS3.0 from the scratch.

d'Oursse
13th November 2006, 10:45
in fact, we try to use libs (stlport and boost) than work on a lot of platforms, including Windows, Linux, Solaris, *BSD and Mac OS X.
Bidoche is using Windows with a Microsoft compiler, and I use Linux with an old distro.

I tried to compile gstreamer on Mac OS X (with compilefarm on SourceForge), but I had problems. Right now, I only know that avs3 works on Windows and Linux, as I didn't have any report on other platforms.

Blue_MiSfit
13th November 2006, 12:15
Sorry if this is a bit OT, but will there by any possibility for an equivalent for LoadPluginEX wrapper for AviSynth 3.0?

In other words, is it technically possible to load plugins written for 2.5 into 3.0?

I know it's way too early to tell, and that 3.0 is nowhere near being actually usable, but I am curious as to how things will work once it's matured a bit. Will plugin developers have to start over from scratch? Will it be easy to adapt existing plugins? Will said wrapper be possible?

Sorry if I'm being speculative or asking foolish questions, but I'm rather curious! AviSynth on Mac OS X would be.... insane.

~MiSfit

d'Oursse
15th November 2006, 19:06
yes, it is possible. It is not implemented yet. And it will be more difficult than loadpluginex.

Blue_MiSfit
16th November 2006, 11:36
Open source amazes me.

Thank you developers for all your hard work! AviSynth blows away the competition.

nfm
19th November 2006, 00:12
I get this error, same as alec_robertson's one
C: core/block/block.cpp
../../src/core/block/block.cpp:36: error: specialization of ‘avs::block_<align>::block_(int, bool) [with int align = 16]’ after instantiation
../../src/core/block/block.cpp:36: error: invalid function declaration
../../src/core/block/block.cpp:41: error: specialization of ‘avs::owned_block<align>::owned_block(const avs::PEnvironment&, int, bool) [with int align = 16]’ after instantiation
../../src/core/block/block.cpp:41: error: invalid function declaration
make: *** [core/block/block.o] Error 1

I'm running:
- Ubuntu 6.10 i386
- gcc 4.1.1
- kernel smp 2.6.18.2

Edited typos ^

d'Oursse
19th November 2006, 08:14
do you have gcc 4.1.0 or 4.1.1 ?
Also, can you try with gcc 4.0.* ?

Carpo
19th November 2006, 12:14
i would say to use a 3.x.x version of gcc - as i have heard many ppl say they cant compile stuff using gcc 4.x

has anyone tried this on slackware ?

d'Oursse
19th November 2006, 16:23
I've compiled avs3 with g++ 3.3.*, 4.0.(0, 1, 2, 3) and 4.1.1
avs3 will not compile with 3.4.6, iirc (problem with templates)
I also compiled myself these versions of gcc. I do not use packages.

Amnon82
20th November 2006, 11:59
Seems I don't get it.

amnon@amnon-desktop:~/avs3_tmp/avisynth/build/linux$ ~/avs3_tmp/avisynth/build/linux/configure
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking whether to use default CFLAGS... yes
checking whether to use default CXXFLAGS... yes
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 ANSI C... none needed
checking how to run the C preprocessor... gcc -E
checking for __attribute__... yes
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking how to run the C++ preprocessor... g++ -E
checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln -s works... yes
checking for ranlib... ranlib
checking for whether to use assembly code... yes
checking for architecture type... ia32
checking for build extensions... .so .a .o
checking for platform specific LDFLAGS/CFLAGS... ok
checking for nasm... yes
checking for nasm patch version... 38
checking for nasm object format... elf
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for FREETYPE... yes
checking for FONTCONFIG... yes
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking pthread.h usability... yes
checking pthread.h presence... yes
checking for pthread.h... yes
checking time.h usability... yes
checking time.h presence... yes
checking for time.h... yes
checking for clock_gettime in -lrt... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for dlopen in -ldl... yes
checking for dlclose in -ldl... yes
checking for dlsym in -ldl... yes
checking stl/config/user_config.h usability... no
checking stl/config/user_config.h presence... no
checking for stl/config/user_config.h... no
configure: WARNING: STLport headers not in /usr/local/include/stlport
configure: error: "STLport is needed !"


now it is STLport again. Seems Ubuntu 6.06 won't run AVS3.0 or I'm to stupied to compile.

d'Oursse
20th November 2006, 13:47
It's my fault: i've modified the check of stlport and try to detect STLport 5.1. You have 2 solutions
1) check out avs3 again (i've corrected the check)
2) install STLport 5.1 RC3

Amnon82
20th November 2006, 21:48
I used your CVS-Build you linked me. Btw. what distro do you use?

d'Oursse
21st November 2006, 07:35
ha, that's right, I remember. Can't you install cvs ? It should be easy with synaptic

I use an old mandrake 10.0 or 10.1, which now looks more like a LFS :D

alec_robertson
22nd November 2006, 19:25
do you have gcc 4.1.0 or 4.1.1 ? Also, can you try with gcc 4.0.* ?

Version 4.1.1 gives me the error, but gcc-4.0 (ver 4.0.3) compiles fine.

d'Oursse
22nd November 2006, 19:33
Then, it's a problem with your version of gcc 4.1.1. I don't know if you are aware of that, but packagers apply sometimes patches to the progs/libs. That may be the source of the problem, if you have installed gcc 4.1.1 with a package manager.

As I said, I compile myself the different versions of gcc that I'm using.

alec_robertson
22nd November 2006, 19:41
Interesting, I'm using debian unstable's standard gcc-4.1 but this is the first time I've had problems compiling.

Amnon82
22nd November 2006, 22:15
Well. I installed now openSUSE 10.1. Will try it with Suse ...

Teegedeck
24th November 2006, 14:42
(openSUSE 10.2 is scheduled for release on Dec. 7th.)

Sharktooth
24th November 2006, 15:01
Ah! I hope my ISP fixes the low SNR im having these days so they can restore my 20Mbits connection so i can get the DVD edition of suse 10.2 without too much headaches and test if AVS3.0 compiles on it.

Amnon82
26th November 2006, 01:56
I'll try soon to compile AVS3.0 for my own Paldo-Linux. Fly by on www.paldo.org to get more info about the distribution of my friends and me.

d'Oursse
26th November 2006, 09:22
it seems that the bug above is a bug in avisynth which was not found by older compilers that g++ 4.1.1 (inluding this release). Some distro include a patch to notify it. That's why I don't have it. I'll try to fix it.

dirio49
30th November 2006, 03:03
Has anybody tried to install in gentoo?
Thanks

BTW, I am trying now will see how it goes.

ak
30th November 2006, 18:59
Has anybody tried to install in gentoo?


Yes. But then like whole *nix build system was removed in one CVS commit (IIRC). Makes you wonder is it really worth the hassle yet.

shevegen
1st December 2006, 06:56
hey hey hey patience guys ;)

Years back I was unhappy that I had to leave my favourite Windows App (when i switched to Linux).

It was one application which made me curious into "scripting" again :-)

Good code takes time!

d'Oursse
1st December 2006, 08:09
I know 2 persons who built avs3 on gentoo (x86 and amd64). I also have an ebuild. I'll add it to the cvs.

If some people are skilled in writing rpm or deb files, I would be glad to add those for avs3 too.

Sharktooth
7th December 2006, 16:10
built avs3 on sabayon (gentoo) and works.

Gusar
7th December 2006, 20:45
I have a question: Is the dependency on gstreamer fixed, or will we be able to use avs3 without gstreamer at some point in the future?

d'Oursse
7th December 2006, 20:54
on linux (and other unixes), it will be only gstreamer. On windows, There will be the same as what is in avs 2.5 (avi, directshow).

Gstreamer is the only framework (on linux) that I know and which is able to do what we want in avs

Do you have a suggestion ?

Gusar
8th December 2006, 00:30
Do you have a suggestion ?Not really, I was just curious. FFmpeg is the only thing that comes close I guess, but you probably already checked that and found that it doesn't offer everything you need.

Thanks for the information and thanks for all your work, having avisynth natively on linux will be huge.


Oh, another thing: I checked the cvs and didn't see an ebuild there. Am I blind or is it not there yet?

isolationism
8th December 2006, 07:18
d'Oursse, laisse-moi vous dire merci pour vos efforts sur Avisynth 3.

I'm excited that I'll soon be able to use it to encode video; all my horsepower is locked up in 64-bit Linux machines running Gentoo right now. I tried to install from source earlier this week but got stuck with problems with missing libraries.

I too would love to get my hands on that (those?) ebuild(s). I checked out the CVS module today but wasn't able to find any ebuilds or references to Gentoo. I'm sure you're very busy; when you have a moment could you touch the thread to let us fanatics know? Thanks again!

Edit: Speedy reply, d'Oursse! Here's hoping you find time today.

d'Oursse
8th December 2006, 08:16
about ffmpeg, gstreamer already includes ffmpeg, so no need to use it directly.
About the ebuild, I'm lazy, it's not in cvs. But I have it on my hd :) I'll try to do that today

ak
14th December 2006, 15:30
I too would love to get my hands on that (those?) ebuild(s).

Here's one: https://opensvn.csie.org/4nykey/portage/media-video/avisynth/avisynth-9999.ebuild

It didn't build for me, last time I tried, maybe you'll be more lucky.

d'Oursse
14th December 2006, 18:21
some patches are in, as well as the ebuild in build/linux/gentoo

isolationism
14th December 2006, 18:50
Awesome, d'Oursse, thank you. I've updated my local copy and grabbed the ebuild.

On to the next problem ... ;) boost-circular-buffer doesn't have an ebuild currently in portage, but the avisynth-cvs ebuild requires it. I'm assuming the circular-buffer ebuild is already out there, just not in avisynth's cvs folder. Any idea where I could find it?

Edit: Thank you again d'Oursse!

d'Oursse
14th December 2006, 19:23
there's an ebuild. Check that post, I'll edit it when the ebuild is in

Edit: the ebuild is in

isolationism
19th December 2006, 06:38
Okay, progress:

- boost-circular-buffer compiled fine using the provided ebuild and the appropriate archive copied to /usr/portage/distfiles. You can probably mark this ~amd64 (currently x86 is the only keyword).

- When I went to emerge avisynth-cvs, it updated stlport and x264-svn. I had to add "dev-libs/STLport ~amd64" to package.keywords, but it compiled fine.

- Emerging avisynth-cvs itself failed, however, with an error regarding x264-svn not supporting the gtk flag. The actual error is below:

!!! ERROR: media-video/avisynth-cvs-3.0 failed.
Call stack:
ebuild.sh, line 1562: Called dyn_setup
ebuild.sh, line 665: Called pkg_setup
avisynth-cvs-3.0.ebuild, line 45: Called built_with_use 'media-libs/x264-svn' 'gtk'
eutils.eclass, line 1617: Called die

!!! media-libs/x264-svn-20061014-r1 does not actually support the gtk USE flag!
!!! If you need support, post the topmost build error, and the call stack if relevant.

!!! This ebuild is from an overlay: '/usr/local/portage'


Any thoughts as to what might be up? I have 'gtk' specified in my USE flags but true to the error above, "emerge -pv x264-svn" only has the "debug" and "threads" use flags, both of which are disabled for me.

ParadoxHeart
19th December 2006, 09:36
The AviSynth ebuild checks the x264-svn ebuilld to see whether the gtk use flag is enabled, if you have the avisynth gtk use flag enabled (which controls whether or not the GUI program is built). The x264-svn in the main tree doesn't have a gtk use flag yet as I haven't yet got around to asking the package maintainers to add one.

For the purposes of testing I added an overlay x264-svn ebuild with a gtk use flag. I could ask for the overlay ebuild to be added to the AviSynth CVS but it would probably be more productive to get it in the main portage tree. Not that it is all that important right away as Gentoo's (and other distro's) GCC 4.1.1 contains a bug fix not present in the original release of GCC 4.1.1 that picks up on an error in AviSynth's code and causes the build to fail (this is why the specialization after initialisation errors that people have been getting happens). So unless you use an older GCC it won't build yet anyway. :-)

EDIT: It appears that there is now an x264-svn-encoder ebuild in portage with a gtk use flag. I shall adjust the AviSynth ebuild to use this and have it submitted to the CVS.

isolationism
19th December 2006, 17:02
Bummer. I am indeed using the latest GCC (although this is the first time doing so has been a hindrance instead of a help :) ). I haven't quite got to that stage yet, though, but no rush. Thanks for the explanation, ParadoxHeart. I'll update CVS in a day or two to look for your commit and try again (even if I can't yet go "all the way", I can at least get the dependencies wrapped up).

d'Oursse
19th December 2006, 19:10
ebuild updated

Amnon82
19th December 2006, 22:47
did someone a deb? ... I don't have the time for it atm.

isolationism
21st December 2006, 04:12
Okay, looks good. After using the new ebuild and placing the patch file in the package's files/ directory, the x264 encoder was compiled and then avisynth-cvs started compiling. It succeeded up to this point:
C: core/block/holder/ownedsplitting.cpp
../../src/core/block/block.cpp:36: error: specialization of 'avs::block_<align>::block_(int, bool) [with int align = 16]' after instantiation
../../src/core/block/block.cpp:36: error: invalid function declaration
../../src/core/block/block.cpp:41: error: specialization of 'avs::owned_block<align>::owned_block(const avs::PEnvironment&, int, bool) [with int align = 16]' after instantiation
../../src/core/block/block.cpp:41: error: invalid function declaration
make: *** [core/block/block.o] Error 1
make: *** Waiting for unfinished jobs....
C: core/block/holder/ownedstandard.cpp

!!! ERROR: media-video/avisynth-cvs-3.0 failed.
Call stack:
ebuild.sh, line 1546: Called dyn_compile
ebuild.sh, line 937: Called src_compile
avisynth-cvs-3.0.ebuild, line 74: Called die

... Which is probably as far as I can get using GCC 4.1.1 (as it was noted that AviSynth doesn't compile with the latest GCC yet).

d'Oursse
21st December 2006, 07:37
yes, problem with gcc 4.1.1. Btw, we'll rewrite the Block class in a near future

d'Oursse
28th December 2006, 14:01
now, avisynth uses STLport 5.1. I've also updated the ebuild (I hope that it's correct)

isolationism
28th December 2006, 19:07
Hey d'Oursse, thanks for the update. Does STLport affect the block class mentioned above (e.g. make AVISynth compilable in GCC 4.1), or is it unrelated?

d'Oursse
28th December 2006, 19:29
not at all, it's a compiler bug, not a STLport one. But that newer version fixes a bunch of bugs in STLport and improves some stuff too. So I prefered to bump the version.

Sirber
30th December 2006, 22:36
Will the usage be the same for windows and linux?
I mean the execution, not the .avs ;)

d'Oursse
31st December 2006, 10:10
except the sources specific to the OS, yes. Even the scripts will be the same, except the sources :)

Amnon82
1st January 2007, 11:03
I'm just on installing AVS 3.0 on Debian 4.0. BJAM is installed. Here is the List

BOOST BUILD

/.
/etc
/etc/user-config.jam
/etc/site-config.jam
/usr
/usr/share
/usr/share/doc
/usr/share/doc/boost-build
/usr/share/doc/boost-build/html
/usr/share/doc/boost-build/html/jam
/usr/share/doc/boost-build/html/jam/building.html
/usr/share/doc/boost-build/html/jam/miscellaneous.html
/usr/share/doc/boost-build/html/jam/language.html
/usr/share/doc/boost-build/html/jam/usage.html
/usr/share/doc/boost-build/html/bbv2
/usr/share/doc/boost-build/html/bbv2/faq
/usr/share/doc/boost-build/html/bbv2/faq/s02.html
/usr/share/doc/boost-build/html/bbv2/faq/s04.html
/usr/share/doc/boost-build/html/bbv2/faq/s05.html
/usr/share/doc/boost-build/html/bbv2/faq/s07.html
/usr/share/doc/boost-build/html/bbv2/faq/s08.html
/usr/share/doc/boost-build/html/bbv2/faq/dll-path.html
/usr/share/doc/boost-build/html/bbv2/faq/envar.html
/usr/share/doc/boost-build/html/bbv2/faq/external.html
/usr/share/doc/boost-build/html/bbv2/faq/header-only-libraries.html
/usr/share/doc/boost-build/html/bbv2/arch
/usr/share/doc/boost-build/html/bbv2/arch/tools.html
/usr/share/doc/boost-build/html/bbv2/arch/targets.html
/usr/share/doc/boost-build/html/bbv2/arch/build.html
/usr/share/doc/boost-build/html/bbv2/advanced.html
/usr/share/doc/boost-build/html/bbv2/extender.html
/usr/share/doc/boost-build/html/bbv2/howto.html
/usr/share/doc/boost-build/html/bbv2/faq.html
/usr/share/doc/boost-build/html/bbv2/installation.html
/usr/share/doc/boost-build/html/bbv2/arch.html
/usr/share/doc/boost-build/html/bbv2/jam.html
/usr/share/doc/boost-build/html/bbv2/reference.html
/usr/share/doc/boost-build/html/bbv2/tutorial.html
/usr/share/doc/boost-build/html/bbv2/tutorial
/usr/share/doc/boost-build/html/bbv2/tutorial/conditions.html
/usr/share/doc/boost-build/html/bbv2/tutorial/libs.html
/usr/share/doc/boost-build/html/bbv2/tutorial/hierarchy.html
/usr/share/doc/boost-build/html/bbv2/tutorial/testing.html
/usr/share/doc/boost-build/html/bbv2/tutorial/prebuilt.html
/usr/share/doc/boost-build/html/bbv2/tutorial/linkage.html
/usr/share/doc/boost-build/html/bbv2/tutorial/properties.html
/usr/share/doc/boost-build/html/bbv2/extending
/usr/share/doc/boost-build/html/bbv2/extending/features.html
/usr/share/doc/boost-build/html/bbv2/extending/tools.html
/usr/share/doc/boost-build/html/bbv2/extending/toolset_modules.html
/usr/share/doc/boost-build/html/bbv2/extending/targets.html
/usr/share/doc/boost-build/html/bbv2/extending/rules.html
/usr/share/doc/boost-build/html/bbv2/reference
/usr/share/doc/boost-build/html/bbv2/reference/definitions.html
/usr/share/doc/boost-build/html/bbv2/reference/jamfiles.html
/usr/share/doc/boost-build/html/bbv2/reference/buildprocess.html
/usr/share/doc/boost-build/html/bbv2/reference/generators.html
/usr/share/doc/boost-build/html/bbv2/advanced
/usr/share/doc/boost-build/html/bbv2/advanced/projects.html
/usr/share/doc/boost-build/html/bbv2/advanced/differences_to_v1.html
/usr/share/doc/boost-build/html/bbv2/advanced/build_process.html
/usr/share/doc/boost-build/html/bbv2/advanced/targets.html
/usr/share/doc/boost-build/html/bbv2/advanced/builtins
/usr/share/doc/boost-build/html/bbv2/advanced/builtins/features.html
/usr/share/doc/boost-build/html/bbv2/advanced/builtins/targets.html
/usr/share/doc/boost-build/html/bbv2/advanced/other-rules.html
/usr/share/doc/boost-build/html/bbv2/advanced/configuration.html
/usr/share/doc/boost-build/html/bbv2/advanced/invocation.html
/usr/share/doc/boost-build/html/bbv2/recipies
/usr/share/doc/boost-build/html/bbv2/recipies/site-config.html
/usr/share/doc/boost-build/html/index.html
/usr/share/doc/boost-build/html/HTML.manifest
/usr/share/doc/boost-build/html/images
/usr/share/doc/boost-build/html/images/warning.png
/usr/share/doc/boost-build/html/images/toc-blank.png
/usr/share/doc/boost-build/html/images/blank.png
/usr/share/doc/boost-build/html/images/note.png
/usr/share/doc/boost-build/html/images/toc-plus.png
/usr/share/doc/boost-build/html/images/next_disabled.png
/usr/share/doc/boost-build/html/images/important.png
/usr/share/doc/boost-build/html/images/tip.png
/usr/share/doc/boost-build/html/images/home.png
/usr/share/doc/boost-build/html/images/toc-minus.png
/usr/share/doc/boost-build/html/images/up_disabled.png
/usr/share/doc/boost-build/html/images/prev.png
/usr/share/doc/boost-build/html/images/up.png
/usr/share/doc/boost-build/html/images/prev_disabled.png
/usr/share/doc/boost-build/html/images/next.png
/usr/share/doc/boost-build/html/images/draft.png
/usr/share/doc/boost-build/html/images/caution.png
/usr/share/doc/boost-build/html/boostbook.css
/usr/share/doc/boost-build/example
/usr/share/doc/boost-build/example/qt
/usr/share/doc/boost-build/example/qt/qt3
/usr/share/doc/boost-build/example/qt/qt3/uic
/usr/share/doc/boost-build/example/qt/qt3/uic/Jamroot
/usr/share/doc/boost-build/example/qt/qt3/uic/main.cpp
/usr/share/doc/boost-build/example/qt/qt3/uic/hello_world_widget.ui
/usr/share/doc/boost-build/example/qt/qt3/hello
/usr/share/doc/boost-build/example/qt/qt3/hello/Jamroot
/usr/share/doc/boost-build/example/qt/qt3/hello/main.cpp
/usr/share/doc/boost-build/example/qt/qt3/hello/canvas.h
/usr/share/doc/boost-build/example/qt/qt3/hello/canvas.cpp
/usr/share/doc/boost-build/example/qt/qt3/moccable-cpp
/usr/share/doc/boost-build/example/qt/qt3/moccable-cpp/Jamroot
/usr/share/doc/boost-build/example/qt/qt3/moccable-cpp/main.cpp
/usr/share/doc/boost-build/example/qt/qt4
/usr/share/doc/boost-build/example/qt/qt4/uic
/usr/share/doc/boost-build/example/qt/qt4/uic/Jamroot
/usr/share/doc/boost-build/example/qt/qt4/uic/main.cpp
/usr/share/doc/boost-build/example/qt/qt4/uic/hello_world_widget.ui
/usr/share/doc/boost-build/example/qt/qt4/hello
/usr/share/doc/boost-build/example/qt/qt4/hello/Jamroot
/usr/share/doc/boost-build/example/qt/qt4/hello/main.cpp
/usr/share/doc/boost-build/example/qt/qt4/hello/arrow.cpp
/usr/share/doc/boost-build/example/qt/qt4/hello/arrow.h
/usr/share/doc/boost-build/example/qt/qt4/moccable-cpp
/usr/share/doc/boost-build/example/qt/qt4/moccable-cpp/Jamroot
/usr/share/doc/boost-build/example/qt/qt4/moccable-cpp/main.cpp
/usr/share/doc/boost-build/example/qt/README.txt
/usr/share/doc/boost-build/example/customization
/usr/share/doc/boost-build/example/customization/class.verbatim
/usr/share/doc/boost-build/example/customization/codegen.cpp
/usr/share/doc/boost-build/example/customization/t2.verbatim
/usr/share/doc/boost-build/example/customization/Jamfile
/usr/share/doc/boost-build/example/customization/verbatim.jam
/usr/share/doc/boost-build/example/customization/inline_file.py
/usr/share/doc/boost-build/example/customization/usage.verbatim
/usr/share/doc/boost-build/example/customization/readme.txt
/usr/share/doc/boost-build/example/customization/project-root.jam
/usr/share/doc/boost-build/example/customization/t1.verbatim
/usr/share/doc/boost-build/example/python_modules
/usr/share/doc/boost-build/example/python_modules/Jamroot
/usr/share/doc/boost-build/example/python_modules/readme.txt
/usr/share/doc/boost-build/example/python_modules/python_helpers.py
/usr/share/doc/boost-build/example/python_modules/python_helpers.jam
/usr/share/doc/boost-build/example/boost-build.jam
/usr/share/doc/boost-build/example/hello
/usr/share/doc/boost-build/example/hello/Jamroot
/usr/share/doc/boost-build/example/hello/hello.cpp
/usr/share/doc/boost-build/example/libraries
/usr/share/doc/boost-build/example/libraries/app
/usr/share/doc/boost-build/example/libraries/app/Jamfile
/usr/share/doc/boost-build/example/libraries/app/app.cpp
/usr/share/doc/boost-build/example/libraries/util
/usr/share/doc/boost-build/example/libraries/util/foo
/usr/share/doc/boost-build/example/libraries/util/foo/Jamfile
/usr/share/doc/boost-build/example/libraries/util/foo/bar.cpp
/usr/share/doc/boost-build/example/libraries/util/foo/include
/usr/share/doc/boost-build/example/libraries/util/foo/include/lib1.h
/usr/share/doc/boost-build/example/libraries/Jamroot
/usr/share/doc/boost-build/example/gettext
/usr/share/doc/boost-build/example/gettext/Jamfile
/usr/share/doc/boost-build/example/gettext/main.cpp
/usr/share/doc/boost-build/example/gettext/readme.txt
/usr/share/doc/boost-build/example/gettext/project-root.jam
/usr/share/doc/boost-build/example/gettext/russian.po
/usr/share/doc/boost-build/example/variant
/usr/share/doc/boost-build/example/variant/libs
/usr/share/doc/boost-build/example/variant/libs/l.cpp
/usr/share/doc/boost-build/example/variant/libs/Jamfile
/usr/share/doc/boost-build/example/variant/a.cpp
/usr/share/doc/boost-build/example/variant/Jamfile
/usr/share/doc/boost-build/example/variant/readme.txt
/usr/share/doc/boost-build/example/variant/project-root.jam
/usr/share/doc/boost-build/copyright
/usr/share/doc/boost-build/changelog.Debian.gz
/usr/share/boost-build
/usr/share/boost-build/util
/usr/share/boost-build/util/sequence.jam
/usr/share/boost-build/util/utility.jam
/usr/share/boost-build/util/doc.jam
/usr/share/boost-build/util/set.jam
/usr/share/boost-build/util/option.jam
/usr/share/boost-build/util/assert.jam
/usr/share/boost-build/util/path.jam
/usr/share/boost-build/util/string.jam
/usr/share/boost-build/util/indirect.jam
/usr/share/boost-build/util/order.jam
/usr/share/boost-build/util/container.jam
/usr/share/boost-build/util/os.jam
/usr/share/boost-build/util/regex.jam
/usr/share/boost-build/util/numbers.jam
/usr/share/boost-build/util/print.jam
/usr/share/boost-build/boost-build.jam
/usr/share/boost-build/build
/usr/share/boost-build/build/targets.jam
/usr/share/boost-build/build/type.jam
/usr/share/boost-build/build/project.jam
/usr/share/boost-build/build/property-set.jam
/usr/share/boost-build/build/feature.jam
/usr/share/boost-build/build/version.jam
/usr/share/boost-build/build/virtual-target.jam
/usr/share/boost-build/build/scanner.jam
/usr/share/boost-build/build/modifiers.jam
/usr/share/boost-build/build/alias.jam
/usr/share/boost-build/build/property.jam
/usr/share/boost-build/build/readme.txt
/usr/share/boost-build/build/toolset.jam
/usr/share/boost-build/build/generators.jam
/usr/share/boost-build/build/build-request.jam
/usr/share/boost-build/notes
/usr/share/boost-build/notes/build_dir_option.txt
/usr/share/boost-build/notes/relative_source_paths.txt
/usr/share/boost-build/notes/README.txt
/usr/share/boost-build/tools
/usr/share/boost-build/tools/quickbook-config.jam
/usr/share/boost-build/tools/hpfortran.jam
/usr/share/boost-build/tools/testing.jam
/usr/share/boost-build/tools/xlf.jam
/usr/share/boost-build/tools/hp_cxx.jam
/usr/share/boost-build/tools/qt3.jam
/usr/share/boost-build/tools/qt4.jam
/usr/share/boost-build/tools/intel-linux.jam
/usr/share/boost-build/tools/como-win.jam
/usr/share/boost-build/tools/unix.jam
/usr/share/boost-build/tools/msvc.jam
/usr/share/boost-build/tools/dmc.jam
/usr/share/boost-build/tools/docutils.jam
/usr/share/boost-build/tools/types
/usr/share/boost-build/tools/types/cpp.jam
/usr/share/boost-build/tools/types/html.jam
/usr/share/boost-build/tools/types/lib.jam
/usr/share/boost-build/tools/types/rsp.jam
/usr/share/boost-build/tools/types/exe.jam
/usr/share/boost-build/tools/types/obj.jam
/usr/share/boost-build/tools/types/qt.jam
/usr/share/boost-build/tools/types/register.jam
/usr/share/boost-build/tools/types/asm.jam
/usr/share/boost-build/tools/package.jam
/usr/share/boost-build/tools/lex.jam
/usr/share/boost-build/tools/xsltproc.jam
/usr/share/boost-build/tools/vacpp.jam
/usr/share/boost-build/tools/gfortran.jam
/usr/share/boost-build/tools/doxygen.jam
/usr/share/boost-build/tools/notfile.jam
/usr/share/boost-build/tools/boostbook-config.jam
/usr/share/boost-build/tools/make.jam
/usr/share/boost-build/tools/midl.jam
/usr/share/boost-build/tools/gcc.jam
/usr/share/boost-build/tools/sun.jam
/usr/share/boost-build/tools/cw.jam
/usr/share/boost-build/tools/como.jam
/usr/share/boost-build/tools/fop.jam
/usr/share/boost-build/tools/cast.jam
/usr/share/boost-build/tools/python-config.jam
/usr/share/boost-build/tools/ifort.jam
/usr/share/boost-build/tools/python.jam
/usr/share/boost-build/tools/mc.jam
/usr/share/boost-build/tools/acc.jam
/usr/share/boost-build/tools/stlport.jam
/usr/share/boost-build/tools/kylix.jam
/usr/share/boost-build/tools/stage.jam
/usr/share/boost-build/tools/como-linux.jam
/usr/share/boost-build/tools/rc.jam
/usr/share/boost-build/tools/qt.jam
/usr/share/boost-build/tools/whale.jam
/usr/share/boost-build/tools/darwin.jam
/usr/share/boost-build/tools/boostbook.jam
/usr/share/boost-build/tools/msvc-config.jam
/usr/share/boost-build/tools/gettext.jam
/usr/share/boost-build/tools/intel-win.jam
/usr/share/boost-build/tools/xsltproc-config.jam
/usr/share/boost-build/tools/pch.jam
/usr/share/boost-build/tools/quickbook.jam
/usr/share/boost-build/tools/borland.jam
/usr/share/boost-build/tools/doxygen-config.jam
/usr/share/boost-build/tools/builtin.jam
/usr/share/boost-build/tools/intel.jam
/usr/share/boost-build/tools/qcc.jam
/usr/share/boost-build/tools/common.jam
/usr/share/boost-build/tools/bison.jam
/usr/share/boost-build/tools/fortran.jam
/usr/share/boost-build/tools/cw-config.jam
/usr/share/boost-build/tools/symlink.jam
/usr/share/boost-build/build-system.jam
/usr/share/boost-build/bootstrap.jam
/usr/share/boost-build/kernel
/usr/share/boost-build/kernel/boost-build.jam
/usr/share/boost-build/kernel/bootstrap.jam
/usr/share/boost-build/kernel/errors.jam
/usr/share/boost-build/kernel/class.jam
/usr/share/boost-build/kernel/modules.jam
/usr/share/boost-build/timestamp.txt
/usr/share/boost-build/user-config.jam
/usr/share/boost-build/options
/usr/share/boost-build/options/help.jam

BJAM
/.
/usr
/usr/bin
/usr/bin/bjam
/usr/share
/usr/share/doc
/usr/share/doc/bjam
/usr/share/doc/bjam/jam
/usr/share/doc/bjam/jam/building.html
/usr/share/doc/bjam/jam/miscellaneous.html
/usr/share/doc/bjam/jam/language.html
/usr/share/doc/bjam/jam/usage.html
/usr/share/doc/bjam/index.html
/usr/share/doc/bjam/copyright
/usr/share/doc/bjam/Jambase.gz
/usr/share/doc/bjam/changelog.Debian.gz
/usr/share/man
/usr/share/man/man1
/usr/share/man/man1/bjam.1.gz

Avisynth 3.0 needs an extension of Boost that is not in the current version of Boost. Nevertheless, we have included it in our tree. Here is how to install it if Boost is installed in usr/local:
cd avisynth/build
tar jxvf circular_buffer_v3.7.tar.bz2
cd circular_buffer
su (give your root password)
cp -R circular_buffer* /usr/local/include/boost-1_33_1/boost
[ctrl-D] (to return to user mode)

... so which path will it be for Debian, if I use the Deb-Packs?

http://img177.imageshack.us/img177/2424/screenshotsynapticpackajm5.th.png (http://img177.imageshack.us/my.php?image=screenshotsynapticpackajm5.png) http://img299.imageshack.us/img299/6127/screenshotsynapticpackawv8.th.png (http://img299.imageshack.us/my.php?image=screenshotsynapticpackawv8.png)

d'Oursse
1st January 2007, 11:53
I think that all the needed packages are installed (libboost-dev, and libboost-thread*)

Now, you have to check where the header files are installed. I guess that they are installed in /usr/include/boost. Then, the commands to install circular buffer are:


cd avisynth/build
tar jxvf circular_buffer_v3.7.tar.bz2
cd circular_buffer
su (give your root password)
cp -R circular_buffer* /usr/include/boost
[ctrl-D] (to return to user mode)

Amnon82
9th January 2007, 13:36
I'll try to install Gentoo 2006.1 today. Hope I get into it with the ebuild thing ;)

Sharktooth
15th January 2007, 03:50
Amnon82, try Sabayon linux. It's based on gentoo but it's MUCH easier to install and comes as a Live CD/DVD...

Amnon82
15th January 2007, 21:28
Will try it as soon as I get 6000 DSL so the download won't take so long.

danpos
22nd January 2007, 22:31
Amnon82, try Sabayon linux. It's based on gentoo but it's MUCH easier to install and comes as a Live CD/DVD...

Great tip, Sharktoot. :) I got both DVD and CD (mini-edition) and both work great (the mini-edition was installed in my daughter's machine and it's working great there - AMD Duron 1.3 GHz with 640 MB of RAM).

Regards,

alec_robertson
23rd January 2007, 01:11
Any chance of fixing the gcc-4.1 compilation error? It worked fine using gcc-4.0 until that package disappeared from debian!

d'Oursse
24th January 2007, 10:19
right now, no. The block class will be rewritten later.
can't you downgrade a package ?

alec_robertson
24th January 2007, 16:58
There are alternative apt sources (deb http://www.gallet.info.free.fr/debian/ sarge contrib main non-free) which work fine but as far as I can tell, gcc-4.0 has disappeared from all debian versions.

Is there a list of filters/commands that work with v3? I'd like to give it a spin beyond just opening a movie with GstreamerSource. Also which formats (at the moment I've only been able to open an avi/h264/mp3?)

d'Oursse
24th January 2007, 20:39
sorry, no :/ we are working on the new parser, but we don't have much free time
about the formats, all those that gstreamer can open :
containers: avi, mkv, ogm/ogg, mov, mp4, real and some wmv for the video, mp3, ogg, some wma and real,.. for the audio
codecs : everything that is supported by ffmpeg and those from the libs temselves (xvid, theora, etc...)

alec_robertson
25th January 2007, 23:36
OK, so I installed all the possible gstreamer plugins available for debian + marrillat but I can't load my quicktime/dv/twos video from dvgrab. Something about unsupported colorspace (YUY2). I've tested with two other gstreamer applications (remuxer.py and pitivi) and they can read these movies fine.

Any ideas? Here's the output:
accept /home/alecr/dvd/avs/trailer.avs
** Message: Pipeline Create
** Message: Pipeline Create
** Message: new pad video/x-raw-yuv, format=(fourcc)YUY2, width=(int)720, framerate=(fraction)[ 1/1, 60/1 ]; video/x-raw-rgb, bpp=(int)32, depth=(int)24, endianness=(int)4321, red_mask=(int)65280, green_mask=(int)16711680, blue_mask=(int)-16777216, width=(int)720, framerate=(fraction)[ 1/1, 60/1 ]; video/x-raw-rgb, bpp=(int)24, depth=(int)24, endianness=(int)4321, red_mask=(int)16711680, green_mask=(int)65280, blue_mask=(int)255, width=(int)720, framerate=(fraction)[ 1/1, 60/1 ]
** Message: new pad audio/x-raw-int, width=(int)16, depth=(int)16, endianness=(int)4321, signed=(boolean)true, rate=(int)48000, channels=(int)2
** Message: new pad video/x-raw-yuv, format=(fourcc)YUY2, width=(int)720, framerate=(fraction)[ 1/1, 60/1 ]; video/x-raw-rgb, bpp=(int)32, depth=(int)24, endianness=(int)4321, red_mask=(int)65280, green_mask=(int)16711680, blue_mask=(int)-16777216, width=(int)720, framerate=(fraction)[ 1/1, 60/1 ]; video/x-raw-rgb, bpp=(int)24, depth=(int)24, endianness=(int)4321, red_mask=(int)16711680, green_mask=(int)65280, blue_mask=(int)255, width=(int)720, framerate=(fraction)[ 1/1, 60/1 ]
** Message: new pad audio/x-raw-int, width=(int)16, depth=(int)16, endianness=(int)4321, signed=(boolean)true, rate=(int)48000, channels=(int)2
** Message: size : 720x480
** Message: frame count : 214
** Message: fps : 30000/1001
** Message: colorspace : YUY2
** Message: sample count : 342744
** Message: sample rate : 48000
** Message: channels : 2
frame count !! : 214
terminate called after throwing an instance of 'avs::exception::colorspace::Unsupported'
what(): N3avs9exception10colorspace11UnsupportedE
Aborted

The avs file contains: GstreamerSource("ut.mov",0,0). ut.mov is here: http://web.mit.edu/alecr/www/cwf/ut.mov

Inventive Software
26th January 2007, 12:17
You're missing a YUY2 codec with GStreamer then.

alec_robertson
26th January 2007, 15:15
But it plays fine in two other gstreamer based applications: pitivi and remuxer.py from the gstreamer cvs...

d'Oursse
27th January 2007, 11:53
it's only because I need to display the video in the gui. That is I need to convert an frame from the colorspace YUY2 to the colorspace RGB32
there aren't such converter in avs3 yet
damn, my todo is growing too much :/
I'll try to add one tomorrow

d'Oursse
29th January 2007, 14:02
I've written a small conversion function in C++ (no asm). It's not yet in the cvs. Also, even if the colorspace is not supported, there is now a beautiful dialog that explains what is wrong. I've not committed it yet as i'm doing a lot more tests.

I'll edit that post when everything will be in cvs (in 48 hours, I think)

edit: it was faster that I thought. I've added the YUY2->RGB32 colorspace conversion. I can see your video, now

renrutal
2nd February 2007, 16:56
Hello,

just a bit ago I was trying to build it through portage, but this came up: http://pastebin.com/873659

Actually I only came here to ask what was the last CVS revision that had no compilation errors, so I could pull that revision instead.

Thank you.

d'Oursse
2nd February 2007, 17:45
renrutal: could you please use rafb.net/paste instead of pastebin.com ?

edit: ok, pastebin was not so down, finally :) The problem is that you're trying to compile avs3 with gcc 4.1.1 or later. There'sa bug that is shown only with those compilers. Try to use an older gcc.

alec_robertson
2nd February 2007, 21:41
I'm also getting compilation errors on the latest cvs (feb-2):
../../src/bin/private.h:15: error: storage class specified for parameter ‘Avs3_Data’
../../src/bin/private.h:36: error: syntax error before ‘*’ token

...the rest is here...http://rafb.net/p/aAZwON85.html

My system: debian unstable, gcc/g++-4.0, stlport5.1, boost1.33.1, gstreamer0.10.10, x264-r622...

d'Oursse
2nd February 2007, 22:33
i would need more error messages (those before the ones you posted)

alec_robertson
2nd February 2007, 23:48
OK, my build commands are: http://rafb.net/p/xiryN379.html
Configure output is: http://rafb.net/p/qAenU381.html
Debian depends: http://rafb.net/p/eFolGN55.html
Build output: http://rafb.net/p/XhYDBa54.html

d'Oursse
2nd February 2007, 23:52
can you also paste the file platform.inc which is in build/linux, please ?

alec_robertson
3rd February 2007, 00:05
platform.inc: http://rafb.net/p/LgL7Hw34.html

d'Oursse
3rd February 2007, 00:38
i don't really know what happens. Try to put all the typedef instructions in src/bin/private.h and src/bin/provate_x264.h after the dfinition of the structs, instead of before.

alec_robertson
3rd February 2007, 05:09
Nah, no difference...

It seems to have a problem with the typedefs, as when I remove them and use "struct Avs3_Data" (and so on for a few structs and void*) it no longer barfs, but then I run into problems later on in encode.c...

d'Oursse
3rd February 2007, 08:04
../../src/bin/private.h:15: error: storage class specified for parameter ‘Avs3_Data’

can you paste private.h, please ? and also mark the line 15, please

alec_robertson
3rd February 2007, 20:14
original private.h: http://rafb.net/p/GlpIza25.html
removing the typedef avoids the compiler error: http://rafb.net/p/K1Ul2M94.html

d'Oursse
3rd February 2007, 20:29
I can't understand why the code fails for you. The code *is* correct.

Did you change compiler version during 2 builds of avs3 ? To be sure, make clean, then make

alec_robertson
3rd February 2007, 23:39
Nope, same gcc as last time. I even remove the entire directory and re-checkout from cvs between compiles... Same problem with gcc-3.4...

d'Oursse
4th February 2007, 22:45
i have no more ideas. I'll look deeper in the code for possible errors. It's difficult to fix a bug that I don't have :(

Amnon82
7th February 2007, 20:34
Sers, I'll try tomorrow to compile AVS for Paldo 1.9. Thats what I should have:


STLport 5.0.2
Boost 1.33.1
bjam 3.1.12 (utilitaire similaire a make)
Freetype 2.2.1
Fontconfig 2.3.2
liboil 0.3.10
Gstreamer 0.10.10
Gst-Plugins-Base 0.10.10
Gst-Plugins-Good 0.10.4
Gst-Plugins-Bad 0.10.3
Gst-Plugins-Ugly 0.10.4
Gst-FFmpeg 0.10.1
Nasm 0.98.39


And what we have in our distro:


GCC 4.1-20061222-1
boost 1.33.1-2
freetype 2.3.1-1
fontconfig 2.4.2-1
liboil 0.3-0.3.9-1
Gstreamer 0.10.11
Gst-Plugins-Base 0.10.11
Gst-Plugins-Good 0.10.5
Gst-Plugins-Bad 0.10.4
Gst-Plugins-Ugly 0.10.5
Gst-FFmpeg 0.10.2
nasm 0.98.39-1


Needs to be compiled:


STLport
bjam


Are there any bugs with GCC 4.1? LibOil needs to be updated, right?

d'Oursse
7th February 2007, 20:44
bjam is used to compile boost. If boost is installed, you don't need it.
liboil is used to get gstreamer compiled, so no need to update it

I fear that gcc 4.1 will have problems with block :/ Try and tell me.

I have to update the doc. The versions of gstreamer libs, freetype and fontconfig are not up to date :)

Amnon82
7th February 2007, 20:47
STLport is still needed, right?

So I did a package:

[amnon@amnonsstation:~]$ upkg-show stlport
stlport-x86-glibc-2.5-gcc-4.1-1-5.0.3-1
----
Package: stlport
Version: 5.0.3-1
Branch: testing
Installed-Size: 5118 KB
Build-Duration: 1 min
Build-Date: 2007-02-07 21:33:49 +0000
Build-Host: amnonsstation.paldo.org
- /usr
- /usr/include/stlport
- /usr/include/stlport/algorithm
- /usr/include/stlport/assert.h
- /usr/include/stlport/bitset
- /usr/include/stlport/cassert
- /usr/include/stlport/cctype
- /usr/include/stlport/cerrno
- /usr/include/stlport/cfloat
- /usr/include/stlport/ciso646
- /usr/include/stlport/climits
- /usr/include/stlport/clocale
- /usr/include/stlport/cmath
- /usr/include/stlport/complex
- /usr/include/stlport/config
- /usr/include/stlport/config/_epilog.h
- /usr/include/stlport/config/_msvc_warnings_off.h
- /usr/include/stlport/config/new_compiler
- /usr/include/stlport/config/new_compiler/configure
- /usr/include/stlport/config/new_compiler/configure.in
- /usr/include/stlport/config/new_compiler/README
- /usr/include/stlport/config/new_compiler/stlconf.h.in
- /usr/include/stlport/config/new_compiler/unconfigure
- /usr/include/stlport/config/_prolog.h
- /usr/include/stlport/config/stl_apcc.h
- /usr/include/stlport/config/stl_apple.h
- /usr/include/stlport/config/stl_as400.h
- /usr/include/stlport/config/stl_bc.h
- /usr/include/stlport/config/stl_como.h
- /usr/include/stlport/config/stlcomp.h
- /usr/include/stlport/config/stl_confix.h
- /usr/include/stlport/config/stl_cray.h
- /usr/include/stlport/config/stl_dec.h
- /usr/include/stlport/config/stl_dec_vms.h
- /usr/include/stlport/config/stl_dm.h
- /usr/include/stlport/config/stl_evc.h
- /usr/include/stlport/config/stl_fujitsu.h
- /usr/include/stlport/config/stl_gcc.h
- /usr/include/stlport/config/stl_hpacc.h
- /usr/include/stlport/config/stl_ibm.h
- /usr/include/stlport/config/stl_icc.h
- /usr/include/stlport/config/stl_intel.h
- /usr/include/stlport/config/stl_kai.h
- /usr/include/stlport/config/stl_mlc.h
- /usr/include/stlport/config/stl_msvc.h
- /usr/include/stlport/config/stl_mwerks.h
- /usr/include/stlport/config/stl_mycomp.h
- /usr/include/stlport/config/stl_sco.h
- /usr/include/stlport/config/stl_sgi.h
- /usr/include/stlport/config/stl_solaris.h
- /usr/include/stlport/config/stl_sunpro.h
- /usr/include/stlport/config/stl_symantec.h
- /usr/include/stlport/config/stl_watcom.h
- /usr/include/stlport/config/stl_wince.h
- /usr/include/stlport/csetjmp
- /usr/include/stlport/csignal
- /usr/include/stlport/cstdarg
- /usr/include/stlport/cstddef
- /usr/include/stlport/cstdio
- /usr/include/stlport/cstdlib
- /usr/include/stlport/cstring
- /usr/include/stlport/ctime
- /usr/include/stlport/ctype.h
- /usr/include/stlport/cwchar
- /usr/include/stlport/cwctype
- /usr/include/stlport/deque
- /usr/include/stlport/errno.h
- /usr/include/stlport/exception
- /usr/include/stlport/exception.h
- /usr/include/stlport/float.h
- /usr/include/stlport/fstream
- /usr/include/stlport/fstream.h
- /usr/include/stlport/functional
- /usr/include/stlport/hash_map
- /usr/include/stlport/hash_set
- /usr/include/stlport/iomanip
- /usr/include/stlport/iomanip.h
- /usr/include/stlport/ios
- /usr/include/stlport/iosfwd
- /usr/include/stlport/ios.h
- /usr/include/stlport/iostream
- /usr/include/stlport/iostream.h
- /usr/include/stlport/iso646.h
- /usr/include/stlport/istream
- /usr/include/stlport/istream.h
- /usr/include/stlport/iterator
- /usr/include/stlport/limits
- /usr/include/stlport/limits.h
- /usr/include/stlport/list
- /usr/include/stlport/locale
- /usr/include/stlport/locale.h
- /usr/include/stlport/map
- /usr/include/stlport/math.h
- /usr/include/stlport/mem.h
- /usr/include/stlport/memory
- /usr/include/stlport/new
- /usr/include/stlport/new.h
- /usr/include/stlport/numeric
- /usr/include/stlport/ostream
- /usr/include/stlport/ostream.h
- /usr/include/stlport/pthread_alloc
- /usr/include/stlport/pthread.h
- /usr/include/stlport/queue
- /usr/include/stlport/rlocks.h
- /usr/include/stlport/rope
- /usr/include/stlport/set
- /usr/include/stlport/setjmp.h
- /usr/include/stlport/signal.h
- /usr/include/stlport/slist
- /usr/include/stlport/sstream
- /usr/include/stlport/stack
- /usr/include/stlport/stdarg.h
- /usr/include/stlport/stddef.h
- /usr/include/stlport/stdexcept
- /usr/include/stlport/stdio.h
- /usr/include/stlport/stdiostream.h
- /usr/include/stlport/stdlib.h
- /usr/include/stlport/stl
- /usr/include/stlport/stl/_abbrevs.h
- /usr/include/stlport/stl/_algobase.c
- /usr/include/stlport/stl/_algobase.h
- /usr/include/stlport/stl/_algo.c
- /usr/include/stlport/stl/_algo.h
- /usr/include/stlport/stl/_alloc.c
- /usr/include/stlport/stl/_alloc.h
- /usr/include/stlport/stl/_alloc_old.h
- /usr/include/stlport/stl/_auto_ptr.h
- /usr/include/stlport/stl/_bitset.c
- /usr/include/stlport/stl/_bitset.h
- /usr/include/stlport/stl/boost_type_traits.h
- /usr/include/stlport/stl/_bvector.h
- /usr/include/stlport/stl/char_traits.h
- /usr/include/stlport/stl/_check_config.h
- /usr/include/stlport/stl/c_locale.h
- /usr/include/stlport/stl/_cmath.h
- /usr/include/stlport/stl/_codecvt.h
- /usr/include/stlport/stl/_collate.h
- /usr/include/stlport/stl/_complex.c
- /usr/include/stlport/stl/_complex.h
- /usr/include/stlport/stl/concept_checks.h
- /usr/include/stlport/stl/_config_compat.h
- /usr/include/stlport/stl/_config_compat_post.h
- /usr/include/stlport/stl/_config.h
- /usr/include/stlport/stl/_construct.h
- /usr/include/stlport/stl/_ctraits_fns.h
- /usr/include/stlport/stl/_ctype.h
- /usr/include/stlport/stl/_cwchar.h
- /usr/include/stlport/stl/_cwctype.h
- /usr/include/stlport/stl/debug
- /usr/include/stlport/stl/debug/_debug.c
- /usr/include/stlport/stl/debug/_debug.h
- /usr/include/stlport/stl/debug/_deque.h
- /usr/include/stlport/stl/debug/_hashtable.h
- /usr/include/stlport/stl/debug/_iterator.h
- /usr/include/stlport/stl/debug/_list.h
- /usr/include/stlport/stl/debug/_relops_cont.h
- /usr/include/stlport/stl/debug/_relops_hash_cont.h
- /usr/include/stlport/stl/debug/_slist.h
- /usr/include/stlport/stl/debug/_string.h
- /usr/include/stlport/stl/debug/_string_workaround.h
- /usr/include/stlport/stl/debug/_tree.h
- /usr/include/stlport/stl/debug/_vector.h
- /usr/include/stlport/stl/_deque.c
- /usr/include/stlport/stl/_deque.h
- /usr/include/stlport/stl/_epilog.h
- /usr/include/stlport/stl/_exception.h
- /usr/include/stlport/stl/_fstream.c
- /usr/include/stlport/stl/_fstream.h
- /usr/include/stlport/stl/_function_adaptors.h
- /usr/include/stlport/stl/_function_base.h
- /usr/include/stlport/stl/_function.h
- /usr/include/stlport/stl/_hash_fun.h
- /usr/include/stlport/stl/_hash_map.h
- /usr/include/stlport/stl/_hash_set.h
- /usr/include/stlport/stl/_hashtable.c
- /usr/include/stlport/stl/_hashtable.h
- /usr/include/stlport/stl/_heap.c
- /usr/include/stlport/stl/_heap.h
- /usr/include/stlport/stl/_ios_base.h
- /usr/include/stlport/stl/_ios.c
- /usr/include/stlport/stl/_ioserr.h
- /usr/include/stlport/stl/_iosfwd.h
- /usr/include/stlport/stl/_ios.h
- /usr/include/stlport/stl/_iostream_string.h
- /usr/include/stlport/stl/_istreambuf_iterator.h
- /usr/include/stlport/stl/_istream.c
- /usr/include/stlport/stl/_istream.h
- /usr/include/stlport/stl/_iterator_base.h
- /usr/include/stlport/stl/_iterator.h
- /usr/include/stlport/stl/_iterator_old.h
- /usr/include/stlport/stl/_limits.c
- /usr/include/stlport/stl/_limits.h
- /usr/include/stlport/stl/_list.c
- /usr/include/stlport/stl/_list.h
- /usr/include/stlport/stl/_locale.h
- /usr/include/stlport/stl/_map.h
- /usr/include/stlport/stl/_messages_facets.h
- /usr/include/stlport/stl/_monetary.c
- /usr/include/stlport/stl/_monetary.h
- /usr/include/stlport/stl/_move_construct_fwk.h
- /usr/include/stlport/stl/msl_string.h
- /usr/include/stlport/stl/_new.h
- /usr/include/stlport/stl/_null_stream.h
- /usr/include/stlport/stl/_numeric.c
- /usr/include/stlport/stl/_numeric.h
- /usr/include/stlport/stl/_num_get.c
- /usr/include/stlport/stl/_num_get.h
- /usr/include/stlport/stl/_numpunct.h
- /usr/include/stlport/stl/_num_put.c
- /usr/include/stlport/stl/_num_put.h
- /usr/include/stlport/stl/_ostreambuf_iterator.h
- /usr/include/stlport/stl/_ostream.c
- /usr/include/stlport/stl/_ostream.h
- /usr/include/stlport/stl/_pair.h
- /usr/include/stlport/stl/pointers
- /usr/include/stlport/stl/pointers/_deque.h
- /usr/include/stlport/stl/pointers/_list.h
- /usr/include/stlport/stl/pointers/_slist.h
- /usr/include/stlport/stl/pointers/_vector.h
- /usr/include/stlport/stl/pointers/_void_ptr_traits.h
- /usr/include/stlport/stl/_prolog.h
- /usr/include/stlport/stl/_pthread_alloc.c
- /usr/include/stlport/stl/_pthread_alloc.h
- /usr/include/stlport/stl/_ptrs_specialize.h
- /usr/include/stlport/stl/_queue.h
- /usr/include/stlport/stl/_range_errors.h
- /usr/include/stlport/stl/_raw_storage_iter.h
- /usr/include/stlport/stl/_relops_cont.h
- /usr/include/stlport/stl/_relops_hash_cont.h
- /usr/include/stlport/stl/_rope.c
- /usr/include/stlport/stl/_rope.h
- /usr/include/stlport/stl/_set.h
- /usr/include/stlport/stl/_site_config.h
- /usr/include/stlport/stl/_slist_base.c
- /usr/include/stlport/stl/_slist_base.h
- /usr/include/stlport/stl/_slist.c
- /usr/include/stlport/stl/_slist.h
- /usr/include/stlport/stl/_sparc_atomic.h
- /usr/include/stlport/stl/_sstream.c
- /usr/include/stlport/stl/_sstream.h
- /usr/include/stlport/stl/_stack.h
- /usr/include/stlport/stl/_stlport_version.h
- /usr/include/stlport/stl/_streambuf.c
- /usr/include/stlport/stl/_streambuf.h
- /usr/include/stlport/stl/_stream_iterator.h
- /usr/include/stlport/stl/_string_base.h
- /usr/include/stlport/stl/_string.c
- /usr/include/stlport/stl/_string_fwd.h
- /usr/include/stlport/stl/_string.h
- /usr/include/stlport/stl/_string_hash.h
- /usr/include/stlport/stl/_string_io.c
- /usr/include/stlport/stl/_string_io.h
- /usr/include/stlport/stl/_string_operators.h
- /usr/include/stlport/stl/_string_sum.h
- /usr/include/stlport/stl/_string_sum_methods.h
- /usr/include/stlport/stl/_string_workaround.h
- /usr/include/stlport/stl/_strstream.h
- /usr/include/stlport/stl/_tempbuf.c
- /usr/include/stlport/stl/_tempbuf.h
- /usr/include/stlport/stl/_threads.c
- /usr/include/stlport/stl/_threads.h
- /usr/include/stlport/stl/_time_facets.c
- /usr/include/stlport/stl/_time_facets.h
- /usr/include/stlport/stl/_tree.c
- /usr/include/stlport/stl/_tree.h
- /usr/include/stlport/stl/type_manips.h
- /usr/include/stlport/stl/type_traits.h
- /usr/include/stlport/stl/_uninitialized.h
- /usr/include/stlport/stl/_unordered_map.h
- /usr/include/stlport/stl/_unordered_set.h
- /usr/include/stlport/stl_user_config.h
- /usr/include/stlport/stl/_valarray.c
- /usr/include/stlport/stl/_valarray.h
- /usr/include/stlport/stl/_vector.c
- /usr/include/stlport/stl/_vector.h
- /usr/include/stlport/stl/_windows.h
- /usr/include/stlport/stl/wrappers
- /usr/include/stlport/stl/wrappers/_deque.h
- /usr/include/stlport/stl/wrappers/_hash_map.h
- /usr/include/stlport/stl/wrappers/_hash_set.h
- /usr/include/stlport/stl/wrappers/_list.h
- /usr/include/stlport/stl/wrappers/_map.h
- /usr/include/stlport/stl/wrappers/_set.h
- /usr/include/stlport/stl/wrappers/_slist.h
- /usr/include/stlport/stl/wrappers/_vector.h
- /usr/include/stlport/streambuf
- /usr/include/stlport/streambuf.h
- /usr/include/stlport/string
- /usr/include/stlport/string.h
- /usr/include/stlport/strstream
- /usr/include/stlport/strstream.h
- /usr/include/stlport/time.h
- /usr/include/stlport/typeinfo
- /usr/include/stlport/typeinfo.h
- /usr/include/stlport/unordered_map
- /usr/include/stlport/unordered_set
- /usr/include/stlport/using
- /usr/include/stlport/using/cstring
- /usr/include/stlport/using/export
- /usr/include/stlport/using/fstream
- /usr/include/stlport/using/h
- /usr/include/stlport/using/h/fstream.h
- /usr/include/stlport/using/h/iomanip.h
- /usr/include/stlport/using/h/iostream.h
- /usr/include/stlport/using/h/ostream.h
- /usr/include/stlport/using/h/streambuf.h
- /usr/include/stlport/using/h/strstream.h
- /usr/include/stlport/using/iomanip
- /usr/include/stlport/using/ios
- /usr/include/stlport/using/iosfwd
- /usr/include/stlport/using/iostream
- /usr/include/stlport/using/istream
- /usr/include/stlport/using/locale
- /usr/include/stlport/using/ostream
- /usr/include/stlport/using/sstream
- /usr/include/stlport/using/streambuf
- /usr/include/stlport/using/strstream
- /usr/include/stlport/utility
- /usr/include/stlport/valarray
- /usr/include/stlport/vector
- /usr/include/stlport/wchar.h
- /usr/include/stlport/wctype.h
- /usr/lib/libstlportg.so
- /usr/lib/libstlportg.so.5
- /usr/lib/libstlportg.so.5.0
- /usr/lib/libstlportg.so.5.0.3
- /usr/lib/libstlport.so
- /usr/lib/libstlport.so.5
- /usr/lib/libstlport.so.5.0
- /usr/lib/libstlport.so.5.0.3
- /usr/lib/libstlportstlg.so
- /usr/lib/libstlportstlg.so.5
- /usr/lib/libstlportstlg.so.5.0
- /usr/lib/libstlportstlg.so.5.0.3
- /usr/src

Amnon82
7th February 2007, 21:57
In your guide you wrote:

cd
cd avs3_tmp
tar jxvf boost_1_33_1.tar.bz2
tar zxvf boost-jam-3.1.12-1-linuxx86.tgz
cd boost_1_33_1
su (give your root password)
../boost-jam-3.1.12-1-linuxx86/bjam "-sTOOLS=gcc" -sSTLPORT_PATH="/usr/local/include/stlport/" -sSTLPORT_VERSION="5.0.2" --prefix=/usr/local --with-thread install
[ctrl-D] (to return to user mode)

We compiled boost this way (http://www.paldo.org/paldo/specs/boost.xml). This (http://www.paldo.org/paldo/sources/boost/boost_1_33_1.tar.bz2) is the used tarball.

So I have to recompile it with STLport?
Take a look on the boost files (http://www.paldo.org/index-section-packages-page-main-filelist-1-releaseid-71207-binaryid-143474-pagenr-1.html) and tell me what I have to do.

cd avisynth/build
tar jxvf circular_buffer_v3.7.tar.bz2
cd circular_buffer
su (give your root password)
cp -R circular_buffer* /usr/local/include/boost-1_33_1/boost
[ctrl-D] (to return to user mode)

So it will be cp -R circular_buffer* /usr/include/boost, right?

Till now we are using boost only for:


bmpx: beep media player -stable: bmpx-0.34.9-1
mockpp: Mock objects for C++ - stable: mockpp-1.13.0-1

d'Oursse
7th February 2007, 23:27
in boost.xml, why do you remove the static libs ? I need at least one (the thread one) for the compilation of avs3.

Yes, install first STLPORT, then compile boost using STLport. Compile boost with the command I give in the doc. I need at least the thread library (hence the --with-thread parameter. Remove --with thread to compile all the libs). Later, I'll need the test library of boost, for unit tests (but it's more a developper tool than something else).


So it will be cp -R circular_buffer* /usr/include/boost, right?

yes, it's in that directory.

Why don't you keep the boost_1_33_1 dir ? It allows the installation of several boost versions

Amnon82
7th February 2007, 23:59
I didn't do the boost-package. So I'll add a boost-avs package to paldo and compile it as written in your guide.

Here are the files:

boost_1_33_1-2 (http://home.arcor.de/amnonssecondpaldorepo/logs/boost.files) - boost-avs-1.33.1-1 (http://home.arcor.de/amnonssecondpaldorepo/logs/boost-avs.files)

Amnon82
8th February 2007, 01:40
Got the block:

d variable 'synchronizer'
C: core/block/ownedholder.cpp
C: core/block/block.cpp
../../src/core/block/block.cpp:36: error: specialization of 'avs::block_<align>::block_(int, bool) [with int align = 16]' after instantiation
../../src/core/block/block.cpp:36: error: invalid function declaration
../../src/core/block/block.cpp:41: error: specialization of 'avs::owned_block<align>::owned_block(const avs::PEnvironment&, int, bool) [with int align = 16]' after instantiation
../../src/core/block/block.cpp:41: error: invalid function declaration
make: *** [core/block/block.o] Error 1
*** Error: make
*** ERROR: avisynth-x86-glibc-2.5-gcc-4.1-1-3.0-CVS-20070207-0

will be there a fix soon?

nfm
8th February 2007, 02:54
I'm waiting since November for block.cpp to be rewritten :(

d'Oursse
8th February 2007, 09:56
Nope, same gcc as last time. I even remove the entire directory and re-checkout from cvs between compiles... Same problem with gcc-3.4...

missing ; at the end of a function declaration. My fault.

amnon82: I'll try to get a newer version than gcc 4.1.1. I don't have the problem with it (the g++ parser fixed the bug in a more recent version). I'll lok at it this week end

Amnon82
8th February 2007, 14:05
With 4.1-20070205-1 I got the same error:

C: core/block/block.cpp
../../src/core/block/block.cpp:36: error: specialization of 'avs::block_<align>::block_(int, bool) [with int align = 16]' after instantiation
../../src/core/block/block.cpp:36: error: invalid function declaration
../../src/core/block/block.cpp:41: error: specialization of 'avs::owned_block<align>::owned_block(const avs::PEnvironment&, int, bool) [with int align = 16]' after instantiation
../../src/core/block/block.cpp:41: error: invalid function declaration
make: *** [core/block/block.o] Error 1
*** Error: make
*** ERROR: avisynth-x86-glibc-2.5-gcc-4.1-1-3.0-CVS-20070208-0

I'll try gcc 4.2 now.

------------------------------------------------------------------------
Avisynth 3.0
------------------------------------------------------------------------

OS..................: linux-gnu

Visibility feature..: no (disabled for now)
Core debug mode.....: no
GNU Profile mode....: no
ASM support.........: yes

Gui program.........: no

Documentation.......: yes

Install path........: /usr
binaries..........: ${exec_prefix}/bin
libraries.........: ${exec_prefix}/lib
headers...........: ${prefix}/include/avisynth-3.0
documentation.....: ${datarootdir}/doc/avisynth-3.0
gst-plugins.......: /usr/lib/gstreamer-0.10

Compilation.........: make
Installation........: make install


btw. how to make the gui?

Amnon82
8th February 2007, 15:12
checking for pthread.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for dlopen in -ldl... yes
checking for dlclose in -ldl... yes
checking for dlsym in -ldl... yes
checking for STLport header files in /usr/include/stlport... no
configure: WARNING: STLport header files not in /usr/include/stlport
checking for STLport header files in /usr/local/include/stlport... no
configure: WARNING: STLport header files not in /usr/local/include/stlport
configure: error: "STLport is needed !"
*** Error: ./configure --prefix=/usr --infodir=/usr/share/info --mandir=/usr/share/man --sysconfdir=/etc
*** ERROR: avisynth-x86-glibc-2.5-gcc-4.1-1-3.0-CVS-20070208-0

Seems boost is not compiled right.

I highered the version of stlport- and boost-avs-package but got this error:

[CHECK] make -f gcc.mak
c++ -pthread -fexceptions -fident -fPIC -O2 -fuse-cxa-atexit -D_STLP_REAL_LOCALE_IMPLEMENTED -D_GNU_SOURCE -I../../stlport -c -o obj/gcc/shared/dll_main.o ../../src/dll_main.cpp
c++ -pthread -fexceptions -fident -fPIC -O2 -fuse-cxa-atexit -D_STLP_REAL_LOCALE_IMPLEMENTED -D_GNU_SOURCE -I../../stlport -c -o obj/gcc/shared/fstream.o ../../src/fstream.cpp
c++ -pthread -fexceptions -fident -fPIC -O2 -fuse-cxa-atexit -D_STLP_REAL_LOCALE_IMPLEMENTED -D_GNU_SOURCE -I../../stlport -c -o obj/gcc/shared/strstream.o ../../src/strstream.cpp
c++ -pthread -fexceptions -fident -fPIC -O2 -fuse-cxa-atexit -D_STLP_REAL_LOCALE_IMPLEMENTED -D_GNU_SOURCE -I../../stlport -c -o obj/gcc/shared/sstream.o ../../src/sstream.cpp
c++ -pthread -fexceptions -fident -fPIC -O2 -fuse-cxa-atexit -D_STLP_REAL_LOCALE_IMPLEMENTED -D_GNU_SOURCE -I../../stlport -c -o obj/gcc/shared/ios.o ../../src/ios.cpp
c++ -pthread -fexceptions -fident -fPIC -O2 -fuse-cxa-atexit -D_STLP_REAL_LOCALE_IMPLEMENTED -D_GNU_SOURCE -I../../stlport -c -o obj/gcc/shared/stdio_streambuf.o ../../src/stdio_streambuf.cpp
c++ -pthread -fexceptions -fident -fPIC -O2 -fuse-cxa-atexit -D_STLP_REAL_LOCALE_IMPLEMENTED -D_GNU_SOURCE -I../../stlport -c -o obj/gcc/shared/istream.o ../../src/istream.cpp
c++ -pthread -fexceptions -fident -fPIC -O2 -fuse-cxa-atexit -D_STLP_REAL_LOCALE_IMPLEMENTED -D_GNU_SOURCE -I../../stlport -c -o obj/gcc/shared/ostream.o ../../src/ostream.cpp
c++ -pthread -fexceptions -fident -fPIC -O2 -fuse-cxa-atexit -D_STLP_REAL_LOCALE_IMPLEMENTED -D_GNU_SOURCE -I../../stlport -c -o obj/gcc/shared/iostream.o ../../src/iostream.cpp
c++ -pthread -fexceptions -fident -fPIC -O2 -fuse-cxa-atexit -D_STLP_REAL_LOCALE_IMPLEMENTED -D_GNU_SOURCE -I../../stlport -c -o obj/gcc/shared/codecvt.o ../../src/codecvt.cpp
c++ -pthread -fexceptions -fident -fPIC -O2 -fuse-cxa-atexit -D_STLP_REAL_LOCALE_IMPLEMENTED -D_GNU_SOURCE -I../../stlport -c -o obj/gcc/shared/collate.o ../../src/collate.cpp
c++ -pthread -fexceptions -fident -fPIC -O2 -fuse-cxa-atexit -D_STLP_REAL_LOCALE_IMPLEMENTED -D_GNU_SOURCE -I../../stlport -c -o obj/gcc/shared/ctype.o ../../src/ctype.cpp
c++ -pthread -fexceptions -fident -fPIC -O2 -fuse-cxa-atexit -D_STLP_REAL_LOCALE_IMPLEMENTED -D_GNU_SOURCE -I../../stlport -c -o obj/gcc/shared/monetary.o ../../src/monetary.cpp
c++ -pthread -fexceptions -fident -fPIC -O2 -fuse-cxa-atexit -D_STLP_REAL_LOCALE_IMPLEMENTED -D_GNU_SOURCE -I../../stlport -c -o obj/gcc/shared/num_get.o ../../src/num_get.cpp
c++ -pthread -fexceptions -fident -fPIC -O2 -fuse-cxa-atexit -D_STLP_REAL_LOCALE_IMPLEMENTED -D_GNU_SOURCE -I../../stlport -c -o obj/gcc/shared/num_put.o ../../src/num_put.cpp
c++ -pthread -fexceptions -fident -fPIC -O2 -fuse-cxa-atexit -D_STLP_REAL_LOCALE_IMPLEMENTED -D_GNU_SOURCE -I../../stlport -c -o obj/gcc/shared/num_get_float.o ../../src/num_get_float.cpp
c++ -pthread -fexceptions -fident -fPIC -O2 -fuse-cxa-atexit -D_STLP_REAL_LOCALE_IMPLEMENTED -D_GNU_SOURCE -I../../stlport -c -o obj/gcc/shared/num_put_float.o ../../src/num_put_float.cpp
In file included from /usr/lib/gcc/i686-pc-linux-gnu/4.2.0/../../../../include/c++/4.2.0/../4.2.0/cmath:52,
from ../../stlport/cmath:30,
from ../../src/num_put_float.cpp:84:
/usr/lib/gcc/i686-pc-linux-gnu/4.2.0/../../../../include/c++/4.2.0/ext/type_traits.h:184: error: 'streamsize' in namespace 'std' does not name a type
/usr/lib/gcc/i686-pc-linux-gnu/4.2.0/../../../../include/c++/4.2.0/ext/type_traits.h:189: error: expected initializer before '__numeric_traits_floating'
make: *** [obj/gcc/shared/num_put_float.o] Error 1
*** Error: make -f gcc.mak
*** ERROR: stlport-x86-glibc-2.5-gcc-4.1-1-5.0.3-2

The spec-files:

avisynth.xml (http://home.arcor.de/amnonssecondpaldorepo/notworking/specs/avisynth.xml)
boost-avs.xml (http://home.arcor.de/amnonssecondpaldorepo/notworking/specs/boost-avs.xml)
stlport.xml (http://home.arcor.de/amnonssecondpaldorepo/notworking/specs/stlport.xml)
gcc.xml (http://home.arcor.de/amnonssecondpaldorepo/notworking/specs/gcc.xml)

Let's try GCC 4.3 (I did a backup of my system with GCC 4.1.1)
GCC 4.3 won't compile so I downgrade to 4.0-20070128 and try it with this one.

Amnon82
8th February 2007, 16:37
I downgraded to GCC 4.0 and compiled it. Now I must find a way to restore the GCC 4.1 after it is done.

avisynth-x86-glibc-2.5-gcc-4.1-1-3.0-CVS-20070208-0
----
Package: avisynth
Version: 3.0-CVS-20070208-0
Branch: testing
Installed-Size: 16117 KB
Build-Duration: 5 min
Build-Date: 2007-02-08 15:11:42 +0000
Build-Host: amnonsstation.paldo.org

Amnon82
8th February 2007, 18:46
Well I found a way to downgrade GCC to Version 4.0 for installing avisynth. After all is done GCC gets restored to his last version.

I'm now testing the final packages.

d'Oursse
8th February 2007, 19:32
don't play with g++ 4.2 or 4.3. The compiler and libstdc++ are changing a lot. If there's a problem with STLport and g++ 4.2, it will be fixed only after an official release of that version of gcc.

to have the gui, you need gtk+ (>= 2.8) and x264 with the gtk interface.
There is a warning message during the configuration of avs3 that tells you what is missing

Amnon82
8th February 2007, 20:16
GTK+ 2.10.9 I have installed on paldo. x264 I compiled for AVIDemux, but without gtk interface. Will see how to do that.

Bidoche
8th February 2007, 22:14
Just committed an attempt to work around that bug.

I hope it will work.

d'Oursse
8th February 2007, 23:52
it works for me (gcc 4.1.1 snapshot 20070205)

Amnon82
9th February 2007, 00:30
You mean this one:

http://gcc-ca.internet.bs/snapshots/4.1-20070205/

I got an error, the block-error but I'll recheck it tomorrow.
Must the stlport and boost be compiled with the same gcc or not?

I rechecked:

C: core/block/ownedholder.cpp
C: core/block/block.cpp
../../src/core/block/block.cpp:36: error: specialization of 'avs::block_<align>::block_(int, bool) [with int align = 16]' after instantiation
../../src/core/block/block.cpp:36: error: invalid function declaration
../../src/core/block/block.cpp:41: error: specialization of 'avs::owned_block<align>::owned_block(const avs::PEnvironment&, int, bool) [with int align = 16]' after instantiation
../../src/core/block/block.cpp:41: error: invalid function declaration
make: *** [core/block/block.o] Error 1
*** Error: make
*** ERROR: avisynth-x86-glibc-2.5-gcc-4.1-1-3.0-CVS-20070208-3


... till now I've to do the downgrade/restore-thing.

Here are the gcc-4.1-20070205 files (http://home.arcor.de/amnonssecondpaldorepo/logs/gcc-4.1.files).

Can you tell me the exact dependencies with them it worked for you?

nfm
9th February 2007, 01:11
Bidoche & d'Oursse, thank you very much for fixing that :) I have successfully built avisynth on Ubuntu 6.10 i386 Edgy Eft running kernel 2.6.20, stlport 4.6.2, gcc-4.1 and boost_133.1. I encounter:avisynth_test: error while loading shared libraries: libboost_thread-gcc-mt-1_33_1.so.1.33.1: cannot open shared object file: No such file or directory while using avisynth but I think it's a problem with my distro, I've seen similar error whem I built and ran mpeg4iptools but I don't remember how I got around that error. I have installed all avisynth dependencies through synaptic package manager except boost, that I compiled and installed into /usr/local dir. Also, avisynth was installed into /usr/local too. If you guys know and are willing to reply, point me in the right direction :)
To build with gtk support Amnon82, you have to build x264 with --enable-gtk and --enable-shared as configure script from avisynth is telling you.

Edit: From what I can conclude now, avisynth looks into /usr/lib instead of /usr/local/lib. Copying missing files into /usr/lib seems to work now.
Edit 2: I got it to work, had to install x264 into /usr

Amnon82
9th February 2007, 01:28
@nfm: I already got it. Also the GUI thing. For the boost-error: You have to install Boost-1.33.1. Maybe you missed something.
@Bidoche & d'Oursse: On my distro it only works with an downgrade of gcc. These are the spec-files I'm using for the moment:

downgrade-gcc.xml (http://home.arcor.de/amnonssecondpaldorepo/specs/downgrade-gcc.xml)
gcc-4.0.xml (http://home.arcor.de/amnonssecondpaldorepo/specs/gcc-4.0.xml)
stlport.xml (http://home.arcor.de/amnonssecondpaldorepo/specs/stlport.xml)
boost-avs.xml (http://home.arcor.de/amnonssecondpaldorepo/specs/boost-avs.xml)
x264.xml (http://home.arcor.de/amnonssecondpaldorepo/specs/x264.xml)
avisynth.xml (http://home.arcor.de/amnonssecondpaldorepo/specs/avisynth.xml)

What can it be that the block-error apears with gcc-4.1-20070205 (http://home.arcor.de/amnonssecondpaldorepo/logs/gcc-4.1.files)?

When I use this spec:

gcc-4.0.xml (http://home.arcor.de/amnonssecondpaldorepo/notworking/specs/gcc-4.0_.xml)
I might can use ./configure --cc=gcc-4.0 --gxx=g++-4.0 for avisynth.xml but what can I use for Phyton and gcc.mak?

d'Oursse
9th February 2007, 08:24
nfm: it's not a good idea to copy those files. If boost is installed in /usr/local and not /usr, then you have 2 solutions for the .so file to be found :

1) export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/usr/local/lib"

2) or :
* edit (as root) /etc/ld.so.conf and add /usr/local/lib
* as root, run: ldconfig

also, are you sure that STLport 5.1 and boost 1.33.1 are not installed ? You talked about STLport 4.6.2 (which is not supported anymore by avs3) and boost 1.33 (clearly, it's boost 1.33.1 that is searched)

amnon82: first, check if, in src/core/block.h, at lines 113 and 114, you have the following code:

template <>
block_<block::Align>::block_(int size, bool recycle);
that is, have you ckecked out the cvs repository since Bidoche's post ?

Amnon82
9th February 2007, 12:14
No I didn't. I'll check it today when I came home. I'll restore my system again to do a clean install of all files.

Maybe it will work with CVS-20070209 and the installed GCC 4.1.

Edit: It works now with the latest CVS and GCC 4.1 also in Paldo GNU/Linux. The compile takes now 8 Min instead of 22 Min. Keep up the good work. The block-Bug is gone now. Paldo uses GCC Snapshot 4.1-20061222-1.

Amnon82
9th February 2007, 23:44
If I start avisynth_test with this .desktop-file:

[Desktop Entry]
Encoding=UTF-8
Name=AVISynth 3.0 Tester
Exec=avisynth_test
Icon=/usr/share/icons/gnome/32x32/categories/applications-multimedia.png
Terminal=true
Type=Application
Categories=Application;AudioVideo;Player;
StartupNotify=false

It closes it self without an error message.

Only when I start avisynth_test via terminal it works. Maybe you guys wanna fix this or tell me how to setup the .desktop-file.

Amnon82
17th April 2007, 23:36
A german user found a bug:

silentium:/usr/src/avisynth/src/filters/source# diff messageclip.cpp.orig messageclip.cpp
47c47
< : StaticImage( CreateFrame(msg, text::freetype::Font("C:\\WINNT\\Fonts\\Arial.ttf", 28), vi->GetDimension(), vi->GetColorSpace(), env), vi )
---
> : StaticImage( CreateFrame(msg, text::freetype::Font("/usr/share/fonts/truetype/msttcorefonts/Arial.ttf", 28), vi->GetDimension(), vi->GetColorSpace(), env), vi )
70c70
< Font font("C:\\WINNT\\Fonts\\Arial.ttf", 28);
---
> Font font("/usr/share/fonts/truetype/msttcorefonts/Arial.ttf", 28);

The path points to Arial.tff the windowsway. Maybe you guys add a ifthen routine.

d'Oursse
17th April 2007, 23:40
I'm aware of that. I've made a fontconfig branch that allows to detect the location of the font.

I need Bidoche to test it on win32 before committing it

Also the patch is wrong, as the location of the font files depends on the unix distribution.

but thanks for the report :)

Amnon82
20th April 2007, 00:09
I know that the path differs on some unix os's. A find-routine might be handy for searchig the tff-file.

d'Oursse
20th April 2007, 07:06
A find-routine might be handy for searchig the tff-file.
That's what fontconfig is for ;)

Amnon82
21st April 2007, 17:57
so it won't be a problem ...

Amnon82
9th May 2007, 20:29
What is the actual status of avisynth? alpha or beta?

nfm
9th May 2007, 23:14
I think 3.0 is dead.

d'Oursse
10th May 2007, 07:47
it is not. The develoment is just stalled at the moment

Inventive Software
3rd June 2007, 22:56
Any more news d'Oursse? I realise of course you could be taking muchos avantage of the glorious weather at the moment, but I'm more than keen to know what's been going on regarding AviSynth 3.0 development. :D ;)

shevegen
7th June 2007, 23:30
yeah we are gonna ask every 10. of the month :)

d'Oursse
8th June 2007, 21:06
we are going to switch to svn :D (maybe it's already done, I'm just back from a workshop)

dk75
9th June 2007, 12:35
yatta!!! :cool:

pasta03
19th July 2007, 00:00
Hey!
How I can download latest avisynth 3.0 witch cvs by use TortoiseCVS (under windows)
I use commend
cvs -z3 -d:pserver:anonymous@avisynth2.cvs.sourceforge.net:/cvsroot/avisynth2 co -r avisynth_3_0 avisynth
but this isn't working or I do some wrong!

Someone can write me how can I config TortoiseCVS.

d'Oursse
19th July 2007, 00:19
I suggest that you learn tortoisesvn, as we have switched to svn

pasta03
19th July 2007, 17:26
Ok!
So when you will switch on on svn?

d'Oursse
19th July 2007, 17:40
i know that my english is ugly, but i thought I was clear enough.

Right now, the svn repository is up and available.

Look here (http://sourceforge.net/svn/?group_id=57023).

But as I said previously, wait a bit. I'll do some modifications (don't expect them before the end of the next week)

pasta03
27th July 2007, 20:25
I compiling x264 (from the latest revisions x264 straight from SVN).


Building x264 from SVN:

svn co svn://svn.videolan.org/x264/trunk x264
cd x264
./configure
make
sudo make install
cd ..


So After the compilation x264 from svn I will be able to to compress to x264 from the line of commands so as in windows eg.

x264.exe --pass 1 --bitrate 6000 --stats stats.a --bframes 3 --b-pyramid --direct auto --deblock -2,-1 --subme 1 --partitions none --vbv-maxrate 25000 --me dia --thread-input --cqmfile matrices.M4G_HRM_V1 --progress --no-psnr --output NUL input.avs

or I will be able to to use only some graphic GUI as eg. MEncoder

d'Oursse
28th July 2007, 07:54
this has nothing to do with avs3, as you might see that no avisynth is detected once configure is executed

please post that question in the correct thread or in the forum related to avc codecs, please.

sl1pkn07
5th August 2007, 22:24
i have problem with a configure

./configure --with-boost-libdir-path=/usr/lib --with-boost-includedir-path=/usr/include/boost --prefix=/usr
......
hecking for STLport header files in /usr/include/stlport... yes
checking for /usr/lib/libstlport.so... yes
checking for Boost header files in /usr/include/boost... yes
checking for main in -lboost_thread-gcc-mt-gdp... no
configure: WARNING: Boost library (1_33_1) not in /usr/lib
checking for Boost header files in /usr/include/boost... yes
checking for main in -lboost_thread-gcc-mt-gdp... (cached) no
configure: WARNING: Boost library (1_33_1) not in /usr/lib
checking for Boost header files in /usr/include/boost... yes
checking for main in -lboost_thread-gcc-mt-gdp... (cached) no
configure: WARNING: Boost library (1_33) not in /usr/lib
checking for Boost header files in /usr/include/boost... yes
checking for main in -lboost_thread-gcc-mt-gdp... (cached) no
configure: WARNING: Boost library (1_33) not in /usr/lib
configure: error: "Boost is needed !"
sl1pkn07@SpinFlo:~/aplicaciones/avisynth/build/linux$

ln -s libboost_thread-gcc-mt-1_33_1.so libboost_thread-gcc-mt-gdp-1_33_1.so

same error

install boost from apt-get

i have Ubuntu Feisty 64bits

j0m
22nd August 2007, 10:38
Exact same problem as Sl1pkn07 here, Ubuntu Feisty 32 bit.

I've installed all needed libs + libs-dev versions in the official repos, and copied the circular buffer files manually, yet (as per Sl1pkn07 post) ./configure (with no switches) looks for a libboost*gdp* file, whereas my Feisty boost files have no "gdp" string in the filenames.

=A=RGOS
23rd August 2007, 08:25
Hello,

I have the same problem on my Ubuntu Gusty AMD64.
I have see the message and the path /usr/include/boost_1.33_1 isn't correct.
My libboost is in /usr/include/boost
And the source code refer to a subdirectory #include "boost/.hpp".

Please make a Debian/rules for Ubuntu / Debian users :).
I have very insterrest for testing Avinsynth on Linux.

Many thx, bye.

sl1pkn07
23rd August 2007, 22:47
I have see the message and the path /usr/include/boost_1.33_1 isn't correct.
My libboost is in /usr/include/boost


put --with-boost-includedir-path=/usr/include/boost in your configure

jamieuk
30th September 2007, 19:41
cool.

d'Oursse
30th September 2007, 20:27
always look at ./configure --help ;)

Amnon82
1st October 2007, 19:30
When can we expect the first beta or rc?

Ranguvar
2nd October 2007, 21:00
When can we expect the first beta or rc?
http://avisynth.org/AviSynth30

liquidator87
3rd October 2007, 16:23
I've the same problem of sl1pkn07... Has anyone solved?

vicfred
19th October 2007, 09:21
is avisynth available on ubuntu?

Kurtnoise
19th October 2007, 10:31
nope...

dk75
19th October 2007, 18:47
on the other hand I have this:

../../src/linker/external/plugin.cpp:30:37: error: boost/filesystem/path.hpp: No such file or directory
../../src/linker/external/plugin.cpp:31:43: error: boost/filesystem/operations.hpp: No such file or directory
make: *** [linker/external/plugin.o] Błąd 1

the thing is that I have these files in "/usr/local/include/boost-1_33_1/" and "configure" recognize boost lib and includes.

=A=RGOS
5th January 2008, 11:06
Hello all,

I solve the problem of boost library :-).
On Ubuntu Gusty AMD64.

After the bootstrap execution a have modified the configure file with the value of BOOST_VERSION_MINOR are "34" and not "33" because my version of libboost is 1.34.
After I have specified the name of boost_thread :

./configure --with-boost-lib-name=boost_thread-gcc41-mt-1_34_1

Bye,

sl1pkn07
7th January 2008, 08:09
thanks man!

liquidator87
27th February 2008, 19:52
I'm not able to compile...
Here's my command-line:
--with-boost-lib-name=boost_thread-gcc41-mt-1_34_1 --with-boost-includedir-path=/usr/include/boost --with-boost-libdir-path=/usr/lib

boost is into /usr/include/boost and the version is 1_34_1

=A=RGOS
28th February 2008, 10:15
Hello,

I'm run on Ubuntu Hardy AMD64 (it's an alpha version).

The GCC version is very important for libboost.
Now I have a GCC v4.2 and my boost lib name for avisynth is boost_thread-gcc42-mt-1_34_1

1. Install circular_buffer
2. run in build/linux/ the script ./bootstrap.sh
3. Modify configure file and replace BOOST_VERSION_MINOR="33" by BOOST_VERSION_MINOR="34"
4. ./configure --with-boost-lib-name=boost_thread-gcc42-mt-1_34_1
5. And run make

But I have a compilation error on "parser/grammar/statement.cpp" :confused:

bye...

sl1pkn07
28th February 2008, 16:30
But I have a compilation error on "parser/grammar/statement.cpp" :confused:

bye...


+1

greetings

liquidator87
28th February 2008, 19:19
Another one here...

shevegen
12th March 2008, 17:22
Hey d'Oursse

still alive? :-)

I really hope that Avisynth wont stop development. Longer breaks are fine as long as the devs dont want to stop developing Avisynth :)

At least on windows it still seems to have many people using it

pprovost
13th March 2008, 01:39
But I have a compilation error on "parser/grammar/statement.cpp" :confused:

bye...

Same error here.

Wintershade
22nd January 2009, 00:29
any news?
don't tell me Avisynth is discontinued... :(

nm
22nd January 2009, 00:44
http://forum.doom9.org/showthread.php?p=1235933#post1235933