Re: [protobuf] Re: Why does ARMv5 thinks their are 2 implementations for these 4 functions in repeated_field.CC?
A lot of C++ compilers do not implement the (ridiculously complicated) standard correctly, especially when it comes to complex templates. If you can provide a patch which fixes your problem, we could consider adopting it, but otherwise the only advice I can give is: use GCC, Clang, or MSVC. On Fri, Feb 11, 2011 at 2:35 AM, RainBow wrote: > I have no clue what QT v4.6 is doing internally. > > I took all the PB files and put them in a .mmp and compiled it through > Carbide v2.7 IDE for armv5 (which uses exactly same version of armcc > as posted above). Surprisingly, it compiled very smoothly at the very > first attempt. QT is gaytown...fer sure !!! > > -- > You received this message because you are subscribed to the Google Groups > "Protocol Buffers" group. > To post to this group, send email to protobuf@googlegroups.com. > To unsubscribe from this group, send email to > protobuf+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/protobuf?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To post to this group, send email to protobuf@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Why does ARMv5 thinks their are 2 implementations for these 4 functions in repeated_field.CC?
I have no clue what QT v4.6 is doing internally. I took all the PB files and put them in a .mmp and compiled it through Carbide v2.7 IDE for armv5 (which uses exactly same version of armcc as posted above). Surprisingly, it compiled very smoothly at the very first attempt. QT is gaytown...fer sure !!! -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To post to this group, send email to protobuf@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Why does ARMv5 thinks their are 2 implementations for these 4 functions in repeated_field.CC?
More info: This is for Symbian^3, using QT v4.6. If I switch compiler to use GCCE, then the code compiles without making any changes. I created a totally new project and repeated the same exercise for ARM but still the same results. My config.h is handcrafted (based on Android config) and pasted below (if that could help). My ARM version is: vshakya@Eng-Vshakya ~ $ armcc --vsn ARM/Thumb C/C++ Compiler, RVCT2.2 [Build 686] For support please contact support...@arm.com Software supplied by: ARM Limited // - /* the name of */ #define HASH_MAP_CLASS unordered_map /* the location of */ #define HASH_MAP_H /* the namespace of hash_map/hash_set */ #define HASH_NAMESPACE std::tr1 /* the name of */ #define HASH_SET_CLASS unordered_set /* the location of */ #define HASH_SET_H /* Define to 1 if you have the header file. */ #define HAVE_DLFCN_H 1 /* Define to 1 if you have the header file. */ #define HAVE_FCNTL_H 1 /* Define to 1 if you have the `ftruncate' function. */ #define HAVE_FTRUNCATE 1 //viren+ //#if defined(ANDROID) #define SYMBIAN_QT_PORT 1 #if defined(SYMBIAN_QT_PORT) //viren- /* * TODO: Figure out how to use stlport unordered_map and set. * For some reason they don't work when I try to point the * HASH_MAP_H and HASH_SET_H to the stlport files, I get * compile timer errors. */ /* define if the compiler has hash_map */ #undef HAVE_HASH_MAP /* define if the compiler has hash_set */ #undef HAVE_HASH_SET #else /* define if the compiler has hash_map */ #define HAVE_HASH_MAP 1 /* define if the compiler has hash_set */ #define HAVE_HASH_SET 1 #endif /* Define to 1 if you have the header file. */ #define HAVE_INTTYPES_H 1 /* Define to 1 if you have the header file. */ #define HAVE_LIMITS_H 1 /* Define to 1 if you have the header file. */ #define HAVE_MEMORY_H 1 /* Define to 1 if you have the `memset' function. */ #define HAVE_MEMSET 1 /* Define to 1 if you have the `mkdir' function. */ #define HAVE_MKDIR 1 /* Define if you have POSIX threads libraries and header files. */ #define HAVE_PTHREAD 1 //#define HAVE_PTHREAD 0 //viren : no support for pthread on symbian ??? /* Define to 1 if you have the header file. */ #define HAVE_STDINT_H 1 /* Define to 1 if you have the header file. */ #define HAVE_STDLIB_H 1 /* Define to 1 if you have the `strchr' function. */ #define HAVE_STRCHR 1 /* Define to 1 if you have the `strerror' function. */ #define HAVE_STRERROR 1 /* Define to 1 if you have the header file. */ #define HAVE_STRINGS_H 1 /* Define to 1 if you have the header file. */ #define HAVE_STRING_H 1 /* Define to 1 if you have the `strtol' function. */ #define HAVE_STRTOL 1 /* Define to 1 if you have the header file. */ #define HAVE_SYS_STAT_H 1 /* Define to 1 if you have the header file. */ #define HAVE_SYS_TYPES_H 1 /* Define to 1 if you have the header file. */ #define HAVE_UNISTD_H 1 /* Enable classes using zlib compression. */ //#define HAVE_ZLIB 1 #define HAVE_ZLIB 0 //viren : enable zlib later...deadline s near... /* Define to the sub-directory in which libtool stores uninstalled libraries. */ #define LT_OBJDIR ".libs/" /* Name of package */ #define PACKAGE "protobuf" /* Define to the address where bug reports for this package should be sent. */ #define PACKAGE_BUGREPORT "protobuf@googlegroups.com" /* Define to the full name of this package. */ #define PACKAGE_NAME "Protocol Buffers" /* Define to the full name and version of this package. */ #define PACKAGE_STRING "Protocol Buffers 2.3.0" /* Define to the one symbol short name of this package. */ #define PACKAGE_TARNAME "protobuf" /* Define to the version of this package. */ #define PACKAGE_VERSION "2.3.0" /* Define to necessary symbol if this constant uses a non-standard name on your system. */ /* #undef PTHREAD_CREATE_JOINABLE */ /* Define to 1 if you have the ANSI C header files. */ #define STDC_HEADERS 1 /* Version number of package */ #define VERSION "2.3.0" /* Define to 1 if on AIX 3. System headers sometimes define this. We just want to avoid a redefinition error message. */ #ifndef _ALL_SOURCE /* # undef _ALL_SOURCE */ #endif /* Enable GNU extensions on systems that have them. */ #ifndef _GNU_SOURCE # define _GNU_SOURCE 1 #endif /* Define to 1 if on MINIX. */ /* #undef _MINIX */ /* Define to 2 if the system does not provide POSIX.1 features except with this defined. */ /* #undef _POSIX_1_SOURCE */ /* Define to 1 if you need to in order for `stat' and other things to work. */ /* #undef _POSIX_SOURCE */ /* Enable extensions on Solaris. */ #ifndef __EXTENSIONS__ //# define __EXTENSIONS__ 1 # define __EXTENSIONS__ 0 //viren #endif #ifndef _POSIX_PTHREAD_SEMANTICS # define _POSIX_PTHREAD_SEMANTICS 1 #endif #ifndef _TANDEM_SOURCE //# define _TANDEM_SOURCE 1 # define _TANDEM_SOURCE 0 //viren #endif -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To post
