similar to: [LLVMdev] Compiling with -ansi and -pedantic

Hi guys i'm using asterisk 11.18.0. I need to send the pound # sign to my SIP provider, but each time it's reencoded in %23. I try to put pedantic=yes in the sip.conf as advised here: http://www.voip-info.org/wiki/view/Asterisk+SIP+pedantic but nothing's changed. Have someone already met this issue please ? thanks a lot, regards, Alan

G++ 4.x.x with -pedantic option reject comma at end of enumerator list: Attached patches let LLVM Instruction.h and Type.h headers compile using G++ 4.x.x with lot warrnigs but without errors. Vladimir -------------- next part -------------- A non-text attachment was scrubbed... Name: Instruction.h.patch Type: application/octet-stream Size: 1332 bytes Desc: not available URL:

Chris said something about Xcode fixing this ? It doesn't happen with the GCC 3.4.6 compiler on Linux so that's why I missed it, but I thought Chris had fixed it. Reid. On Fri, 2006-11-03 at 08:48 -0400, Jim Laskey wrote: > The build is failing with; > > LiveIntervalAnalysis.cpp:218: error: floating constant exceeds range > of 'double' >

Hello developers. I have made a yes/no 'pedantic' patch that affects how ssh command line and other agents that employ yes/no prompts interpret results. The nature of the patch is the following: When prompted with things like: ----SNIP---- ./ssh localhost The authenticity of host 'localhost (127.0.0.1)' can't be established. RSA key fingerprint is

hello list, when I use method lda of the MASS package I experience a warning: variables are collinear in: lda.default(data[train, ], classes[train]) Is there an easy way to recover from this issue within the MASS package? Or how can I tell how severe this issue is at all? I understand that I shouldn't use lda at all with collinear data and should use "quadratische" (squared?)

Hi List, I have a provider that uses 6060# as a prefix, but when I send the INVITE asterisk is changing the number to 6060%23. I have activated pedantic=yes in the sip.conf but it seems not working at all. I have asterisk 11.7.0. Can someone please guide me here? Thanks, Wilmar -------------- next part -------------- An HTML attachment was scrubbed... URL:

The build is failing with; LiveIntervalAnalysis.cpp:218: error: floating constant exceeds range of 'double' LiveIntervalAnalysis.cpp:253: error: floating constant exceeds range of 'double' LiveIntervalAnalysis.cpp:328: error: floating constant exceeds range of 'double' LiveIntervalAnalysis.cpp:1350: error: floating constant exceeds range of 'double' If I

Thanks very much for the responses on my last three issues. I've incorporated the appropriate changes into the budding Debian package. I feel embarrassed to raise this one, but in the interests of shutting lintian up maybe this could be fixed at some point: I: hivex: spelling-error-in-manpage usr/share/man/man1/hivexregedit.1.gz reencode re-encode I: libhivex-perl: spelling-error-in-manpage

Hello, Trying to #include a 'make install'-ed LLVM header gives the following error: #error "Must #define __STDC_LIMIT_MACROS before #including Support/DataTypes.h" How could I get past this? The documentation I've read so far seems to suggest that LLVM is meant to be used from inside its own source tree. Does this mean that make install is not "officially"

On 1/14/19 6:15 AM, Richard W.M. Jones wrote: > In commit 3775916120749e935d287f35cb29ff6c586656df (and before that in > discussions with Eric) we decided that we should try to allow plugins > to be compiled with C compilers other than GCC or Clang (or with very > old / peculiar / incompatible versions of those compilers). > > However until we test this we cannot guarantee that

We previously discussed allowing the plugin API to be consumed by non-GCC/non-Clang/old compilers. This implements a test. Rich.

In commit 3775916120749e935d287f35cb29ff6c586656df (and before that in discussions with Eric) we decided that we should try to allow plugins to be compiled with C compilers other than GCC or Clang (or with very old / peculiar / incompatible versions of those compilers). However until we test this we cannot guarantee that changes to the code will not break this in future, hence this test. Note

Having a difficult problem getting my pam_access.so module enforced on a 3.0.22 version of Samba. Here is my /etc/pam.d/samba file: auth required pam_winbind.so debug account required pam_access.so account sufficient pam_winbind.so debug account include system-auth session include system-auth session required pam_winbind.so debug My

Hello I use a new samba server with LDAP support as PDC for some Windows2000 and WindowsXP machines. All is working nice. The useer can login with a user/password in the domain, we have remote profiles, the user can access the samba shares and print etc. But after some time (< 1 day) we get a smbstatus output like the attached file. Users are connected multiple times with the same share

fansi provides counterparts to the base string manipulation functions substr, strwrap, strtrim, strsplit, and n(z)char that account for ANSI CSI SGR control sequences.? ANSI CSI SGR control sequences [1] can be used to format text in terminals that support them. For example the control sequence "\033[31m" causes text that follows to render in red, and the control sequence

I have noticed anything using ANSI escape sequences to color text does not work if syslinux is in VESA mode. It only works if the \1#, \2#, or \3# are used. This means that libmenu which relies on csprint fails to render colors in VESA mode. I noticed the default color table has a complete table generated at runtime for all VGA color combinations, which csprint also does but from VGA attributes on

From: Randy Dunlap <randy.dunlap at oracle.com> Fix sparse warning for non-ANSI function declaration: arch/x86/xen/irq.c:129:30: warning: non-ANSI function declaration of function 'xen_init_irq_ops' Signed-off-by: Randy Dunlap <randy.dunlap at oracle.com> Cc: Jeremy Fitzhardinge <jeremy.fitzhardinge at citrix.com> --- arch/x86/xen/irq.c | 2 +- 1 file changed, 1

From: Randy Dunlap <randy.dunlap at oracle.com> Fix sparse warning for non-ANSI function declaration: arch/x86/xen/irq.c:129:30: warning: non-ANSI function declaration of function 'xen_init_irq_ops' Signed-off-by: Randy Dunlap <randy.dunlap at oracle.com> Cc: Jeremy Fitzhardinge <jeremy.fitzhardinge at citrix.com> --- arch/x86/xen/irq.c | 2 +- 1 file changed, 1

From: Randy Dunlap <randy.dunlap at oracle.com> Fix sparse warning for non-ANSI function declaration: arch/x86/xen/irq.c:129:30: warning: non-ANSI function declaration of function 'xen_init_irq_ops' Signed-off-by: Randy Dunlap <randy.dunlap at oracle.com> Cc: Jeremy Fitzhardinge <jeremy.fitzhardinge at citrix.com> --- arch/x86/xen/irq.c | 2 +- 1 file changed, 1

I ran across one file in the openbsd-compat directory, strmode.c, that was not using an ANSI C function declaration. One compiler (HPUX's cc -Ae) wouldn't let it pass. Here's a patch. - Dave Dykstra *** openbsd-compat/strmode.c.O Wed Jun 6 17:32:44 2001 --- openbsd-compat/strmode.c Wed Jun 6 17:32:59 2001 *************** *** 43,51 **** #include <string.h> void !