Welcome to Al-Manahel Newsletter List

2006-02-19 Thread munir 

The subscription of the email address: 

[EMAIL PROTECTED]

To the mailing list: 

Al-Manahel Newsletter List

is all set. Thanks for subscribing! 

Date of this subscription: Sun Feb 19 08:47:25 2006

Please save this email message for future reference. 

---

You may automatically unsubscribe from this list at any time by 
visiting the following URL:



If the above URL is inoperable, make sure that you have copied the 
entire address. Some mail readers will wrap a long URL and thus break
this automatic unsubscribe mechanism. 

You may also change your subscription by visiting this list's main screen: 



If you're still having trouble, please contact the list owner at: 



The following physical address is associated with this mailing list: 



- 


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

Processed: Bug#348723: gcc-3.3 [powerpc] ICE in simplify_subeg, at simplify-rtx.c:2368

2006-02-19 Thread Debian Bug Tracking System 
Processing commands for [EMAIL PROTECTED]:

> tags 348723 + moreinfo
Bug#348723: gcc-3.3 [powerpc] ICE in simplify_subeg, at  simplify-rtx.c:2368
There were no tags set.
Tags added: moreinfo

> 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]

Bug#348723: gcc-3.3 [powerpc] ICE in simplify_subeg, at simplify-rtx.c:2368

2006-02-19 Thread Falk Hueffner 
tags 348723 + moreinfo
thanks

Hi,

gcc-3.3 isn't supported upstream anymore. Can you please test with gcc
3.4?

-- 
Falk


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

Bug#353618: [m68k] gcc-4.0 segfault building glibc

2006-02-19 Thread Aurelien Jarno 
Package: gcc-4.0
Version: 4.0.2-8
Severity: important

I am currently trying to build the glibc with gcc-4.0 instead of gcc-3.4
on all arches. On m68k, I get an ICE:

(unstable)[EMAIL PROTECTED]:~$ gcc-4.0 system.c -O -c -g -fomit-frame-pointer 
-o system.o
system.c: In function '__libc_system':
system.c:16: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See http://gcc.gnu.org/bugs.html> for instructions.
For Debian GNU/Linux specific bug reporting instructions,
see .
(unstable)[EMAIL PROTECTED]:~$

This is with a reduced testcase:

extern int __libc_multiple_threads __attribute__ ((visibility ("hidden")));

static int
do_system (const char *line)
{
  return 0;
}

int
__libc_system (const char *line)
{
  if (__builtin_expect (__libc_multiple_threads == 0, 1))
return do_system (line);

  return 0;
}

To reproduce the bug, you need to compile this code with:
-O (also with -O2 or -O3 on the original code, but not on the reduced
testcase probably because optimisation is easier on it)
AND
-g or -g2
AND
-fomit-frame-pointer



-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (100, 'unstable')
Architecture: m68k
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.4.31
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages gcc-4.0 depends on:
ii  binutils 2.16.1cvs20060117-1 The GNU assembler, linker and bina
ii  cpp-4.0  4.0.2-8 The GNU C preprocessor
ii  gcc-4.0-base 4.0.2-8 The GNU Compiler Collection (base 
ii  libc62.3.5-12.1  GNU C Library: Shared libraries an
ii  libgcc2  4.0.2-8 GCC support library

Versions of packages gcc-4.0 recommends:
ii  libc6-dev 2.3.5-12.1 GNU C Library: Development Librari
pn  libmudflap0-dev(no description available)

-- no debconf information


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

Bug#353618: [m68k] gcc-4.0 segfault building glibc

2006-02-19 Thread Matthias Klose 
Please recheck with a current gcc-4.1 from experimental.

Aurelien Jarno writes:
> Package: gcc-4.0
> Version: 4.0.2-8
> Severity: important
> 
> I am currently trying to build the glibc with gcc-4.0 instead of gcc-3.4
> on all arches. On m68k, I get an ICE:
> 
> (unstable)[EMAIL PROTECTED]:~$ gcc-4.0 system.c -O -c -g -fomit-frame-pointer 
> -o system.o
> system.c: In function '__libc_system':
> system.c:16: internal compiler error: Segmentation fault
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See http://gcc.gnu.org/bugs.html> for instructions.
> For Debian GNU/Linux specific bug reporting instructions,
> see .
> (unstable)[EMAIL PROTECTED]:~$
> 
> This is with a reduced testcase:
> 
> extern int __libc_multiple_threads __attribute__ ((visibility ("hidden")));
> 
> static int
> do_system (const char *line)
> {
>   return 0;
> }
> 
> int
> __libc_system (const char *line)
> {
>   if (__builtin_expect (__libc_multiple_threads == 0, 1))
> return do_system (line);
> 
>   return 0;
> }
> 
> To reproduce the bug, you need to compile this code with:
> -O (also with -O2 or -O3 on the original code, but not on the reduced
> testcase probably because optimisation is easier on it)
> AND
> -g or -g2
> AND
> -fomit-frame-pointer
> 
> 
> 
> -- System Information:
> Debian Release: testing/unstable
>   APT prefers unstable
>   APT policy: (100, 'unstable')
> Architecture: m68k
> Shell:  /bin/sh linked to /bin/bash
> Kernel: Linux 2.4.31
> Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
> 
> Versions of packages gcc-4.0 depends on:
> ii  binutils 2.16.1cvs20060117-1 The GNU assembler, linker and 
> bina
> ii  cpp-4.0  4.0.2-8 The GNU C preprocessor
> ii  gcc-4.0-base 4.0.2-8 The GNU Compiler Collection 
> (base 
> ii  libc62.3.5-12.1  GNU C Library: Shared libraries 
> an
> ii  libgcc2  4.0.2-8 GCC support library
> 
> Versions of packages gcc-4.0 recommends:
> ii  libc6-dev 2.3.5-12.1 GNU C Library: Development 
> Librari
> pn  libmudflap0-dev(no description available)
> 
> -- no debconf information
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]


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

Bug#353618: [m68k] gcc-4.0 segfault building glibc

2006-02-19 Thread Aurelien Jarno 

Matthias Klose a écrit :

Please recheck with a current gcc-4.1 from experimental.


I don't have and m68k machine, and I really doubt debian-admin would 
like to install experimental packages on crest.d.o. Therefore it would 
be nice if somebody who have a m68k machine (hence the Cc: to the m68k 
list) could do the test. Also gcc-4.0 4.0.2-8 is not the latest version 
(there is a 4.0.2-9), so could you please test with this version?


You will fine the testcase below.

Thanks
Aurelien



Aurelien Jarno writes:


Package: gcc-4.0
Version: 4.0.2-8
Severity: important

I am currently trying to build the glibc with gcc-4.0 instead of gcc-3.4
on all arches. On m68k, I get an ICE:

(unstable)[EMAIL PROTECTED]:~$ gcc-4.0 system.c -O -c -g -fomit-frame-pointer 
-o system.o
system.c: In function '__libc_system':
system.c:16: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See http://gcc.gnu.org/bugs.html> for instructions.
For Debian GNU/Linux specific bug reporting instructions,
see .
(unstable)[EMAIL PROTECTED]:~$

This is with a reduced testcase:

extern int __libc_multiple_threads __attribute__ ((visibility ("hidden")));

static int
do_system (const char *line)
{
 return 0;
}

int
__libc_system (const char *line)
{
 if (__builtin_expect (__libc_multiple_threads == 0, 1))
   return do_system (line);

 return 0;
}

To reproduce the bug, you need to compile this code with:
-O (also with -O2 or -O3 on the original code, but not on the reduced
testcase probably because optimisation is easier on it)
AND
-g or -g2
AND
-fomit-frame-pointer



-- System Information:
Debian Release: testing/unstable
 APT prefers unstable
 APT policy: (100, 'unstable')
Architecture: m68k
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.4.31
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages gcc-4.0 depends on:
ii  binutils 2.16.1cvs20060117-1 The GNU assembler, linker and bina
ii  cpp-4.0  4.0.2-8 The GNU C preprocessor
ii  gcc-4.0-base 4.0.2-8 The GNU Compiler Collection (base 
ii  libc62.3.5-12.1  GNU C Library: Shared libraries an

ii  libgcc2  4.0.2-8 GCC support library

Versions of packages gcc-4.0 recommends:
ii  libc6-dev 2.3.5-12.1 GNU C Library: Development Librari
pn  libmudflap0-dev(no description available)

-- no debconf information


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






--
  .''`.  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]

Moving 32-bit libraries to (/usr)/lib32 on amd64

2006-02-19 Thread Aurelien Jarno 
Hi all,

The amd64 port is currently providing 32-bit libraries via the ia32-libs
package. This package was originally designed for ia64, and thus install
32-bit libraries in /emul/ia32-linux/ . This is not compliant with the
FHS for amd64. Note also that this package does not rebuild the
libraries, but use the ones in the i386 packages.

As it has already been discussed with Steve Langasek on IRC (see
bug#274367 for a log), we should move those libraries to (/usr)/lib32.
This is still not FHS compliant, but a it is more "standard" library,
and it is the solution choosen by other distributions like Gentoo or
Ubuntu. I think we should also build them from the corresponding source
packages.

The first part of the transition need some coordination between a few
packages. The idea behing this transition, is that we keep libraries in
/emul/ia32-linux/ until they are transitioned. It is even possible to
keep two versions of the libraries (one in /usr/lib32, the other in
/emul/ia32-linux/) for a while to reduce the number of upload of
ia32-libs, which is quite a big package.

Here is my view on the transition:
1) Upload of glibc with 32-bit libraries
2) Upload of ia32-libs without the /usr/lib32 symlink, and without the
   glibc for amd64
3) Upload of zlib with 32-bit libraries in /usr/lib32 instead of
   /emul/ia32-linux/
4) Upload of gcc-4.0 with 32-bit libraries in /usr/lib32 instead of
   /emul/ia32-linux/

The order has been defined to reduce the number of uninstallable
packages on amd64. Only between step 1 and 2, the new packages
libc6-i386 and libc6-dev-i386 are uninstallable. It also permit to do
the transition without needing to bootstrap one or more packages, which
may be difficult on amd64, as only very few people have the rights to
upload packages.

I have already patches for all those packages, I have put them on
http://people.debian.org/~aurel32/amd64-lib32

Then it would be possible to transition the remaining packages, but no
more coordination is need.

I am waiting for you comments, especially if you think about something I
have forgotten, and also for the opinion of the release team.

Bye,
Aurelien

-- 
  .''`.  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]

Re: Moving 32-bit libraries to (/usr)/lib32 on amd64

2006-02-19 Thread Matthias Klose 
thanks!

Aurelien Jarno writes:
> Here is my view on the transition:
> 1) Upload of glibc with 32-bit libraries
> 2) Upload of ia32-libs without the /usr/lib32 symlink, and without the
>glibc for amd64
> 3) Upload of zlib with 32-bit libraries in /usr/lib32 instead of
>/emul/ia32-linux/
> 4) Upload of gcc-4.0 with 32-bit libraries in /usr/lib32 instead of
>/emul/ia32-linux/

gcc-3.4 and gcc-4.1 need to follow

> I have already patches for all those packages, I have put them on
> http://people.debian.org/~aurel32/amd64-lib32
> 
> Then it would be possible to transition the remaining packages, but no
> more coordination is need.
> 
> I am waiting for you comments, especially if you think about something I
> have forgotten, and also for the opinion of the release team.

integrated your patch, please check http://people.debian.org/~doko/gcc-4.0/

  Matthias


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