Dear, I also use version of github. and get that error: libape-spidermonkey.c: In function ‘ape_cb_allocateuser’: libape-spidermonkey.c:3054: warning: dereferencing type-punned pointer will break strict-aliasing rules libape-spidermonkey.c: In function ‘ape_cb_del_user’: libape-spidermonkey.c:3083: warning: dereferencing type-punned pointer will break strict-aliasing rules libape-spidermonkey.c: In function ‘ape_cb_mkchan’: libape-spidermonkey.c:3110: warning: dereferencing type-punned pointer will break strict-aliasing rules libape-spidermonkey.c: In function ‘ape_cb_rmchan’: libape-spidermonkey.c:3139: warning: dereferencing type-punned pointer will break strict-aliasing rules libape-spidermonkey.c: In function ‘ape_cb_addsubuser’: libape-spidermonkey.c:3188: warning: dereferencing type-punned pointer will break strict-aliasing rules libape-spidermonkey.c: In function ‘ape_cb_delsubuser’: libape-spidermonkey.c:3202: warning: dereferencing type-punned pointer will break strict-aliasing rules
How can I fix this. Thank you On Fri, Mar 4, 2011 at 12:59 AM, erSan <[email protected]> wrote: > Thanks, i found just before your msg. > > build seems OK. > > I try this night if it's ok running APE Server > > regards, > > On 3 mar, 18:54, Anthony Catel <[email protected]> wrote: > > cd ./modules/deps/mysac > > make > > cd ../../ > > make > > > > Le 03/03/2011 18:51, erSan a crit : > > > > > Hi Nicolas, > > > > > I found but not explain. > > > > > when i extract the downloaded file from github, some files extraction > > > not ok. > > > I redo and it's better now > > > > > I have an error nevertheless > > > gcc -D_GNU_SOURCE -Wall -O2 -shared -fPIC -rdynamic -Wl,- > > > soname,libmod_spidermonkey.so -o lib/libmod_spidermonkey.so libape- > > > spidermonkey.c -I../deps/js/src/dist/include/ -L../deps/js/src/ - > > > ljs_static -lstdc++ -L./deps/mysac/ -I./deps/mysac/ -lmysac - > > > lmysqlclient_r > > > /usr/bin/ld: cannot find -lmysac > > > collect2: ld returned 1 exit status > > > make: *** [modules] Erreur 1 > > > > > I remember another message on forum, for this issue. I try to found > > > it. > > > > > Thanks a lot, and sorry for a pb no due to repository. > > > If you can tell me for mysac, i save a lot of time > > > > > Bye. > > > > > On 3 mar, 17:27, erSan<[email protected]> wrote: > > >> OK, I do > > >> but i still have config/rules.mk:311: *** invalid syntax in > > >> conditional. Stop. > > > > >> On 3 mar, 17:16, Anthony Catel<[email protected]> wrote: > > > > >>> Ok, > > >>> apt-get install autoconf2.13 > > >>> $ cd ./deps/js/src/ > > >>> $ rm ./configure&& rm ./configure.cache > > >>> $ autoconf2.1.3 > > >>> $ ./configure > > >>> Tell me if you still have > > >>> config/rules.mk:311: *** invalid syntax in conditional. Stop. > > >>> Thanks > > >>> Le 03/03/2011 17:11, erSan a crit : > > >>>> APE_Server/deps/js/src$ rm config.cache > > >>>> APE_Server/deps/js/src$ make clean > > >>>> config/rules.mk:311: *** syntaxe invalide dans la condition. Arr t. > > >>>> APE_Server/deps/js/src$ ./configure > > >>>> creating cache ./config.cache > > >>>> checking host system type... i686-pc-linux-gnu > > >>>> checking target system type... i686-pc-linux-gnu > > >>>> checking build system type... i686-pc-linux-gnu > > >>>> checking for mawk... mawk > > >>>> checking for gcc... gcc > > >>>> checking whether the C compiler (gcc ) works... yes > > >>>> checking whether the C compiler (gcc ) is a cross-compiler... no > > >>>> checking whether we are using GNU C... yes > > >>>> checking whether gcc accepts -g... yes > > >>>> checking for c++... c++ > > >>>> checking whether the C++ compiler (c++ ) works... yes > > >>>> checking whether the C++ compiler (c++ ) is a cross-compiler... no > > >>>> checking whether we are using GNU C++... yes > > >>>> checking whether c++ accepts -g... yes > > >>>> checking for ranlib... ranlib > > >>>> checking for as... /usr/bin/as > > >>>> checking for ar... ar > > >>>> checking for ld... ld > > >>>> checking for strip... strip > > >>>> checking for windres... no > > >>>> checking whether gcc and cc understand -c and -o together... yes > > >>>> checking how to run the C preprocessor... gcc -E > > >>>> checking how to run the C++ preprocessor... c++ -E > > >>>> checking for sb-conf... no > > >>>> checking for ve... no > > >>>> checking for a BSD compatible install... /usr/bin/install -c > > >>>> checking whether ln -s works... yes > > >>>> checking for perl5... no > > >>>> checking for perl... /usr/bin/perl > > >>>> checking for minimum required perl version>= 5.006... 5.010001 > > >>>> checking for full perl installation... yes > > >>>> checking for python... /usr/bin/python > > >>>> checking for doxygen... : > > >>>> checking for autoconf... : > > >>>> checking for unzip... /usr/bin/unzip > > >>>> checking for zip... /usr/bin/zip > > >>>> checking for makedepend... no > > >>>> checking for xargs... /usr/bin/xargs > > >>>> checking for gmake... no > > >>>> checking for make... /usr/bin/make > > >>>> checking for X... no > > >>>> checking whether the compiler supports -Wno-invalid-offsetof... yes > > >>>> checking whether the compiler supports -Wno-variadic-macros... yes > > >>>> checking whether ld has archive extraction flags... yes > > >>>> checking that static assertion macros used in autoconf tests work... > > >>>> yes > > >>>> checking for 64-bit OS... no > > >>>> checking for ANSI C header files... yes > > >>>> checking for working const... yes > > >>>> checking for mode_t... yes > > >>>> checking for off_t... yes > > >>>> checking for pid_t... yes > > >>>> checking for size_t... yes > > >>>> checking for ssize_t... yes > > >>>> checking for st_blksize in struct stat... yes > > >>>> checking for siginfo_t... yes > > >>>> checking for stdint.h... yes > > >>>> checking for the size of void*... 4 > > >>>> checking for the alignment of void*... 4 > > >>>> checking for the size of double... 8 > > >>>> checking for int16_t... yes > > >>>> checking for int32_t... yes > > >>>> checking for int64_t... yes > > >>>> checking for int64... no > > >>>> checking for uint... yes > > >>>> checking for uint_t... no > > >>>> checking for uint16_t... no > > >>>> checking for uname.domainname... yes > > >>>> checking for uname.__domainname... no > > >>>> checking for visibility(hidden) attribute... yes > > >>>> checking for visibility(default) attribute... yes > > >>>> checking for visibility pragma support... yes > > >>>> checking For gcc visibility bug with class-level attributes (GCC bug > > >>>> 26905)... no > > >>>> checking For x86_64 gcc visibility bug with builtins (GCC bug > > >>>> 20297)... no > > >>>> checking for dirent.h that defines DIR... yes > > >>>> checking for opendir in -ldir... no > > >>>> checking for sys/byteorder.h... no > > >>>> checking for compat.h... no > > >>>> checking for getopt.h... yes > > >>>> checking for sys/bitypes.h... yes > > >>>> checking for memory.h... yes > > >>>> checking for unistd.h... yes > > >>>> checking for gnu/libc-version.h... yes > > >>>> checking for nl_types.h... yes > > >>>> checking for malloc.h... yes > > >>>> checking for X11/XKBlib.h... no > > >>>> checking for sys/statvfs.h... yes > > >>>> checking for sys/statfs.h... yes > > >>>> checking for sys/vfs.h... yes > > >>>> checking for sys/mount.h... yes > > >>>> checking for mmintrin.h... no > > >>>> checking for new... yes > > >>>> checking for sys/cdefs.h... yes > > >>>> checking for gethostbyname_r in -lc_r... no > > >>>> checking for atan in -lm... yes > > >>>> checking for dlopen in -ldl... yes > > >>>> checking for dlfcn.h... yes > > >>>> checking for dladdr... yes > > >>>> checking for socket in -lsocket... no > > >>>> checking for pthread_create in -lpthreads... no > > >>>> checking for pthread_create in -lpthread... yes > > >>>> checking whether gcc accepts -pthread... yes > > >>>> checking whether mmap() sees write()s... yes > > >>>> checking whether gcc needs -traditional... no > > >>>> checking for 8-bit clean memcmp... yes > > >>>> checking for fchmod... yes > > >>>> checking for flockfile... yes > > >>>> checking for getc_unlocked... yes > > >>>> checking for _getc_nolock... no > > >>>> checking for getpagesize... yes > > >>>> checking for lchown... yes > > >>>> checking for localtime_r... yes > > >>>> checking for lstat64... yes > > >>>> checking for memmove... yes > > >>>> checking for random... yes > > >>>> checking for rint... yes > > >>>> checking for sbrk... yes > > >>>> checking for snprintf... yes > > >>>> checking for stat64... yes > > >>>> checking for statvfs... yes > > >>>> checking for statvfs64... yes > > >>>> checking for strerror... yes > > >>>> checking for strtok_r... yes > > >>>> checking for truncate64... yes > > >>>> checking for wcrtomb... yes > > >>>> checking for mbrtowc... yes > > >>>> checking for res_ninit()... yes > > >>>> checking for gnu_get_libc_version()... yes > > >>>> checking for iconv in -lc... yes > > >>>> checking for iconv()... yes > > >>>> checking for iconv() with const input... no > > >>>> checking for an implementation of va_copy()... yes > > >>>> checking for an implementation of __va_copy()... yes > > >>>> checking whether va_lists can be copied by value... yes > > >>>> checking for gcc 3.0 ABI... yes > > >>>> checking for C++ "explicit" keyword... yes > > >>>> checking for C++ "typename" keyword... yes > > >>>> checking for modern C++ template specialization syntax support... > yes > > >>>> checking whether partial template specialization works... yes > > >>>> checking whether operators must be re-defined for templates derived > > >>>> from templates... no > > >>>> checking whether we need to cast a derived template to pass as its > > >>>> base class... no > > >>>> checking whether the compiler can resolve const ambiguities for > > >>>> templates... yes > > >>>> checking whether the C++ "using" keyword can change access... yes > > >>>> checking whether the C++ "using" keyword resolves ambiguity... yes > > >>>> checking for "std::" namespace... yes > > >>>> checking whether standard template operator!=() is ambiguous... > > >>>> unambiguous > > >>>> checking for C++ reinterpret_cast... yes > > >>>> checking for C++ dynamic_cast to void*... yes > > >>>> checking whether C++ requires implementation of unused virtual > > >>>> methods... yes > > >>>> checking for trouble comparing to zero near std::operator!=()... no > > >>>> checking for LC_MESSAGES... yes > > >>>> checking for valid optimization flags... yes > > >>>> checking for __cxa_demangle... yes > > >>>> checking for unwind.h... yes > > >>>> checking for _Unwind_Backtrace... yes > > >>>> checking for gcc -pipe support... yes > > >>>> checking whether C compiler supports -fprofile-generate... yes > > >>>> checking whether C++ compiler has -pedantic long long bug... no > > >>>> checking for correct temporary object destruction order... yes > > >>>> checking for correct overload resolution with const and templates... > > >>>> no > > >>>> checking for tm_zone tm_gmtoff in struct tm... yes > > >>>> checking for setlocale... yes > > >>>> checking for localeconv... yes > > >>>> updating cache ./config.cache > > >>>> creating ./config.status > > >>>> creating config/autoconf.mk > > >>>> creating js-config.h > > >>>> js-config.h is unchanged > > >>>> config/autoconf.mk is unchanged > > >>>> invoking make to create js-config script > > >>>> config/rules.mk:311: *** invalid syntax in conditional. Stop. > > >>>> /APE_Server/deps/js/src$ make > > >>>> config/rules.mk:311: *** syntaxe invalide dans la condition. Arr t. > > >>>> On 3 mar, 17:03, Anthony Catel<[email protected]> wrote: > > >>>>> cd deps/js/src/ > > >>>>> rm config.cache > > >>>>> make clean > > >>>>> ./configure > > >>>>> (^ error ?) > > >>>>> make > > >>>>> (^ error ?) > > >>>>> Le 03/03/2011 17:01, erSan a crit : > > >>>>>> It's seems a little better but same error > > >>>>>> ./build.sh results > > >>>>>> ....... > > >>>>>> ....... > > >>>>>> #define _REENTRANT 1 > > >>>>>> #endif /* _JS_CONFDEFS_H_ */ > > >>>>>> creating Makefile > > >>>>>> updating shell/Makefile > > >>>>>> updating lirasm/Makefile > > >>>>>> updating jsapi-tests/Makefile > > >>>>>> updating tests/Makefile > > >>>>>> updating config/Makefile > > >>>>>> updating config/mkdepend/Makefile > > >>>>>> updating > > > > ... > > > > plus de détails » > > -- > You received this message because you are subscribed to the Google > Groups "APE Project" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/ape-project?hl=en > --- > APE Project (Ajax Push Engine) > Official website : http://www.ape-project.org/ > Git Hub : http://github.com/APE-Project/ > -- You received this message because you are subscribed to the Google Groups "APE Project" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/ape-project?hl=en --- APE Project (Ajax Push Engine) Official website : http://www.ape-project.org/ Git Hub : http://github.com/APE-Project/
