search for: __strict_ansi__

Displaying 9 results from an estimated 9 matches for "__strict_ansi__".

2009 Dec 30
7
DO NOT REPLY [Bug 7015] New: Build problems on HP-UX, Tru64 -- alloca, -Wno-unused-parameter
...t-in functio n 'alloca' Suggestion: dyi # gdiff -u ./popt/system.h_orig ./popt/system.h --- ./popt/system.h_orig 2006-11-08 20:37:38.000000000 -0600 +++ ./popt/system.h 2009-12-30 05:03:15.000000000 -0600 @@ -87,6 +87,8 @@ # endif #elif defined(__GNUC__) && defined(__STRICT_ANSI__) #define alloca __builtin_alloca +#elif HAVE_ALLOCA_H +# include <alloca.h> #endif #ifndef HAVE_STRLCPY Rationale: The use of GCC should not preclude the use of <alloca.h>. I haven't looked at what happens with __STRICT_ANSI__ defined, so even broader use of <alloca.h&g...
2016 Aug 01
4
OpenSSH 7.3p1 can't be build on Solaris 10
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 configure:17280: result: no configure:17300: checking for mblen configure:17356: gcc -o conftest -O3 -m64 -mtune=native -pipe -Wall -Wpointer-arith -Wuninitialized -Wsign-compare -Wformat-security -Wsizeof-pointer-memaccess -Wno-pointer-sign -Wno-unused-result -fno-strict-aliasing -D_FORTIFY_SOURCE=2 -ftrapv -fno-builtin-memset
2008 Oct 15
0
gccfss-4.2.0 fixincludes headers out of date, breaking dtrace SDT
...ll rights reserved. 9c18 &lt; #pragma ident "@(#)feature_tests.h 1.25 07/02/02 SMI" --- &gt; #pragma ident "@(#)feature_tests.h 1.24 04/09/28 SMI" 112c121 &lt; #if (__STDC__ - 0 == 1 && !defined(__GNUC__)) || \ --- &gt; #if ( defined(__STRICT_ANSI__) && !defined(__GNUC__)) || \ 365,370d373 &lt; /* &lt; * The following macro indicates header support for DTrace. The value is an &lt; * integer that corresponds to the major version number for DTrace. &lt; */ &lt; #define _DTRACE_VERSION 1 &lt; -- This message...
2005 Aug 04
9
wxruby2 retooling
I finally gave up on swig 1.3.22, since it seems to be causing too many problems. Ubuntu breezy will have 1.3.24, so I''m retargeting wxruby2 to swig 1.3.24+. At the moment, I have 1.3.25 on my system, since that''s the current release. I''m finding all kinds of problems with the post-processors we have that clean up the .cpp files that swig creates. The
2013 Jan 23
132
[PATCH 00/45] initial arm v8 (64-bit) support
First off, Apologies for the massive patch series... This series boots a 32-bit dom0 kernel to a command prompt on an ARMv8 (AArch64) model. The kernel is the same one as I am currently using with the 32 bit hypervisor I haven''t yet tried starting a guest or anything super advanced like that ;-). Also there is not real support for 64-bit domains at all, although in one or two places I
2013 Feb 22
48
[PATCH v3 00/46] initial arm v8 (64-bit) support
This round implements all of the review comments from V2 and all patches are now acked. Unless there are any objections I intend to apply later this morning. Ian.
2012 Apr 30
5
[PATCH 0/4 v1] Remove gettextify, implement OCaml gettext.
Version 1 of the patch, for discussion, but not to be applied. It does work, but needs a lot more testing. This removes all the psychopathic gettextify cruft, and replaces it with a 99 line Makefile.am. A large win, I think. The third patch implements gettext support in the OCaml tools. The fourth patch is just for illustration. It shows the consequent changes to libguestfs.pot and the po
2012 Jan 09
39
[PATCH v4 00/25] xen: ARMv7 with virtualization extensions
Hello everyone, this is the fourth version of the patch series that introduces ARMv7 with virtualization extensions support in Xen. The series allows Xen and Dom0 to boot on a Cortex-A15 based Versatile Express simulator. See the following announce email for more informations about what we are trying to achieve, as well as the original git history: See
2011 Dec 06
57
[PATCH RFC 00/25] xen: ARMv7 with virtualization extensions
Hello everyone, this is the very first version of the patch series that introduces ARMv7 with virtualization extensions support in Xen. The series allows Xen and Dom0 to boot on a Cortex-A15 based Versatile Express simulator. See the following announce email for more informations about what we are trying to achieve, as well as the original git history: See