Hello!

( based on http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701315 )

I have searched the reason for problems with gcc 4.8. I have found that
the new gcc generates other header in some lilo files (first.s and
common.s). If I take back the changes because of gcc 4.8 in the two
(generated) files then lilo can be compiled without errors.

Unfortunately I have no plan how I can find a solution for this problem.
Perhaps this is a bug of gcc 4.8? Does anyone know a way of solution?


In detail this is the difference:

--- lilo-23.3_gcc47/first.s     2013-05-04 20:38:28.000000000 +0200
+++ lilo-23.3_gcc48/first.s     2013-05-04 20:36:28.000000000 +0200
@@ -1,6 +1,10 @@
 # 1 "first.S"
-# 1 "<built-in>"
 # 1 "<command-line>"
+# 1 "/usr/include/stdc-predef.h" 1 3 4
+# 30 "/usr/include/stdc-predef.h" 3 4
+# 1 "/usr/include/x86_64-linux-gnu/bits/predefs.h" 1 3 4
+# 31 "/usr/include/stdc-predef.h" 2 3 4
+# 1 "<command-line>" 2
 # 1 "first.S"
 ; first.S - 0xbb920890 first stage boot loader with LBA32 support
 ;
--- lilo-23.3_gcc47/common.s    2013-05-04 20:38:28.000000000 +0200
+++ lilo-23.3_gcc48/common.s    2013-05-04 20:50:25.000000000 +0200
@@ -1,6 +1,77 @@
 # 1 "common.h"
-# 1 "<built-in>"
 # 1 "<command-line>"
+
+# 1 "/usr/include/stdc-predef.h" 1 3 4
+/* Copyright (C) 1991-2012 Free Software Foundation, Inc.
+   This file is part of the GNU C Library.
+
+   The GNU C Library is free software; you can redistribute it and/or
+   modify it under the terms of the GNU Lesser General Public
+   License as published by the Free Software Foundation; either
+   version 2.1 of the License, or (at your option) any later version.
+
+   The GNU C Library 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
+   Lesser General Public License for more details.
+
+   You should have received a copy of the GNU Lesser General Public
+   License along with the GNU C Library; if not, see
+   <http://www.gnu.org/licenses/>.  */
+
+
+
+
+/* This header is separate from features.h so that the compiler can
+   include it implicitly at the start of every compilation.  It must
+   not itself include <features.h> or any other header that includes
+   <features.h> because the implicit include comes before any feature
+   test macros that may be defined in a source file before it first
+   explicitly includes a system header.  GCC knows the name of this
+   header in order to preinclude it.  */
+
+/* Define __STDC_IEC_559__ and other similar macros.  */
+
+# 1 "/usr/include/x86_64-linux-gnu/bits/predefs.h" 1 3 4
+/* Copyright (C) 2005 Free Software Foundation, Inc.
+   This file is part of the GNU C Library.
+
+   The GNU C Library is free software; you can redistribute it and/or
+   modify it under the terms of the GNU Lesser General Public
+   License as published by the Free Software Foundation; either
+   version 2.1 of the License, or (at your option) any later version.
+
+   The GNU C Library 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
+   Lesser General Public License for more details.
+
+   You should have received a copy of the GNU Lesser General Public
+   License along with the GNU C Library; if not, write to the Free
+   Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA
+   02111-1307 USA.  */
+
+
+
+
+
+
+
+
+/* We do support the IEC 559 math functionality, real and complex.  */
+
+
+
+# 31 "/usr/include/stdc-predef.h" 2 3 4
+
+/* wchar_t uses ISO/IEC 10646 (2nd ed., published 2011-03-15) /
+   Unicode 6.0.  */
+
+
+/* We do not support C11 <threads.h>.  */
+
+
+# 1 "<command-line>" 2
 # 1 "common.h"
 /* common.h  -  Common data structures and functions
  * 

---
Have a nice day.

Joachim (Germany)


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to