Request 2536 (accepted)

Overview

Request 2536 (accepted)

- add missing patches to submit from 20160309

Created by jsjhb about 8 years ago
In state accepted
Package maintainers: manfred-h and sagiben

Submit kodi.binary-addons

Submit package home:jsjhb...ultimedia / kodi.binary-addons to package Multimedia / kodi.binary-addons

kodi.binary-addons-audiodecoder.ncsf-gcc5.3.patch Added

kodi.binary-addons-screensavers.rsxs-upstream-stdbool_h.patch Added

@@ -0,0 +1,160 @@
+--- stdbool.in.h	2015-09-07 08:01:54.000000000 +0200
++++ stdbool.in.h.gcc53	2016-03-09 15:03:29.036408581 +0100
+@@ -1,119 +1,54 @@
+-/* Copyright (C) 2001-2003, 2006-2008 Free Software Foundation, Inc.
+-   Written by Bruno Haible <haible@clisp.cons.org>, 2001.
++/* Copyright (C) 1998-2015 Free Software Foundation, Inc.
+ 
+-   This program is free software; you can redistribute it and/or modify
+-   it under the terms of the GNU General Public License as published by
+-   the Free Software Foundation; either version 3, or (at your option)
+-   any later version.
++This file is part of GCC.
+ 
+-   This program is distributed in the hope that it will be useful,
+-   but WITHOUT ANY WARRANTY; without even the implied warranty of
+-   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+-   GNU General Public License for more details.
++GCC is free software; you can redistribute it and/or modify
++it under the terms of the GNU General Public License as published by
++the Free Software Foundation; either version 3, or (at your option)
++any later version.
+ 
+-   You should have received a copy of the GNU General Public License
+-   along with this program; if not, write to the Free Software Foundation,
+-   Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.  */
++GCC is distributed in the hope that it will be useful,
++but WITHOUT ANY WARRANTY; without even the implied warranty of
++MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
++GNU General Public License for more details.
+ 
+-#ifndef _GL_STDBOOL_H
+-#define _GL_STDBOOL_H
++Under Section 7 of GPL version 3, you are granted additional
++permissions described in the GCC Runtime Library Exception, version
++3.1, as published by the Free Software Foundation.
+ 
+-/* ISO C 99 <stdbool.h> for platforms that lack it.  */
++You should have received a copy of the GNU General Public License and
++a copy of the GCC Runtime Library Exception along with this program;
++see the files COPYING3 and COPYING.RUNTIME respectively.  If not, see
++<http://www.gnu.org/licenses/>.  */
+ 
+-/* Usage suggestions:
++/*
++ * ISO C Standard:  7.16  Boolean type and values  <stdbool.h>
++ */
+ 
+-   Programs that use <stdbool.h> should be aware of some limitations
+-   and standards compliance issues.
++#ifndef _STDBOOL_H
++#define _STDBOOL_H
+ 
+-   Standards compliance:
++#ifndef __cplusplus
+ 
+-       - <stdbool.h> must be #included before 'bool', 'false', 'true'
+-         can be used.
++#define bool	_Bool
++#define true	1
++#define false	0
+ 
+-       - You cannot assume that sizeof (bool) == 1.
++#else /* __cplusplus */
+ 
+-       - Programs should not undefine the macros bool, true, and false,
+-         as C99 lists that as an "obsolescent feature".
++/* Supporting _Bool in C++ is a GCC extension.  */
++#define _Bool	bool
+ 
+-   Limitations of this substitute, when used in a C89 environment:
+-
+-       - <stdbool.h> must be #included before the '_Bool' type can be used.
+-
+-       - You cannot assume that _Bool is a typedef; it might be a macro.
+-
+-       - Bit-fields of type 'bool' are not supported.  Portable code
+-         should use 'unsigned int foo : 1;' rather than 'bool foo : 1;'.
+-
+-       - In C99, casts and automatic conversions to '_Bool' or 'bool' are
+-         performed in such a way that every nonzero value gets converted
+-         to 'true', and zero gets converted to 'false'.  This doesn't work
+-         with this substitute.  With this substitute, only the values 0 and 1
+-         give the expected result when converted to _Bool' or 'bool'.
+-
+-   Also, it is suggested that programs use 'bool' rather than '_Bool';
+-   this isn't required, but 'bool' is more common.  */
+-
+-
+-/* 7.16. Boolean type and values */
+-
+-/* BeOS <sys/socket.h> already #defines false 0, true 1.  We use the same
+-   definitions below, but temporarily we have to #undef them.  */
+-#if defined __BEOS__ && !defined __HAIKU__
+-# include <OS.h> /* defines bool but not _Bool */
+-# undef false
+-# undef true
++#if __cplusplus < 201103L
++/* Defining these macros in C++98 is a GCC extension.  */
++#define bool	bool
++#define false	false
++#define true	true
+ #endif
+ 
+-/* For the sake of symbolic names in gdb, we define true and false as
+-   enum constants, not only as macros.
+-   It is tempting to write
+-      typedef enum { false = 0, true = 1 } _Bool;
+-   so that gdb prints values of type 'bool' symbolically. But if we do
+-   this, values of type '_Bool' may promote to 'int' or 'unsigned int'
+-   (see ISO C 99 6.7.2.2.(4)); however, '_Bool' must promote to 'int'
+-   (see ISO C 99 6.3.1.1.(2)).  So we add a negative value to the
+-   enum; this ensures that '_Bool' promotes to 'int'.  */
+-#if defined __cplusplus || (defined __BEOS__ && !defined __HAIKU__)
+-  /* A compiler known to have 'bool'.  */
+-  /* If the compiler already has both 'bool' and '_Bool', we can assume they
+-     are the same types.  */
+-# if !@HAVE__BOOL@
+-typedef bool _Bool;
+-# endif
+-#else
+-# if !defined __GNUC__
+-   /* If @HAVE__BOOL@:
+-        Some HP-UX cc and AIX IBM C compiler versions have compiler bugs when
+-        the built-in _Bool type is used.  See
+-          http://gcc.gnu.org/ml/gcc-patches/2003-12/msg02303.html
+-          http://lists.gnu.org/archive/html/bug-coreutils/2005-11/msg00161.html
+-          http://lists.gnu.org/archive/html/bug-coreutils/2005-10/msg00086.html
+-        Similar bugs are likely with other compilers as well; this file
+-        wouldn't be used if <stdbool.h> was working.
+-        So we override the _Bool type.
+-      If !@HAVE__BOOL@:
+-        Need to define _Bool ourselves. As 'signed char' or as an enum type?
+-        Use of a typedef, with SunPRO C, leads to a stupid
+-          "warning: _Bool is a keyword in ISO C99".
+-        Use of an enum type, with IRIX cc, leads to a stupid
+-          "warning(1185): enumerated type mixed with another type".
+-        Even the existence of an enum type, without a typedef,
+-          "Invalid enumerator. (badenum)" with HP-UX cc on Tru64.
+-        The only benefit of the enum, debuggability, is not important
+-        with these compilers.  So use 'signed char' and no enum.  */
+-#  define _Bool signed char
+-# else
+-   /* With this compiler, trust the _Bool type if the compiler has it.  */
+-#  if !@HAVE__BOOL@
+-typedef enum { _Bool_must_promote_to_int = -1, false = 0, true = 1 } _Bool;
+-#  endif
+-# endif
+-#endif
+-#define bool _Bool
++#endif /* __cplusplus */
+ 
+-/* The other macros must be usable in preprocessor directives.  */
+-#define false 0
+-#define true 1
+-#define __bool_true_false_are_defined 1
++/* Signal that all the definitions are present.  */
++#define __bool_true_false_are_defined	1
+ 
+-#endif /* _GL_STDBOOL_H */
++#endif	/* stdbool.h */

Build Results
RPM Lint

Refresh

Comments for request 2536 0

Request History

jsjhb created request about 8 years ago

- add missing patches to submit from 20160309

jsjhb accepted request about 8 years ago

accept now, and wait for submit of libhdhomerun to succeed this build