zoneminder compile error (was: For PacoLM)

[Confusticated]

Hi PacoLM,

(This is the quickest and easiest method for me to communicate with you, we can always delete the thread when we are done)

I have slept on it we need to find a starting point (this is all hypothetical and subjective) from what is known:

The compile error is related to an arm register.
The application source code comes from a reputable place

I surmise:
The cpu register information is imparted from the included header files belonging to the compiler.
It is unlikely to be a coding error.

That leads me:
Both the application and the compiler are multi platform, possibly making it a porting issue (of either one).
Both the application and the compiler have been through numerous generations (and subsequently, header file changes).

I suggest you investigate the second issue first, as I believe it to be the most likely.
See if you can track down which version of which compiler was used by the application developers for the particular version of the application source that you are trying to compile.
If you can install the same compiler, see what results you get using it.
If you can't, investigate any differences between the compiler header files against the version you are using.

That's all I can come up with on the information you have given me.
I will need the specific information required to duplicate your development system to be any further help (where and how you got the application source, compiler, diistro and the changes made to it, etc).

Bear in mind, diagnosing errors at a distance of 1262km is never an easy thing, I may be leading you up the garden path.


 

[PacoLM]

Both the application and the compiler have been through numerous generations (and subsequently, header file changes).
I suggest you investigate the second issue first, as I believe it to be the most likely.
See if you can track down which version of which compiler was used by the application developers for the particular version of the application source that you are trying to compile.
If you can install the same compiler, see what results you get using it.
If you can't, investigate any differences between the compiler header files against the version you are using.

 I will download the source code for the version 1.24.4 of Zoneminder that I have working in one of my guruplugs, then compare the source files with the newer version, looking for a difference. I have contacted with the Zoneminder developers and made the same questions I did to you.

 I will post here the findings, if any.

 Thanks for your help,

PacoLM

[PacoLM]

Hi,

 I have more data, I have tried to compile the previous version 1.24.4, and still the same error. I have tried this settings:

Code:

export CFLAGS="-march=armv5te -mtune=arm926ej-s -O2 -fomit-frame-pointer"
export CXXFLAGS="-march=armv5te -mtune=arm926ej-s -O2 -fomit-frame-pointer"
export CPPFLAGS="${CFLAGS}"

./configure --with-webdir=/var/www/zm --with-cgidir=/usr/lib/cgi-bin \
ZM_DB_HOST=localhost ZM_DB_NAME=zm ZM_DB_USER=zmuser \
ZM_DB_PASS=zmpass ZM_SSL_LIB=openssl --enable-debug=no \
--with-webgroup=www-data --with-webuser=www-data --enable-mmap=yes --with-libarch=lib --with-ffmpeg=/usr/local/bin CPPFLAGS="-D__STDC_CONSTANT_MACROS ${CPPFLAGS}"

So, seems that there's a problem in the flags I'm using, because I have the same application working in the another guruplug perfectly, but installed from the repository.

I continue working on it...

PacoLM

[PacoLM]

Hi,

 Fixed with the help of my friend Paco Gil:

Well the fix turned out to be changing cr2 to fault_address in zm_signal.cpp. I forgot where I got that solution from but it compiles without problem now.

Now I'm reinstalling the complete OS, I did too many dirty things on the guruplug and only to have Zoneminder working it's 89% full.

Thanks for your help!

[Confusticated]

I was wrong, it is a porting issue, negative credits to me on this one
I leave it up to you whether this stays PacoLM, if you don't want this thread around delete your posts and I'll do the same.

[apemberton]

I have been watching this thread from afar and have found it useful in that i am not alone with problems with ZM. I also had been looking at zm_signal.cpp source since my error logs indicated ZM was crashing there. I havn't had time to take the ZM source code and compile it. (My sheevaplug with ZM on has a 1TB eSata disk attached so I would have (and maybe still will) compiled ZM on the 'plug natively.)

I guess ZM testers can only prove the code on Intel/AMD hardware.

So thanks for the insight anyway.

[PacoLM]

I guess ZM testers can only prove the code on Intel/AMD hardware.

The funny thing here is that there's a armel debian package that you could install from repositories (ZM V1.24.4), so someone had to correct this 'bug' before releasing the package, isn't it?. I have found no documentation, I need to check the debian package to see if the error is corrected there.

Regards,

PacoLM