mail it again
On Wed, Aug 6, 2008 at 11:00 AM, serusers-request@lists.iptel.org wrote:
Send Serusers mailing list submissions to serusers@lists.iptel.org
To subscribe or unsubscribe via the World Wide Web, visit http://lists.iptel.org/mailman/listinfo/serusers or, via email, send a message with subject or body 'help' to serusers-request@lists.iptel.org
You can reach the person managing the list at serusers-owner@lists.iptel.org
When replying, please edit your Subject line so it is more specific than "Re: Contents of Serusers digest..."
Today's Topics:
- 2.0 survey (Jiri Kuthan)
- ser 2.1 - compilation error - conflicting types (Tomasz Zieleniewski)
- ser 2.1 - compilation error - conflicting types (Tomasz Zieleniewski)
- SER/FIFO not accessible (cindy.cao)
Message: 1 Date: Tue, 05 Aug 2008 19:20:33 +0200 From: Jiri Kuthan jiri@iptel.org Subject: [Serusers] 2.0 survey To: "serusers@iptel.org" serusers@iptel.org Message-ID: 48988BE1.9030503@iptel.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed
I'm just wondering if folks using the 2.0 have found so far any issue which has not been tracked -- I've been off-line for vacation, IETF and a couple of other trips and began to be uncertain if I might have missed something. Any concerns/issues/comments regarding 2.0 are most welcome, publicly or privately.
Thanks a lot
-jiri
Message: 2 Date: Wed, 6 Aug 2008 01:11:34 +0200 From: "Tomasz Zieleniewski" tzieleniewski@gmail.com Subject: [Serusers] ser 2.1 - compilation error - conflicting types To: serusers@lists.iptel.org, serusers@iptel.org Message-ID: 5fd52d7a0808051611g2017ff27uef0685ef960450d@mail.gmail.com Content-Type: text/plain; charset="iso-8859-2"
Hi,
When I try to compile ser from sources I get the following conflicting types errors: gcc -m64 -g -O9 -funroll-loops -Wcast-align -minline-all-stringops -falign-loops -ftree-vectorize -mtune=opteron -Wall -DNAME='"ser"' -DVERSION='"2.1.0-dev23-make"' -DARCH='"x86_64"' -DOS='linux_' -DOS_QUOTED='"linux"' -DCOMPILER='"gcc 4.3.1"' -D__CPU_x86_64 -D__OS_linux -DSER_VER=2001000 -DCFG_DIR='"/usr/local/etc/ser/"' -DMODS_DIR='"/usr/local/lib/ser/modules/"' -DPKG_MALLOC -DSHM_MEM -DSHM_MMAP -DDNS_IP_HACK -DUSE_IPV6 -DUSE_MCAST -DUSE_TCP -DDISABLE_NAGLE -DHAVE_RESOLV_RES -DUSE_DNS_CACHE -DUSE_DNS_FAILOVER -DUSE_DST_BLACKLIST -DUSE_NAPTR -DDBG_QM_MALLOC -DUSE_TLS -DTLS_HOOKS -DFAST_LOCK -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024 -DCC_GCC_LIKE_ASM -DHAVE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN -DHAVE_SCHED_YIELD -DHAVE_MSG_NOSIGNAL -DHAVE_MSGHDR_MSG_CONTROL -DHAVE_ALLOCA_H -DHAVE_TIMEGM -DHAVE_SCHED_SETSCHEDULER -DHAVE_EPOLL -DHAVE_SIGIO_RT -DSIGINFO64_WORKARROUND -DUSE_FUTEX -DHAVE_SELECT -c lock_ops.c -o lock_ops.o In file included from ut.h:53, from lock_ops.c:28: /usr/include/sys/types.h:46: error: conflicting types for 'loff_t' /usr/include/linux/types.h:30: error: previous declaration of 'loff_t' was here /usr/include/sys/types.h:62: error: conflicting types for 'dev_t' /usr/include/linux/types.h:13: error: previous declaration of 'dev_t' was here In file included from /usr/include/sys/types.h:133, from ut.h:53, from lock_ops.c:28: /usr/include/time.h:105: error: conflicting types for 'timer_t' /usr/include/linux/types.h:22: error: previous declaration of 'timer_t' was here In file included from ut.h:53, from lock_ops.c:28: /usr/include/sys/types.h:198: error: conflicting types for 'int64_t' /usr/include/linux/types.h:98: error: previous declaration of 'int64_t' was here /usr/include/sys/types.h:204: error: conflicting types for 'u_int64_t' /usr/include/linux/types.h:97: error: previous declaration of 'u_int64_t' was here In file included from /usr/include/sys/types.h:220, from ut.h:53, from lock_ops.c:28: /usr/include/sys/select.h:78: error: conflicting types for 'fd_set' /usr/include/linux/types.h:12: error: previous declaration of 'fd_set' was here In file included from ut.h:53, from lock_ops.c:28: /usr/include/sys/types.h:235: error: conflicting types for 'blkcnt_t' /usr/include/linux/types.h:124: error: previous declaration of 'blkcnt_t' was here make: *** [lock_ops.o] B??d 1
Is there any fix for that?
Regards Tomasz