[dt1]

Is it possible to build Serna on amd64?

[timof]

Originally Posted by dt1

Is it possible to build Serna on amd64?

I guess there should not be a problem to build Serna Free on amd64, though we didn't try this.

Please tell us whether it has been built successfully if you do this.

[dt1]

Sorry for my english.

I got errors like this:
g++ -c -pipe -Wall -W -O2 -D_REENTRANT -DNDEBUG -DNOCVSID -DOALLOC_TYPE=4 -DMULTI_THREADED -DQT_THREAD_SUPPORT -DQT_DLL -DQT3_SUPPORT -I"/home/user/test/serna/serna-free-src-20090710/sfworks/common/sysdep/i386-linux-g++" -I"/usr/share/qt4/include" -I"/usr/share/qt4/mkspecs/linux-g++" -I"/home/user/test/serna/serna-free-src-20090710/sfworks" -I"/home/user/test/serna/serna-free-src-20090710/build/sfworks" -I"/home/user/test/serna/serna-free-src-20090710/sfworks/common/zipfile" -I"/home/user/test/serna/serna-free-src-20090710/sfworks/common/impl" -I"/usr/share/qt4/include/QtCore" -I"/home/user/test/serna/serna-free-src-20090710/sfworks/common/impl/unix" -I"/home/user/test/serna/serna-free-src-20090710/sfworks/common/impl/linux" -o obj/StringCvt.o /home/user/test/serna/serna-free-src-20090710/sfworks/common/impl/StringCvt.cxx
In file included from /home/user/test/serna/serna-free-src-20090710/sfworks/common/impl/StringCvt.cxx:38:
/home/user/test/serna/serna-free-src-20090710/sfworks/common/common_limits.h:168:9: warning: undefining "__STDC_VERSION__"
/home/user/test/serna/serna-free-src-20090710/sfworks/common/RefCntStorage.h: In static member function ‘static void* StringPrivate::RefCntData<E>:perator new(size_t, StringPrivate::size_type) [with E = QChar]’:
/home/user/test/serna/serna-free-src-20090710/sfworks/common/RefCntStorage.h:135: instantiated from ‘void Common::RefCntStorage<E, T, A>::alloc(typename A::size_type) [with E = QChar, T = std::char_traits<QChar>, A = std::allocator<QChar>]’
/home/user/test/serna/serna-free-src-20090710/sfworks/common/RefCntStorage.h:352: instantiated from ‘Common::RefCntStorage<E, T, A>::RefCntStorage(typename A::size_type, typename A::size_type, E, const A&) [with E = QChar, T = std::char_traits<QChar>, A = std::allocator<QChar>]’
/home/user/test/serna/serna-free-src-20090710/sfworks/common/FlexString.i:197: instantiated from ‘Common::flex_string<E, T, A, S>::flex_string(long unsigned int, typename T::char_type, const A&) [with E = QChar, T = std::char_traits<QChar>, A = std::allocator<QChar>, Storage = Common::RefCntStorage<QChar, std::char_traits<QChar>, std::allocator<QChar> >]’
/home/user/test/serna/serna-free-src-20090710/sfworks/common/String.h:76: instantiated from here
/home/user/test/serna/serna-free-src-20090710/sfworks/common/RefCntStorage.h:73: error: cast from ‘QChar (*)[1]’ to ‘StringPrivate::size_type’ loses precision


The problem is that you typedef size_type as unsigned int, so it fails on amd64, cause int has a size of 4 bytes, while pointer has a size of 8 bytes.

[timof]

I'd suggest you to change size_type definition to the size of the pointer. If it will work, you can send us a patch as described in http://www.syntext.com/products/sern.../free-license/

[dt1]

I tried, but there are many definitions of size_type. It will be better to put one definition in header file and include it everywhere. Besides redefining involves conflicts in template specializations. I suppose that's not just patch changes.

[nomeata]

Is there a good reason not to use (void *) instead of size_type?