Page 1 of 1

1.24.3 configure no --enable-sockets?

Posted: Thu Dec 02, 2010 6:07 am
by BlankMan
Pulled the svn code, must say it compiles a lot cleaner then 1.24.2 on openSuSE 11.2 or 11.3, didn't have to make any changes to the source code to accomplish that. (Did in 1.24.2.)

But when running configure with:

Code: Select all

./configure --with-ffmpeg --with-libarch=lib64 --with-mysql=/usr --with-webdir=/srv/www/htdocs/ZM --with-cgidir=/srv/www/cgi-bin --with-webuser=wwwrun --with-webgroup=www --enable-crashtrace=no --enable-debug=yes --disable-mmap ZM_SSL_LIB=openssl --enable-sockets --with-extralibs="-lfaac -lmp3lame -logg -lvorbis -lamrnb -lamrwb" CPPFLAGS=-D__STDC_CONSTANT_MACROS
I get:

Code: Select all

configure: WARNING: unrecognized options: --enable-sockets
Obviously that option is no longer there or enabled by default, so which is it and what does that mean then as to function?

Haven't installed the compiled code yet, my other question is can I just do a "make install" and everything will be fine? I won't lose any events and/or have to make any config changes, nothing to worry about with the mySQL DB, or any other gotchas?

Re: 1.24.3 configure no --enable-sockets?

Posted: Thu Dec 02, 2010 6:14 am
by jdhar
Haven't installed the compiled code yet, my other question is can I just do a "make install" and everything will be fine? I won't lose any events and/or have to make any config changes, nothing to worry about with the mySQL DB, or any other gotchas?
In short, yes, nothing will be lost. Once you do a make, do your make install (with appropriate permissions), and then run zupdate.pl --version <old>. So if upgrading from 1.24.2, use 'zmupdate.pl --version 1.24.2'

If staying on the same revision and updating from source code, you can just do zmupdate.pl -f

Posted: Thu Dec 02, 2010 6:25 am
by BlankMan
Thanks, was not aware of the zmupdate.pl step, what does that do?

And of equal importance, once that is done what if I have to go back to 1.24.2??

So if I pull the svn again tomorrow and something in it changed I need to do the zmupdate.pl again. Never knew that, but then, never had pulled code that might have changes.

Posted: Thu Dec 02, 2010 6:35 am
by jdhar
BlankMan wrote:Thanks, was not aware of the zmupdate.pl step, what does that do?

And of equal importance, once that is done what if I have to go back to 1.24.2??

So if I pull the svn again tomorrow and something in it changed I need to do the zmupdate.pl again. Never knew that, but then, never had pulled code that might have changes.
zmupdate.pl --version modifies your database to be in the current format. It does this by iterating through all of the revisions in between your "from" revision and the new one, like a patch-set.

If you want to go back, you can do the same thing ("from" version is now 1.24.3).

When you pull from SVN, you only need to do zmupdate.pl -f when something affecting the database has changed, and it doesn't hurt to do it anyway (it's quick). For example, when I'm making changes to the XML Plugin, I may add a configuration option to the database (available in the options panel) that wasn't available yesterday. if you don't do a zmupdate.pl -f, you won't see this.

I switch between 1.24.1, .2 and .3 probably 10 times a day, so I have this down-pat :)

Posted: Thu Dec 02, 2010 6:43 am
by BlankMan
Thanks again. makes sense for DB changes. This will be my first upgrade so never done this before.

Any idea on the --enable-sockets missing thing?

Posted: Thu Dec 02, 2010 6:45 am
by jdhar
BlankMan wrote:Thanks again. makes sense for DB changes. This will be my first upgrade so never done this before.

Any idea on the --enable-sockets missing thing?
Building from source can be a pain, but once you get it once, updating to new versions is so much easier and things don't get broken like can happen sometimes with packages.

Sorry, no clue on the --enable-sockets.

Posted: Thu Dec 02, 2010 7:00 am
by BlankMan
jdhar wrote:Building from source can be a pain, but once you get it once, updating to new versions is so much easier and things don't get broken like can happen sometimes with packages..
Not exactly, when I upgraded from openSuSE 11.2 to openSuSE 11.3 I had to undo in 11.3 some library links for ffmpeg I had to do in 11.2, and apply a patch to the zm source in 11.3 and add a configure option. I updated this thread with the steps. That is all distribution related, and I must say other then the unanswered --enable-sockets thing 1.24.3 compiled on 11.3 just as 1.24.2 did. But whether it really works or not is unanswered as of yet.