Re: wheezy and gcc 4.3 (and maybe 4.5)

2012-12-03 Thread dAgeCKo 

Le 02/12/2012 23:47, Jonathan Nieder a écrit :


That's binutils bug#620448.  If you put this script somewhere before
/usr/bin on your $PATH, make it executable, and name it as, that
should work around it.

#!/bin/sh
exec /usr/bin/as --size-check=warning $@

If you're using gcc 4.6, the changes from de2a8cf9 (e.g., grab it
using git cherry-pick de2a8cf9) and b1d670f10e80 are also needed.


Thanks a lot. I could finally find the commit which caused the 
regression I have:


b5153163ed580e00c67bdfecb02b2e3843817b3e

For interested people here is the page of the bug:

https://bugzilla.kernel.org/show_bug.cgi?id=47791

Thanks again for all people that helped me out. I will soon report 
another regression, I hope I'll be good enough now to avoid request any 
help :)



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/50bca9bd.8040...@free.fr

Re: wheezy and gcc 4.3 (and maybe 4.5)

2012-12-02 Thread Ben Hutchings 
[Moving this to the debian-kernel list.]

On Sun, 2012-12-02 at 13:00 +0100, dAgeCKo wrote:
 Hello,
 
 I have some kernel regressions with my hardware (usb and network). In 
 fact it is the first time I am doing stuffs for the linux kernel team.
 
 The thing is that the last known working kernel is a 2.6.32-46 and the 
 last known unworking kernel is a 3.2 (could be prior to this but 
 unsure). I am using git bisect to try to find where the problems are.
 
 Anyway, my problem is that I need some gcc versions that are no more 
 supported on wheezy. Indeed, the first kernel version I have to compile 
 is a 2.6.37, which, as far as I know, requires gcc 4.3.
 
 I tried to compile this kernel with gcc 4.4 but if failed. So I am 
 looking to install gcc 4.3 into my debian wheezy. Unfortunately, all my 
 attempts failed (too many broken dependencies).

Well, we have used gcc 4.4 for the official kernel packages since Linux
2.6.34.  So it should work.

 Maybe someone here can help me ?

You would have to install gcc-4.3 in a 'squeeze' environment, perhaps
using schroot or pbuilder or a virtual machine.

But you can also save some time by bisecting through the old packages at
http://snapshot.debian.org/package/linux/ and
http://snapshot.debian.org/package/linux-2.6/.

 Thanks in advance.
 
 PS: I hope I subscribed to the good mailing list, if not, please point 
 me to the good one.

debian-kernel is the specific list for our Linux kernel packages.

Ben.

-- 
Ben Hutchings
It is easier to change the specification to fit the program than vice versa.


signature.asc
Description: This is a digitally signed message part

Re: wheezy and gcc 4.3 (and maybe 4.5)

2012-12-02 Thread dAgeCKo 




Well, we have used gcc 4.4 for the official kernel packages since Linux
2.6.34.  So it should work.


Unfortunately, whether I use gcc 4.4 or another version, here is the 
error I have when compiling the kernel:


  CHK include/linux/version.h
  CHK include/generated/utsrelease.h
  CALLscripts/checksyscalls.sh
  CHK include/generated/compile.h
  AS  arch/x86/kernel/entry_64.o
/tmp/cc8aexwo.s: Assembler messages:
/tmp/cc8aexwo.s: Error: .size expression for do_hypervisor_callback does 
not evaluate to a constant

make[3]: *** [arch/x86/kernel/entry_64.o] Erreur 1

From what I could have understood on various internet pages, this is 
most certainly due to a wrong gcc version.
So whether I don't set the correct gcc version correctly (which can be 
possible), whether the error is somewhere else.

Here is what I do to set the correct gcc version:
export CC=gcc-4.4

Then I compile the kernel with this:

fakeroot make-kpkg --initrd --revision=1.0 kernel_image




Maybe someone here can help me ?


You would have to install gcc-4.3 in a 'squeeze' environment, perhaps
using schroot or pbuilder or a virtual machine.

But you can also save some time by bisecting through the old packages at
http://snapshot.debian.org/package/linux/  and
http://snapshot.debian.org/package/linux-2.6/.


I will have a look about these. It looks interesting.




Thanks in advance.

PS: I hope I subscribed to the good mailing list, if not, please point
me to the good one.


debian-kernel is the specific list for our Linux kernel packages.

Ben.




--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/50bb5186.5010...@free.fr

Re: wheezy and gcc 4.3 (and maybe 4.5)

2012-12-02 Thread Ben Hutchings 
On Sun, 2012-12-02 at 14:03 +0100, dAgeCKo wrote:
 
  Well, we have used gcc 4.4 for the official kernel packages since Linux
  2.6.34.  So it should work.
 
 Unfortunately, whether I use gcc 4.4 or another version, here is the 
 error I have when compiling the kernel:
 
CHK include/linux/version.h
CHK include/generated/utsrelease.h
CALLscripts/checksyscalls.sh
CHK include/generated/compile.h
AS  arch/x86/kernel/entry_64.o
 /tmp/cc8aexwo.s: Assembler messages:
 /tmp/cc8aexwo.s: Error: .size expression for do_hypervisor_callback does 
 not evaluate to a constant
 make[3]: *** [arch/x86/kernel/entry_64.o] Erreur 1
 
  From what I could have understood on various internet pages, this is 
 most certainly due to a wrong gcc version.
[...]

This is related to a binutils change, not gcc.  This particular instance
was fixed by:

commit 371c394af27ab7d1e58a66bc19d9f1f3ac1f67b4
Author: Alexander van Heukelum heuke...@fastmail.fm
Date:   Fri Mar 11 21:59:38 2011 +0100

x86, binutils, xen: Fix another wrong size directive

The commit message has further explanation of the general problem.

Ben.

-- 
Ben Hutchings
It is easier to change the specification to fit the program than vice versa.


signature.asc
Description: This is a digitally signed message part

Re: wheezy and gcc 4.3 (and maybe 4.5)

2012-12-02 Thread dAgeCKo 

Le 02/12/2012 14:20, Ben Hutchings a écrit :


This is related to a binutils change, not gcc.  This particular instance
was fixed by:


OK. I fixed it.

Now I am facing all the possible errors I could have. Thanks to internet 
I could solve some (see below), but then I am facing more errors:


Error #1:
gcc: error: unrecognized command line option '-m'
gcc: error: elf_x86_64: No such file or directory
  VDSOarch/x86/vdso/vdso32-int80.so.dbg
gcc: error: unrecognized command line option '-m'
gcc: error: elf_i386: No such file or directory
  VDSOarch/x86/vdso/vdso32-syscall.so.dbg
gcc: error: unrecognized command line option '-m'
gcc: error: elf_i386: No such file or directory
  VDSOarch/x86/vdso/vdso32-sysenter.so.dbg
gcc: error: unrecognized command line option '-m'
gcc: error: elf_i386: No such file or directory
  VDSOSYM arch/x86/vdso/vdso-syms.lds
nm: 'arch/x86/vdso/vdso.so.dbg': No such file
  VDSOSYM arch/x86/vdso/vdso32-int80-syms.lds
nm: 'arch/x86/vdso/vdso32-int80.so.dbg': No such file
  VDSOSYM arch/x86/vdso/vdso32-syscall-syms.lds
nm: 'arch/x86/vdso/vdso32-syscall.so.dbg': No such file
  VDSOSYM arch/x86/vdso/vdso32-sysenter-syms.lds
nm: 'arch/x86/vdso/vdso32-sysenter.so.dbg': No such file
  OBJCOPY arch/x86/vdso/vdso.so
objcopy: 'arch/x86/vdso/vdso.so.dbg': No such file

I was able to solve this one by modifying a Makefile.

Error #2:
In file included from drivers/net/igbvf/ethtool.c:36:0:
drivers/net/igbvf/igbvf.h:129:15: error: duplicate member 'page'

How can this one be solved ?

Note: With all the errors I am facing, I was wondering if I am really 
compiling kernels with gcc 4.4, so I modified the main Makefile so that 
the used compiler is really gcc-4.4 and I had the same results.



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/50bb92b9.7070...@free.fr

Re: wheezy and gcc 4.3 (and maybe 4.5)

2012-12-02 Thread Ben Hutchings 
On Sun, 2012-12-02 at 18:41 +0100, dAgeCKo wrote:
 Le 02/12/2012 14:20, Ben Hutchings a écrit :
 
  This is related to a binutils change, not gcc.  This particular instance
  was fixed by:
 
 OK. I fixed it.
 
 Now I am facing all the possible errors I could have. Thanks to internet 
 I could solve some (see below), but then I am facing more errors:
[...]
 Error #2:
 In file included from drivers/net/igbvf/ethtool.c:36:0:
 drivers/net/igbvf/igbvf.h:129:15: error: duplicate member 'page'
 
 How can this one be solved ?
[...]

It's a bug in the code.  Use 'git bisect skip' to select a different
place to test.

Ben.

-- 
Ben Hutchings
It is easier to change the specification to fit the program than vice versa.


signature.asc
Description: This is a digitally signed message part

Re: wheezy and gcc 4.3 (and maybe 4.5)

2012-12-02 Thread Jonathan Nieder 
Hi,

dAgeCKo wrote:

   AS  arch/x86/kernel/entry_64.o
 /tmp/cc8aexwo.s: Assembler messages:
 /tmp/cc8aexwo.s: Error: .size expression for do_hypervisor_callback does not 
 evaluate to a constant
 make[3]: *** [arch/x86/kernel/entry_64.o] Erreur 1

That's binutils bug#620448.  If you put this script somewhere before
/usr/bin on your $PATH, make it executable, and name it as, that
should work around it.

#!/bin/sh
exec /usr/bin/as --size-check=warning $@

If you're using gcc 4.6, the changes from de2a8cf9 (e.g., grab it
using git cherry-pick de2a8cf9) and b1d670f10e80 are also needed.

Thanks for your work,
Jonathan


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20121202224706.GA16601@elie.Belkin

Bug#598893: marked as done (linux-2.6 [m68k]: please work around gcc-4.3 ICE bug (37052))

2011-04-26 Thread Debian Bug Tracking System 
Your message dated Tue, 26 Apr 2011 10:57:42 + (UTC)
with message-id pine.bsm.4.64l.1104261057180.4...@herc.mirbsd.org
and subject line linux-2.6 [m68k]: please work around gcc-4.3 ICE bug (37052)
has caused the Debian Bug report #598893,
regarding linux-2.6 [m68k]: please work around gcc-4.3 ICE bug (37052)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
598893: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=598893
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: linux-2.6
Version: 2.6.32-24
Severity: wishlist
Tags: sid

Please see to that -fno-omit-frame-pointer is used during compilation
of a Debian m68k kernel as long as it is built with gcc-4.3 (I think
defining CONFIG_FRAME_POINTER should be enough, I have yet to build
any kernel at all though and have not tested this).

Details: http://wiki.debian.org/M68k/Gcc#iceinfindreloads

Triggered during btrfs compilation, out of all things…

-- System Information:
Debian Release: squeeze/sid
  APT prefers etch-m68k
..oO(why?)
  APT policy: (500, 'etch-m68k')
Architecture: m68k

Kernel: Linux 2.6.26-1-atari
Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/mksh-static


---End Message---
---BeginMessage---
src:linux-2.6 now uses gcc-4.4 so this is done.

---End Message---

Bug#598893: linux-2.6 [m68k]: please work around gcc-4.3 ICE bug (37052)

2010-10-06 Thread Bastian Blank 
On Sat, Oct 02, 2010 at 08:46:08PM +, Thorsten Glaser wrote:
 Please see to that -fno-omit-frame-pointer is used during compilation
 of a Debian m68k kernel as long as it is built with gcc-4.3 (I think
 defining CONFIG_FRAME_POINTER should be enough, I have yet to build
 any kernel at all though and have not tested this).

m68k is not a release architecture. Also all newer kernels uses gcc 4.4.

Bastian

-- 
Is truth not truth for all?
-- Natira, For the World is Hollow and I have Touched
   the Sky, stardate 5476.4.



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20101006112835.gb28...@wavehammer.waldi.eu.org

Bug#598893: linux-2.6 [m68k]: please work around gcc-4.3 ICE bug (37052)

2010-10-06 Thread Thorsten Glaser 
Bastian Blank dixit:

m68k is not a release architecture. Also all newer kernels uses gcc 4.4.

It doesn’t happen in gcc-4.4 but the kernel currently in sid uses gcc-4.3.

bye,
//mirabilos
-- 
I believe no one can invent an algorithm. One just happens to hit upon it
when God enlightens him. Or only God invents algorithms, we merely copy them.
If you don't believe in God, just consider God as Nature if you won't deny
existence.  -- Coywolf Qi Hunt



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/pine.bsm.4.64l.1010061625150.7...@herc.mirbsd.org

Bug#598893: linux-2.6 [m68k]: please work around gcc-4.3 ICE bug (37052)

2010-10-06 Thread Ben Hutchings 
On Wed, Oct 06, 2010 at 04:25:43PM +, Thorsten Glaser wrote:
 Bastian Blank dixit:
 
 m68k is not a release architecture. Also all newer kernels uses gcc 4.4.
 
 It doesn’t happen in gcc-4.4 but the kernel currently in sid uses gcc-4.3.
 
But we aren't going to release with m68k, so why not concentrate on
trunk/experimental?

Ben.

-- 
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
  - Albert Camus



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20101006182022.gt13...@decadent.org.uk

Bug#598893: linux-2.6 [m68k]: please work around gcc-4.3 ICE bug (37052)

2010-10-06 Thread Thorsten Glaser 
Ben Hutchings dixit:

On Wed, Oct 06, 2010 at 04:25:43PM +, Thorsten Glaser wrote:
 Bastian Blank dixit:
 
 m68k is not a release architecture. Also all newer kernels uses gcc 4.4.
 
 It doesnb 
But we aren't going to release with m68k, so why not concentrate on
trunk/experimental?

Makes sense, although I was trying to get something from unstable to
build, so that I could upload it to unstable (instead of unreleased)
on debian-ports.org (which has strict rules in that regard, and is
tightly coupled to Debian proper).

Except for the gcc-4.3 workaround, the issues I found both apply to
the experimental package too. Stephen Marenka, though, is working on
it (thanks).

bye,
//mirabilos
-- 
I believe no one can invent an algorithm. One just happens to hit upon it
when God enlightens him. Or only God invents algorithms, we merely copy them.
If you don't believe in God, just consider God as Nature if you won't deny
existence.  -- Coywolf Qi Hunt



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/pine.bsm.4.64l.1010061837080.11...@herc.mirbsd.org

Bug#598893: linux-2.6 [m68k]: please work around gcc-4.3 ICE bug (37052)

2010-10-03 Thread Thorsten Glaser 
Dixi quod…

Please see to that -fno-omit-frame-pointer is used during compilation
of a Debian m68k kernel as long as it is built with gcc-4.3 (I think
defining CONFIG_FRAME_POINTER should be enough, I have yet to build
any kernel at all though and have not tested this).

ARCH_WANT_FRAME_POINTERS might be needed as well.

I’m still building, ran into another error which will need a patch,
more on that later.

bye,
//mirabilos
-- 
I believe no one can invent an algorithm. One just happens to hit upon it
when God enlightens him. Or only God invents algorithms, we merely copy them.
If you don't believe in God, just consider God as Nature if you won't deny
existence.  -- Coywolf Qi Hunt



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/pine.bsm.4.64l.1010031616570.15...@herc.mirbsd.org

Bug#598893: linux-2.6 [m68k]: please work around gcc-4.3 ICE bug (37052)

2010-10-03 Thread Thorsten Glaser 
Dixi quod…

Please see to that -fno-omit-frame-pointer is used during compilation
of a Debian m68k kernel as long as it is built with gcc-4.3 (I think
defining CONFIG_FRAME_POINTER should be enough, I have yet to build
any kernel at all though and have not tested this).

ARCH_WANT_FRAME_POINTERS might be needed as well.

This part¹ of a debdiff did the trick for me:

diff -u linux-2.6-2.6.32/debian/config/m68k/config 
linux-2.6-2.6.32/debian/config/m68k/config
--- linux-2.6-2.6.32/debian/config/m68k/config
+++ linux-2.6-2.6.32/debian/config/m68k/config
@@ -312,0 +313,3 @@
+# Debian #598893
+CONFIG_ARCH_WANT_FRAME_POINTERS=y
+CONFIG_FRAME_POINTER=y

Corresponding changelog entry:

  [ Thorsten Glaser ]
  * debian/config/m68k/config: define CONFIG_ARCH_WANT_FRAME_POINTERS
and CONFIG_FRAME_POINTER to yes (Closes: #598893)

Note that this *only* applies to the sid kernel, as the experimental
kernel uses gcc-4.4 where I did not run into this problem last time.
(The current¹ problem however does apply to both sid and experimental.)


① as mentioned, I’m running into other issues; patches are being drafted
  and submitted, however, even emulated, m68k is slow so bear with me…

bye,
//mirabilos
-- 
Solange man keine schmutzigen Tricks macht, und ich meine *wirklich*
schmutzige Tricks, wie bei einer doppelt verketteten Liste beide
Pointer XORen und in nur einem Word speichern, funktioniert Boehm ganz
hervorragend.   -- Andreas Bogk über boehm-gc in d.a.s.r



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/pine.bsm.4.64l.1010031853200.15...@herc.mirbsd.org

Bug#598893: linux-2.6 [m68k]: please work around gcc-4.3 ICE bug (37052)

2010-10-02 Thread Thorsten Glaser 
Source: linux-2.6
Version: 2.6.32-24
Severity: wishlist
Tags: sid

Please see to that -fno-omit-frame-pointer is used during compilation
of a Debian m68k kernel as long as it is built with gcc-4.3 (I think
defining CONFIG_FRAME_POINTER should be enough, I have yet to build
any kernel at all though and have not tested this).

Details: http://wiki.debian.org/M68k/Gcc#iceinfindreloads

Triggered during btrfs compilation, out of all things…

-- System Information:
Debian Release: squeeze/sid
  APT prefers etch-m68k
..oO(why?)
  APT policy: (500, 'etch-m68k')
Architecture: m68k

Kernel: Linux 2.6.26-1-atari
Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/mksh-static



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20101002204608.8128.23263.report...@ara0.mirbsd.org

Bug#594289: linux-2.6: non-standard gcc/g++ used for build (gcc-4.3)

2010-08-25 Thread Matthias Klose 
Package: linux-2.6
Version: 2.6.32-20
Severity: normal
User: debian-...@lists.debian.org
Usertags: non-standard-compiler, gcc-4.3

This package builds with a non standard compiler version; please check
if this package can be built with the default version of gcc/g++.

Please keep this report open until the package uses the default
compiler version for the package build.

The severity of this report is likely to be raised before the release.




-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1oo90r-qu...@ravel.debian.org

Bug#594289: marked as done (linux-2.6: non-standard gcc/g++ used for build (gcc-4.3))

2010-08-25 Thread Debian Bug Tracking System 
Your message dated Wed, 25 Aug 2010 11:11:51 +0200
with message-id 20100825091150.gc6...@radis.liafa.jussieu.fr
and subject line Re: Bug#594289: linux-2.6: non-standard gcc/g++ used for build 
(gcc-4.3)
has caused the Debian Bug report #594289,
regarding linux-2.6: non-standard gcc/g++ used for build (gcc-4.3)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
594289: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594289
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 2.6.32-20
Severity: normal
User: debian-...@lists.debian.org
Usertags: non-standard-compiler, gcc-4.3

This package builds with a non standard compiler version; please check
if this package can be built with the default version of gcc/g++.

Please keep this report open until the package uses the default
compiler version for the package build.

The severity of this report is likely to be raised before the release.



---End Message---
---BeginMessage---
Version: 2.6.34-1~experimental.2

On Wed, Aug 25, 2010 at 05:59:05 +, Matthias Klose wrote:

 This package builds with a non standard compiler version; please check
 if this package can be built with the default version of gcc/g++.
 
 Please keep this report open until the package uses the default
 compiler version for the package build.
 
Closing as fixed in experimental:

linux-2.6 (2.6.34-1~experimental.2) experimental; urgency=low
[...]
  * Make gcc-4.4 the default compiler

I'm not sure it's safe to change it for 2.6.32.

Cheers,
Julien


signature.asc
Description: Digital signature
---End Message---

Bug#576477: closed by Ben Hutchings b...@decadent.org.uk (Re: Bug#576477: linux-headers-2.6.33-2-686: ..why in the world does it depend on gcc-4.3.*??? I wanna use gcc-4.5.*!)

2010-04-05 Thread Arnt Karlsen 
On Mon, 05 Apr 2010 03:03:10 +, Debian wrote in message 
handler.576477.d576477.127043640716078.notifd...@bugs.debian.org:

  ...why in the world does it depend on gcc-4.3.*???  I wanna use
  gcc-4.5.*!  
 
 We know which compiler versions the kernel works with.  You may
 override that if you want, but don't blame us if it breaks.

..well, that's why we call it experimental ;o), to find out 
_how_ it breaks, the idea was find bugs with gcc-4.5.* and 
gcc-4.4.*, so I should get to blame you when the darn thing 
even doesn't install. ;o)

..a fix would have the experimental stuff depend on 
gcc-4.3 || gcc-4.4 || gcc-4.5 etc as they appear.

-- 
..med vennlig hilsen = with Kind Regards from Arnt... ;o)
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100405122921.50895...@a45.fmb.no

Bug#576477: linux-headers-2.6.33-2-686: ..why in the world does it depend on gcc-4.3.*??? I wanna use gcc-4.5.*!

2010-04-04 Thread Arnt Karlsen 
Package: linux-headers-2.6.33-2-686
Version: 2.6.33-1~experimental.4
Severity: normal
Tags: squeeze experimental sid


...why in the world does it depend on gcc-4.3.*???  I wanna use gcc-4.5.*!


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.33-2-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100405004730.6612.98138.report...@a45.fmb.no

Bug#576477: marked as done (linux-headers-2.6.33-2-686: ..why in the world does it depend on gcc-4.3.*??? I wanna use gcc-4.5.*!)

2010-04-04 Thread Debian Bug Tracking System 
Your message dated Mon, 05 Apr 2010 03:59:51 +0100
with message-id 1270436391.5535.58.ca...@localhost
and subject line Re: Bug#576477: linux-headers-2.6.33-2-686: ..why in the world 
does it depend on gcc-4.3.*??? I wanna use gcc-4.5.*!
has caused the Debian Bug report #576477,
regarding linux-headers-2.6.33-2-686: ..why in the world does it depend on 
gcc-4.3.*??? I wanna use gcc-4.5.*!
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
576477: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576477
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-headers-2.6.33-2-686
Version: 2.6.33-1~experimental.4
Severity: normal
Tags: squeeze experimental sid


...why in the world does it depend on gcc-4.3.*???  I wanna use gcc-4.5.*!


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.33-2-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash


---End Message---
---BeginMessage---
On Mon, 2010-04-05 at 02:47 +0200, Arnt Karlsen wrote:
 Package: linux-headers-2.6.33-2-686
 Version: 2.6.33-1~experimental.4
 Severity: normal
 Tags: squeeze experimental sid
 
 
 ...why in the world does it depend on gcc-4.3.*???  I wanna use gcc-4.5.*!

We know which compiler versions the kernel works with.  You may override
that if you want, but don't blame us if it breaks.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


signature.asc
Description: This is a digitally signed message part
---End Message---

Bug#559069: linux-headers-2.6.26-2-amd64: why gcc-4.1 instead of gcc-4.3?

2009-12-01 Thread Mohan R 
Package: linux-headers-2.6.26-2-amd64
Severity: minor


Hi,

A newcommer to Debian, forgive me if I do any mistakes, I'm trying to
compile broadcom-sta following http://wiki.debian.org/wl wiki page.
While installing linux-headers-2.6.26-2-amd64, I noticed that it depends on
gcc-4.1, but when I installed 'gcc' package, aptitude installed 'gcc-4.3'.

Is gcc-4.1 desperately needed for this package? can't we change the dependency
to accept = gcc-4.1?

Thanks,
Mohan R.

-- System Information:
Debian Release: 5.0.3
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash



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

Bug#559069: linux-headers-2.6.26-2-amd64: why gcc-4.1 instead of gcc-4.3?

2009-12-01 Thread dann frazier 
On Tue, Dec 01, 2009 at 11:27:59PM +0530, Mohan R wrote:
 Package: linux-headers-2.6.26-2-amd64
 Severity: minor
 
 
 Hi,
 
 A newcommer to Debian, forgive me if I do any mistakes, I'm trying to
 compile broadcom-sta following http://wiki.debian.org/wl wiki page.
 While installing linux-headers-2.6.26-2-amd64, I noticed that it depends on
 gcc-4.1, but when I installed 'gcc' package, aptitude installed 'gcc-4.3'.

gcc-4.1 is provided in the gcc-4.1 package.

 Is gcc-4.1 desperately needed for this package?

I don't recall the details...

 can't we change the dependency to accept = gcc-4.1?

As far as Debian is concerned, its not a bug to use a compiler still
available in the distribution. It can be a wishlist bug if a package
doesn't work w/ a newer compiler, but it won't be a candidate for a
stable release.



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

Processed: Re: Bug#559069: linux-headers-2.6.26-2-amd64: why gcc-4.1 instead of gcc-4.3?

2009-12-01 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

 package linux-headers-2.6.26-2-amd64
Limiting to bugs with field 'package' containing at least one of 
'linux-headers-2.6.26-2-amd64'
Limit currently set to 'package':'linux-headers-2.6.26-2-amd64'

 severity 559069 wishlist
Bug #559069 [linux-headers-2.6.26-2-amd64] linux-headers-2.6.26-2-amd64: why 
gcc-4.1 instead of gcc-4.3?
Severity set to 'wishlist' from 'minor'

 thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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

Processed: Re: Bug#559069: linux-headers-2.6.26-2-amd64: why gcc-4.1 instead of gcc-4.3?

2009-12-01 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

 reassign 559069 linux-2.6
Bug #559069 [linux-headers-2.6.26-2-amd64] linux-headers-2.6.26-2-amd64: why 
gcc-4.1 instead of gcc-4.3?
Bug reassigned from package 'linux-headers-2.6.26-2-amd64' to 'linux-2.6'.
 thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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

Bug#559069: marked as done (linux-headers-2.6.26-2-amd64: why gcc-4.1 instead of gcc-4.3?)

2009-12-01 Thread Debian Bug Tracking System 
Your message dated Tue, 1 Dec 2009 23:26:21 -0700
with message-id 20091202062621.gc21...@lackof.org
and subject line fixed in 2.6.28-1
has caused the Debian Bug report #559069,
regarding linux-headers-2.6.26-2-amd64: why gcc-4.1 instead of gcc-4.3?
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
559069: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559069
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-headers-2.6.26-2-amd64
Severity: minor


Hi,

A newcommer to Debian, forgive me if I do any mistakes, I'm trying to
compile broadcom-sta following http://wiki.debian.org/wl wiki page.
While installing linux-headers-2.6.26-2-amd64, I noticed that it depends on
gcc-4.1, but when I installed 'gcc' package, aptitude installed 'gcc-4.3'.

Is gcc-4.1 desperately needed for this package? can't we change the dependency
to accept = gcc-4.1?

Thanks,
Mohan R.

-- System Information:
Debian Release: 5.0.3
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash


---End Message---
---BeginMessage---
Version: 2.6.28-1

---End Message---

Bug#559069: linux-headers-2.6.26-2-amd64: why gcc-4.1 instead of gcc-4.3?

2009-12-01 Thread Mohan R 

package linux-headers-2.6.26-2-amd64
severity 559069 wishlist
thanks

dann frazier wrote:

As far as Debian is concerned, its not a bug to use a compiler still
available in the distribution. It can be a wishlist bug if a package
doesn't work w/ a newer compiler, but it won't be a candidate for a
stable release.



I just concerned about the conflicts if I install two version of gcc.
Installing gcc-4.1(with its dependencies) just for linux-headers-2.6.26.2-amd64
package seems waste of bandwidth and storage. Because I already installed
'gcc-4.3' and its working smoothly.

Thanks,
Mohan R.



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

Bug#559069: linux-headers-2.6.26-2-amd64: why gcc-4.1 instead of gcc-4.3?

2009-12-01 Thread dann frazier 
reassign 559069 linux-2.6
thanks

On Wed, Dec 02, 2009 at 11:46:15AM +0530, Mohan R wrote:
 package linux-headers-2.6.26-2-amd64
 severity 559069 wishlist
 thanks

 dann frazier wrote:
 As far as Debian is concerned, its not a bug to use a compiler still
 available in the distribution. It can be a wishlist bug if a package
 doesn't work w/ a newer compiler, but it won't be a candidate for a
 stable release.


 I just concerned about the conflicts if I install two version of gcc.
 Installing gcc-4.1(with its dependencies) just for 
 linux-headers-2.6.26.2-amd64
 package seems waste of bandwidth and storage. Because I already installed
 'gcc-4.3' and its working smoothly.

Sorry, this won't happen in a stable release - saving space on a
development system isn't sufficient reason to break stable systems or
make kernel packages unbuildable.

-- 
dann frazier




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

Re: gcc 4.3

2008-06-12 Thread Frederik Schueler 

Hi!
On Tue, Jun 10, 2008 at 09:01:59AM +0200, Bastian Blank wrote:
 On Mon, Jun 09, 2008 at 11:51:28PM +0200, maximilian attems wrote:
  planing to switch x86 to it for 2.6.26.
  compiles, boots and works fine here.
 
 NACK. Too late.

I'd like to see this for amd64 too, but I guess we are indeed too late.

Are we really releasing with .26? 

Best regards
Frederik Schüler

-- 
ENOSIG


signature.asc
Description: Digital signature

Re: gcc 4.3

2008-06-10 Thread Bastian Blank 
On Mon, Jun 09, 2008 at 11:51:28PM +0200, maximilian attems wrote:
 planing to switch x86 to it for 2.6.26.
 compiles, boots and works fine here.

NACK. Too late.

Bastian

-- 
No problem is insoluble.
-- Dr. Janet Wallace, The Deadly Years, stardate 3479.4


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: gcc 4.3

2008-06-10 Thread Martin Michlmayr 
* maximilian attems [EMAIL PROTECTED] [2008-06-09 23:51]:
 planing to switch x86 to it for 2.6.26.
 compiles, boots and works fine here.
 
 please update other archs too for the default Lenny gcc.

IMHO there's too little time to proper test this major change.  You
often get obscure bugs when you move the kernel to a new GCC and given
where we are in our release process I'm not sure there's enough time
to find these problems.

If there are no objections, I'll leave arm and mips at gcc 4.1.
-- 
Martin Michlmayr
http://www.cyrius.com/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

gcc 4.3

2008-06-09 Thread maximilian attems 
planing to switch x86 to it for 2.6.26.
compiles, boots and works fine here.

please update other archs too for the default Lenny gcc.

thanks

-- 
maks


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#459767: linux-source-2.6.23: FTBFS with gcc-4.3

2008-05-27 Thread Didier Raboud 
Le mercredi 21 mai 2008 21:14:05 maximilian attems, vous avez écrit :
 Version: 2.6.25-1

 no longer the case and it even boots fine! :)

Hi,

Just wondering (as user)...

Isn't the gcc-4.3 mandatory for all packages in Lenny (so as well for the 
kernel) ? So why not enabling it per default as soon as possible (at least on 
arches where it builds...) ?

$ apt-cache showsrc linux-image-2.6.25-2-amd64 | grep gcc
Build-Depends: debhelper (= 4.1.0), module-init-tools, dpkg-dev (= 1.10.23), 
sparc-utils [sparc], kernel-package (= 10.063), python, gcc-4.1 [alpha amd64 
arm armel hppa i386 ia64 mips mipsel powerpc s390 sparc], binutils-hppa64 
[hppa], gcc-4.1-hppa64 [hppa], gcc-3.3 [m68k]
Build-Depends: debhelper (= 4.1.0), module-init-tools, dpkg-dev (= 1.10.23), 
sparc-utils [sparc], kernel-package (= 10.063), python, gcc-4.1 [alpha amd64 
arm armel hppa i386 ia64 mips mipsel powerpc s390 sparc], binutils-hppa64 
[hppa], gcc-4.1-hppa64 [hppa], gcc-3.3 [m68k]

Visibly, it is still gcc-4.1 for most of the architectures and event gcc-3.3 
for m68k.

Thanks for your time ! Regards, 

Didier Raboud


signature.asc
Description: This is a digitally signed message part.

Bug#459767: linux-source-2.6.23: FTBFS with gcc-4.3

2008-05-27 Thread maximilian attems 
On Tue, May 27, 2008 at 11:36:23PM +0200, Didier Raboud wrote:
 Le mercredi 21 mai 2008 21:14:05 maximilian attems, vous avez écrit :
  Version: 2.6.25-1
 
  no longer the case and it even boots fine! :)
 
 Hi,
 
 Just wondering (as user)...
 
 Isn't the gcc-4.3 mandatory for all packages in Lenny (so as well for the 
 kernel) ? So why not enabling it per default as soon as possible (at least on 
 arches where it builds...) ?

separate issue and tracked in a separted bug report will be fixed
for 2.6.26

-- 
maks



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#459767: marked as done (linux-source-2.6.23: FTBFS with gcc-4.3)

2008-05-21 Thread Debian Bug Tracking System 

Your message dated Wed, 21 May 2008 21:14:05 +0200
with message-id [EMAIL PROTECTED]
and subject line Re: linux-source-2.6.23: FTBFS with gcc-4.3
has caused the Debian Bug report #459767,
regarding linux-source-2.6.23: FTBFS with gcc-4.3
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
459767: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=459767
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
---BeginMessage---
Package: linux-source-2.6.23
Version: 2.6.23-3~snapshot.10051
Severity: normal


When compiling for Athlon using gcc-4.3:

gcc-4.3 --version
gcc-4.3 (Debian 4.3-20080104-1) 4.3.0 20080104 (experimental) [trunk 
revision 131316]

and make-kpkg --initrd linux-image modules-image

compilation proceeded fine up until:

  CC  arch/i386/lib/msr-on-cpu.o
  LD  arch/i386/lib/built-in.o
  CC  arch/i386/lib/bitops.o
  AS  arch/i386/lib/checksum.o
  CC  arch/i386/lib/delay.o
  AS  arch/i386/lib/getuser.o
  CC  arch/i386/lib/memcpy.o
  CC  arch/i386/lib/mmx.o
  AS  arch/i386/lib/putuser.o
  AS  arch/i386/lib/semaphore.o
  CC  arch/i386/lib/string.o
  CC  arch/i386/lib/strstr.o
  CC  arch/i386/lib/usercopy.o
  AR  arch/i386/lib/lib.a
  GEN .version
  CHK include/linux/compile.h
  UPD include/linux/compile.h
  CC  init/version.o
  LD  init/built-in.o
  LD  .tmp_vmlinux1
kernel/built-in.o: In function `getnstimeofday':
(.text+0x1d927): undefined reference to `__umoddi3'
kernel/built-in.o: In function `do_gettimeofday':
(.text+0x1d9e9): undefined reference to `__udivdi3'
kernel/built-in.o: In function `do_gettimeofday':
(.text+0x1da0c): undefined reference to `__umoddi3'
kernel/built-in.o: In function `timekeeping_resume':
timekeeping.c:(.text+0x1db18): undefined reference to `__udivdi3'
timekeeping.c:(.text+0x1db3b): undefined reference to `__umoddi3'
kernel/built-in.o: In function `update_wall_time':
(.text+0x1e214): undefined reference to `__udivdi3'
kernel/built-in.o: In function `update_wall_time':
(.text+0x1e237): undefined reference to `__umoddi3'
kernel/built-in.o: In function `update_wall_time':
(.text+0x1e2d3): undefined reference to `__udivdi3'
kernel/built-in.o: In function `update_wall_time':
(.text+0x1e2fd): undefined reference to `__umoddi3'
make[1]: *** [.tmp_vmlinux1] Error 1
make[1]: Leaving directory `/usr/src/linux-source-2.6.23'
make: *** [debian/stamp-build-kernel] Error 2


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.23 (SMP w/1 CPU core; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-source-2.6.23 depends on:
ii  binutils2.18.1~cvs20080103-1 The GNU assembler, linker and bina
ii  bzip2   1.0.4-2  high-quality block-sorting file co

Versions of packages linux-source-2.6.23 recommends:
ii  gcc   4:4.2.2-1  The GNU C compiler
ii  libc6-dev [libc-dev]  2.7-5  GNU C Library: Development Librari
ii  make  3.81-3 The GNU version of the make util

-- debconf-show failed


---End Message---
---BeginMessage---
Version: 2.6.25-1

no longer the case and it even boots fine! :)

-- 
maks

---End Message---

Bug#459767: [PATCH] linux-source-2.6.23: FTBFS with gcc-4.3

2008-04-09 Thread Bálint Réczey 
Hi,

The attached patch is a workaround for the build failure. It was cut
from 
http://cvs.fedora.redhat.com/viewcvs/*checkout*/devel/kernel/linux-2.6-compile-fix-gcc-43.patch?rev=1.3

It disables an optimization that triggers the linking problem.

For details, see:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32494

Regards,
Balint
--- linux-2.6.24.noarch.orig/include/linux/time.h
+++ linux-2.6.24.noarch/include/linux/time.h
@@ -169,7 +169,7 @@ extern struct timeval ns_to_timeval(cons
  * @a:		pointer to timespec to be incremented
  * @ns:		unsigned nanoseconds value to be added
  */
-static inline void timespec_add_ns(struct timespec *a, u64 ns)
+static inline void timespec_add_ns(struct timespec *a, volatile u64 ns)
 {
 	ns += a-tv_nsec;
 	while(unlikely(ns = NSEC_PER_SEC)) {

Bug#459767: linux-source-2.6.23: FTBFS with gcc-4.3

2008-03-05 Thread Christian Kujau 
Just for the record: gcc-4.3 still fails on a current vanilla kernel with 
the same message:


http://nerdbynature.de/bits/2.6.25-git/
(gcc 4.3-20080227-1 with today's 2.6.25-git)

Adding -fno-tree-scev-cprop to KBUILD_CFLAGS did not succeed, the build 
fails instantly, please see make_fno-tree-scev-cprop.log.


There are reports on the net to set CONFIG_GCC_4003_SUPPORT, however 
this option is not mainline (nor did I find any patches adding this 
option).


Thanks,
Christian.
--
BOFH excuse #269:

Melting hard drives


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Processed: Re: Bug#459767: linux-source-2.6.23: FTBFS with gcc-4.3

2008-03-05 Thread Debian Bug Tracking System 
Processing commands for [EMAIL PROTECTED]:

 reassign 459767 linux-2.6
Bug#459767: linux-source-2.6.23: FTBFS with gcc-4.3
Warning: Unknown package 'linux-source-2.6.23'
Bug reassigned from package `linux-source-2.6.23' to `linux-2.6'.

 --
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: gcc-4.3: Kernel build fails

2008-01-28 Thread Bastian Blank 
On Mon, Jan 28, 2008 at 03:46:23PM +0100, Matthias Klose wrote:
 these are defined in libgcc.a (linking with -static-libgcc should
 resolve these symbols).

No. libgcc is not compatible with the kernel ABI.

Bastian

-- 
The best diplomat I know is a fully activated phaser bank.
-- Scotty


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: gcc-4.3: Kernel build fails

2008-01-28 Thread Matthias Klose 
Jörg Sommer writes:
 Hi,
 
 I don't know if you are aware of this fact. Compiling the kernel release
 2.6.24 on PowerPC with gcc-4.3 fails.
 
   LD [M]  lib/zlib_inflate/zlib_inflate.o
   GEN .version
   CHK include/linux/compile.h
   UPD include/linux/compile.h
   CC  init/version.o
   LD  init/built-in.o
   LD  .tmp_vmlinux1
 kernel/built-in.o: In function `getnstimeofday':
 (.text+0x24988): undefined reference to `__umoddi3'
 kernel/built-in.o: In function `getnstimeofday':
 (.text+0x249a8): undefined reference to `__udivdi3'
 kernel/built-in.o: In function `do_gettimeofday':
 (.text+0x24b08): undefined reference to `__udivdi3'
 kernel/built-in.o: In function `do_gettimeofday':
 (.text+0x24b28): undefined reference to `__umoddi3'
 kernel/built-in.o: In function `timekeeping_resume':
 timekeeping.c:(.text+0x24e04): undefined reference to `__umoddi3'
 timekeeping.c:(.text+0x24e24): undefined reference to `__udivdi3'
 kernel/built-in.o: In function `update_wall_time':
 (.text+0x25374): undefined reference to `__umoddi3'
 kernel/built-in.o: In function `update_wall_time':
 (.text+0x25394): undefined reference to `__udivdi3'
 kernel/built-in.o: In function `update_wall_time':
 (.text+0x257f0): undefined reference to `__umoddi3'
 kernel/built-in.o: In function `update_wall_time':
 (.text+0x25810): undefined reference to `__udivdi3'
 make: *** [.tmp_vmlinux1] Fehler 1

these are defined in libgcc.a (linking with -static-libgcc should
resolve these symbols).

Bug#459767: linux-source-2.6.23: FTBFS with gcc-4.3

2008-01-09 Thread Arthur Marsh 



maximilian attems wrote, on 2008-01-09 06:32:


did you try 2.6.24-rc7 from trunk, see apt lines
- http://wiki.debian.org/DebianKernel



No. I am about to download it and try to compile it with gcc-4.3


please report back on it,
by default we currently use gcc-4.1


Same error:

  CC  lib/div64.o
  CC  lib/sort.o
  CC  lib/parser.o
  CC  lib/halfmd4.o
  CC  lib/debug_locks.o
  CC  lib/random32.o
  CC  lib/bust_spinlocks.o
  CC  lib/hexdump.o
  CC  lib/kasprintf.o
  CC  lib/bitmap.o
  CC  lib/iomap.o
  CC  lib/iomap_copy.o
  CC  lib/devres.o
  CC  lib/check_signature.o
  CC  lib/hweight.o
  CC  lib/kernel_lock.o
  CC  lib/plist.o
  CC  lib/smp_processor_id.o
  CC  lib/bitrev.o
  HOSTCC  lib/gen_crc32table
  GEN lib/crc32table.h
  CC  lib/crc32.o
  CC  lib/genalloc.o
  CC  lib/textsearch.o
  CC  lib/percpu_counter.o
  CC  lib/audit.o
  LD  lib/built-in.o
  CC  lib/argv_split.o
  CC  lib/bug.o
  CC  lib/cmdline.o
  CC  lib/cpumask.o
  CC  lib/ctype.o
  CC  lib/dec_and_lock.o
  CC  lib/dump_stack.o
  CC  lib/extable.o
  CC  lib/idr.o
  CC  lib/int_sqrt.o
  CC  lib/ioremap.o
  CC  lib/irq_regs.o
  CC  lib/klist.o
  CC  lib/kobject.o
  CC  lib/kobject_uevent.o
  CC  lib/kref.o
  CC  lib/prio_heap.o
  CC  lib/prio_tree.o
  CC  lib/proportions.o
  CC  lib/radix-tree.o
  CC  lib/rbtree.o
  CC  lib/reciprocal_div.o
  CC  lib/rwsem.o
  CC  lib/semaphore-sleepers.o
  CC  lib/sha1.o
  CC  lib/string.o
  CC  lib/vsprintf.o
  AR  lib/lib.a
  LD  lib/reed_solomon/built-in.o
  LD  lib/zlib_deflate/built-in.o
  LD  lib/zlib_inflate/built-in.o
  CC  arch/x86/lib/msr-on-cpu.o
  LD  arch/x86/lib/built-in.o
  CC  arch/x86/lib/bitops_32.o
  AS  arch/x86/lib/checksum_32.o
  CC  arch/x86/lib/delay_32.o
  AS  arch/x86/lib/getuser_32.o
  CC  arch/x86/lib/memcpy_32.o
  AS  arch/x86/lib/putuser_32.o
  AS  arch/x86/lib/semaphore_32.o
  CC  arch/x86/lib/string_32.o
  CC  arch/x86/lib/strstr_32.o
  CC  arch/x86/lib/usercopy_32.o
  AR  arch/x86/lib/lib.a
  GEN .version
  CHK include/linux/compile.h
  UPD include/linux/compile.h
  CC  init/version.o
  LD  init/built-in.o
  LD  .tmp_vmlinux1
kernel/built-in.o: In function `getnstimeofday':
(.text+0x1d9f9): undefined reference to `__umoddi3'
kernel/built-in.o: In function `do_gettimeofday':
(.text+0x1dab1): undefined reference to `__udivdi3'
kernel/built-in.o: In function `do_gettimeofday':
(.text+0x1dad4): undefined reference to `__umoddi3'
kernel/built-in.o: In function `timekeeping_resume':
timekeeping.c:(.text+0x1dbcc): undefined reference to `__udivdi3'
timekeeping.c:(.text+0x1dbef): undefined reference to `__umoddi3'
kernel/built-in.o: In function `update_wall_time':
(.text+0x1e2c8): undefined reference to `__udivdi3'
kernel/built-in.o: In function `update_wall_time':
(.text+0x1e2eb): undefined reference to `__umoddi3'
kernel/built-in.o: In function `update_wall_time':
(.text+0x1e387): undefined reference to `__udivdi3'
kernel/built-in.o: In function `update_wall_time':
(.text+0x1e3b1): undefined reference to `__umoddi3'
make[1]: *** [.tmp_vmlinux1] Error 1
make[1]: Leaving directory `/usr/src/linux-source-2.6.24-rc7'
make: *** [debian/stamp-build-kernel] Error 2




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#459767: linux-source-2.6.23: FTBFS with gcc-4.3

2008-01-09 Thread Bastian Blank 
On Wed, Jan 09, 2008 at 02:40:56AM +1030, Arthur Marsh wrote:
 When compiling for Athlon using gcc-4.3:
 
 gcc-4.3 --version
 gcc-4.3 (Debian 4.3-20080104-1) 4.3.0 20080104 (experimental) [trunk 
 revision 131316]

Does Linux upstream already bless gcc 4.3? I doubt.

 kernel/built-in.o: In function `getnstimeofday':
 (.text+0x1d927): undefined reference to `__umoddi3'
 kernel/built-in.o: In function `do_gettimeofday':
 (.text+0x1d9e9): undefined reference to `__udivdi3'
 kernel/built-in.o: In function `do_gettimeofday':
 (.text+0x1da0c): undefined reference to `__umoddi3'
 kernel/built-in.o: In function `timekeeping_resume':
 timekeeping.c:(.text+0x1db18): undefined reference to `__udivdi3'
 timekeeping.c:(.text+0x1db3b): undefined reference to `__umoddi3'
 kernel/built-in.o: In function `update_wall_time':
 (.text+0x1e214): undefined reference to `__udivdi3'
 kernel/built-in.o: In function `update_wall_time':
 (.text+0x1e237): undefined reference to `__umoddi3'
 kernel/built-in.o: In function `update_wall_time':
 (.text+0x1e2d3): undefined reference to `__udivdi3'
 kernel/built-in.o: In function `update_wall_time':
 (.text+0x1e2fd): undefined reference to `__umoddi3'

New references into libgcc, which is not available in the kernel.

__umoddi3: modulo operation on unsigned double wide integer or so, with
overflow checking.

Bastian

-- 
Leave bigotry in your quarters; there's no room for it on the bridge.
-- Kirk, Balance of Terror, stardate 1709.2

Bug#459767: linux-source-2.6.23: FTBFS with gcc-4.3

2008-01-09 Thread Arthur Marsh 



Bastian Blank wrote, on 09/01/08 21:32:

On Wed, Jan 09, 2008 at 02:40:56AM +1030, Arthur Marsh wrote:

When compiling for Athlon using gcc-4.3:

gcc-4.3 --version
gcc-4.3 (Debian 4.3-20080104-1) 4.3.0 20080104 (experimental) [trunk 
revision 131316]


Does Linux upstream already bless gcc 4.3? I doubt.


kernel/built-in.o: In function `getnstimeofday':
(.text+0x1d927): undefined reference to `__umoddi3'
kernel/built-in.o: In function `do_gettimeofday':
(.text+0x1d9e9): undefined reference to `__udivdi3'
kernel/built-in.o: In function `do_gettimeofday':
(.text+0x1da0c): undefined reference to `__umoddi3'
kernel/built-in.o: In function `timekeeping_resume':
timekeeping.c:(.text+0x1db18): undefined reference to `__udivdi3'
timekeeping.c:(.text+0x1db3b): undefined reference to `__umoddi3'
kernel/built-in.o: In function `update_wall_time':
(.text+0x1e214): undefined reference to `__udivdi3'
kernel/built-in.o: In function `update_wall_time':
(.text+0x1e237): undefined reference to `__umoddi3'
kernel/built-in.o: In function `update_wall_time':
(.text+0x1e2d3): undefined reference to `__udivdi3'
kernel/built-in.o: In function `update_wall_time':
(.text+0x1e2fd): undefined reference to `__umoddi3'


New references into libgcc, which is not available in the kernel.

__umoddi3: modulo operation on unsigned double wide integer or so, with
overflow checking.

Bastian


Would the workaround suggested at 
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32044#c28


You need to add -fno-tree-scev-cprop to the KBUILD_CFLAGS

work when applied the particular source files in the kernel where the 
error is occurring?


Arthur.



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#459767: linux-source-2.6.23: FTBFS with gcc-4.3

2008-01-08 Thread Arthur Marsh 
Package: linux-source-2.6.23
Version: 2.6.23-3~snapshot.10051
Severity: normal


When compiling for Athlon using gcc-4.3:

gcc-4.3 --version
gcc-4.3 (Debian 4.3-20080104-1) 4.3.0 20080104 (experimental) [trunk 
revision 131316]

and make-kpkg --initrd linux-image modules-image

compilation proceeded fine up until:

  CC  arch/i386/lib/msr-on-cpu.o
  LD  arch/i386/lib/built-in.o
  CC  arch/i386/lib/bitops.o
  AS  arch/i386/lib/checksum.o
  CC  arch/i386/lib/delay.o
  AS  arch/i386/lib/getuser.o
  CC  arch/i386/lib/memcpy.o
  CC  arch/i386/lib/mmx.o
  AS  arch/i386/lib/putuser.o
  AS  arch/i386/lib/semaphore.o
  CC  arch/i386/lib/string.o
  CC  arch/i386/lib/strstr.o
  CC  arch/i386/lib/usercopy.o
  AR  arch/i386/lib/lib.a
  GEN .version
  CHK include/linux/compile.h
  UPD include/linux/compile.h
  CC  init/version.o
  LD  init/built-in.o
  LD  .tmp_vmlinux1
kernel/built-in.o: In function `getnstimeofday':
(.text+0x1d927): undefined reference to `__umoddi3'
kernel/built-in.o: In function `do_gettimeofday':
(.text+0x1d9e9): undefined reference to `__udivdi3'
kernel/built-in.o: In function `do_gettimeofday':
(.text+0x1da0c): undefined reference to `__umoddi3'
kernel/built-in.o: In function `timekeeping_resume':
timekeeping.c:(.text+0x1db18): undefined reference to `__udivdi3'
timekeeping.c:(.text+0x1db3b): undefined reference to `__umoddi3'
kernel/built-in.o: In function `update_wall_time':
(.text+0x1e214): undefined reference to `__udivdi3'
kernel/built-in.o: In function `update_wall_time':
(.text+0x1e237): undefined reference to `__umoddi3'
kernel/built-in.o: In function `update_wall_time':
(.text+0x1e2d3): undefined reference to `__udivdi3'
kernel/built-in.o: In function `update_wall_time':
(.text+0x1e2fd): undefined reference to `__umoddi3'
make[1]: *** [.tmp_vmlinux1] Error 1
make[1]: Leaving directory `/usr/src/linux-source-2.6.23'
make: *** [debian/stamp-build-kernel] Error 2


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.23 (SMP w/1 CPU core; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-source-2.6.23 depends on:
ii  binutils2.18.1~cvs20080103-1 The GNU assembler, linker and bina
ii  bzip2   1.0.4-2  high-quality block-sorting file co

Versions of packages linux-source-2.6.23 recommends:
ii  gcc   4:4.2.2-1  The GNU C compiler
ii  libc6-dev [libc-dev]  2.7-5  GNU C Library: Development Librari
ii  make  3.81-3 The GNU version of the make util

-- debconf-show failed



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#459767: linux-source-2.6.23: FTBFS with gcc-4.3

2008-01-08 Thread Arthur Marsh 



maximilian attems wrote, on 2008-01-09 03:06:

On Wed, Jan 09, 2008 at 02:40:56AM +1030, Arthur Marsh wrote:

Package: linux-source-2.6.23
Version: 2.6.23-3~snapshot.10051
Severity: normal


grrr reportbug-ng misses quite a lot of important info,
thinking of automaticaly dropping such,
please use reportbug until reportbug-ng is fixed to use
the bug scripts.


Hi, I was using reportbug and have not installed reportbug-ng.



 

When compiling for Athlon using gcc-4.3:

gcc-4.3 --version
gcc-4.3 (Debian 4.3-20080104-1) 4.3.0 20080104 (experimental) [trunk 
revision 131316]


and make-kpkg --initrd linux-image modules-image

compilation proceeded fine up until:

  CC  arch/i386/lib/msr-on-cpu.o
  LD  arch/i386/lib/built-in.o
  CC  arch/i386/lib/bitops.o
  AS  arch/i386/lib/checksum.o
  CC  arch/i386/lib/delay.o
  AS  arch/i386/lib/getuser.o
  CC  arch/i386/lib/memcpy.o
  CC  arch/i386/lib/mmx.o
  AS  arch/i386/lib/putuser.o
  AS  arch/i386/lib/semaphore.o
  CC  arch/i386/lib/string.o
  CC  arch/i386/lib/strstr.o
  CC  arch/i386/lib/usercopy.o
  AR  arch/i386/lib/lib.a
  GEN .version
  CHK include/linux/compile.h
  UPD include/linux/compile.h
  CC  init/version.o
  LD  init/built-in.o
  LD  .tmp_vmlinux1
kernel/built-in.o: In function `getnstimeofday':
(.text+0x1d927): undefined reference to `__umoddi3'
kernel/built-in.o: In function `do_gettimeofday':
(.text+0x1d9e9): undefined reference to `__udivdi3'
kernel/built-in.o: In function `do_gettimeofday':
(.text+0x1da0c): undefined reference to `__umoddi3'
kernel/built-in.o: In function `timekeeping_resume':
timekeeping.c:(.text+0x1db18): undefined reference to `__udivdi3'
timekeeping.c:(.text+0x1db3b): undefined reference to `__umoddi3'
kernel/built-in.o: In function `update_wall_time':
(.text+0x1e214): undefined reference to `__udivdi3'
kernel/built-in.o: In function `update_wall_time':
(.text+0x1e237): undefined reference to `__umoddi3'
kernel/built-in.o: In function `update_wall_time':
(.text+0x1e2d3): undefined reference to `__udivdi3'
kernel/built-in.o: In function `update_wall_time':
(.text+0x1e2fd): undefined reference to `__umoddi3'
make[1]: *** [.tmp_vmlinux1] Error 1
make[1]: Leaving directory `/usr/src/linux-source-2.6.23'
make: *** [debian/stamp-build-kernel] Error 2


what arch, what .config?


i386 architecture and .config based on linux-image-2.6.23-1-686 with the 
following changes:


selected processor type to Athlon
set pre-emption model to low latency desktop
enabled pre-empting the big kernel lock
enabled default security capabilities as a module

The same error happened when the selected processor type was Pentium II 
(pre-coppermine).






did you try 2.6.24-rc7 from trunk, see apt lines
- http://wiki.debian.org/DebianKernel
 
 


No. I am about to download it and try to compile it with gcc-4.3

Regards,

Arthur.



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#459767: linux-source-2.6.23: FTBFS with gcc-4.3

2008-01-08 Thread maximilian attems 
On Wed, Jan 09, 2008 at 04:29:21AM +1030, Arthur Marsh wrote:
 selected processor type to Athlon
 set pre-emption model to low latency desktop
 enabled pre-empting the big kernel lock
 enabled default security capabilities as a module

the last choice is really b0rked.
 
 The same error happened when the selected processor type was Pentium II 
 (pre-coppermine).
 
 
 
 
 did you try 2.6.24-rc7 from trunk, see apt lines
 - http://wiki.debian.org/DebianKernel
  
  
 
 No. I am about to download it and try to compile it with gcc-4.3

please report back on it,
by default we currently use gcc-4.1

thanks

-- 
maks



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Processed: Re: Processed: Re: Bug#454875: FTBFS with GCC 4.3: missing #includes

2007-12-08 Thread Debian Bug Tracking System 
Processing commands for [EMAIL PROTECTED]:

 reassign 454914 shapetools
Bug#454914: OPEN_MAX macro removed from linux/limits.h on amd64
Bug reassigned from package `linux-libc-dev' to `shapetools'.

 forcemerge 454875 454914
Bug#454875: FTBFS with GCC 4.3: missing #includes
Bug#454914: OPEN_MAX macro removed from linux/limits.h on amd64
Forcibly Merged 454875 454914.

 thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Processed: Re: Bug#454875: FTBFS with GCC 4.3: missing #includes

2007-12-08 Thread Bastian Blank 
reassign 454914 shapetools
forcemerge 454875 454914
thanks

OPEN_MAX got removed from the headers because nothing in the kernel
respects this value any longer as it is a variable limit.

See commit 77293034696e3e0b6c8b8fc1f96be091104b3d2b for further
informations.

Bastian

-- 
There's coffee in that nebula!
-- Capt. Kathryn Janeway, Star Trek: Voyager, The Cloud


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Processed: Re: Bug#454875: FTBFS with GCC 4.3: missing #includes

2007-12-08 Thread Debian Bug Tracking System 
Processing commands for [EMAIL PROTECTED]:

 clone 454875 -1
Bug#454875: FTBFS with GCC 4.3: missing #includes
Bug 454875 cloned as bug 454914.

 reassign -1 linux-libc-dev
Bug#454914: FTBFS with GCC 4.3: missing #includes
Bug reassigned from package `shapetools' to `linux-libc-dev'.

 retitle -1 OPEN_MAX macro removed from linux/limits.h on amd64
Bug#454914: FTBFS with GCC 4.3: missing #includes
Changed Bug title to `OPEN_MAX macro removed from linux/limits.h on amd64' from 
`FTBFS with GCC 4.3: missing #includes'.

 thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]