[EMAIL PROTECTED] a écrit :
---------- Initial header -----------

From      : "Aurelien Jarno" [EMAIL PROTECTED]
To          : "Aurelien Jarno" [EMAIL PROTECTED]
CC          : "Joel Soete" [EMAIL PROTECTED],"randolph"
[EMAIL PROTECTED],"doko" [EMAIL PROTECTED],"debian-gcc"
[email protected],"debian-hppa"
[email protected],"debian-release" [email protected]
Date      : Wed, 22 Feb 2006 11:48:25 +0100
Subject : Re: GCC 4.1 in experimental / GCC for etch


Aurelien Jarno a écrit :

Joel Soete a écrit :


Hello Aurelien,

Hi !


Did you read it:


<http://lists.parisc-linux.org/pipermail/parisc-linux/2005-December/027790.html>

This fix for me the pb when glibc was build with gcc-4.[01]


Thanks for the hint. However I have just build a new glibc with this patch, and I still have the same problem.


Oops, I am sorry, it works. I installed by error the new libc into / whereas I was running the testcase in the chroot. So the patch fixes the problem, thanks a lot for the hint.

I will add the patch to the SVN, and switch the compiler to gcc 4.0 on hppa.


Aurelien,

Good news ;-)

That said, I also figure out that this patch in fact modify an already
existing debian patch: glibc235-hppa-lt.diff.
May be using a new version of this would be more simple (e.g.
glibc235-hppa-lt-20050626.diff as the date of tausq's patch:
<http://cvs.parisc-linux.org/glibc/linuxthreads/sysdeps/unix/sysv/linux/hppa/sysdep-cancel.h?rev=1.4&view=log>

Thanks, I haven't remarked that. I will merge it.

That not yet all folks. More probably if you rebuild glibc with gcc-4 you
would also encounter ome inlining pb which seems fixed to me with following 
stuff:

What do you mean exactly by inlining problems? It builds fine here.


--
  .''`.  Aurelien Jarno             | GPG: 1024D/F1BCDB73
 : :' :  Debian developer           | Electrical Engineer
 `. `'   [EMAIL PROTECTED]         | [EMAIL PROTECTED]
   `-    people.debian.org/~aurel32 | www.aurel32.net


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

Reply via email to