At Mon, 19 Sep 2005 19:27:15 +0200,
Matthias Klose wrote:
> > On the latest i386 Sid, gcc-4.0 does not build from source, on my machine,
> > and on a buildd (see the logs). With dash as sh, I get:
>
> this is known, we're waiting on proper 64bit support from glibc. I'd
> like to downgrade this one
At Sat, 13 Aug 2005 08:25:32 +0200,
Andreas Jochens wrote:
> Will the separation character problem (',' vs. '|') in the glibc
> Build-Depends also be fixed?
OK, fixed in cvs. Thanks.
Regards,
-- gotom
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Con
nstall such libraries packages manually.
At Thu, 14 Jul 2005 15:26:58 +0900,
GOTO Masanori wrote:
> At Tue, 12 Jul 2005 19:44:11 +0200,
> Matthias Klose wrote:
> > GOTO Masanori writes:
> > > At Tue, 05 Jul 2005 20:09:59 -0700,
> > > Ryan Murray wrote:
> > >
At Thu, 21 Jul 2005 10:33:22 +0200,
Matthias Klose wrote:
> GOTO Masanori writes:
> > At Thu, 21 Jul 2005 13:11:05 +0900,
> > GOTO Masanori wrote:
> > > The current gcc-4.0 can't compile the experimental glibc 2.3.5-2 with
> > > unstable gcc-4.0 (4.0.1
At Thu, 21 Jul 2005 13:11:05 +0900,
GOTO Masanori wrote:
> The current gcc-4.0 can't compile the experimental glibc 2.3.5-2 with
> unstable gcc-4.0 (4.0.1-2) on m68k, due to gcc-4.0's Internal Compiler
> Error. Note that this problem was not occured with gcc-3.4 (3.4.4-5)
>
Package: gcc-4.0
Version: 4.0.1-2
Severity: important
The current gcc-4.0 can't compile the experimental glibc 2.3.5-2 with
unstable gcc-4.0 (4.0.1-2) on m68k, due to gcc-4.0's Internal Compiler
Error. Note that this problem was not occured with gcc-3.4 (3.4.4-5)
with -O1/-O2/-O3.
gcc-4.0 with -
At Tue, 12 Jul 2005 19:44:11 +0200,
Matthias Klose wrote:
> GOTO Masanori writes:
> > At Tue, 05 Jul 2005 20:09:59 -0700,
> > Ryan Murray wrote:
> > > libc6-s390x is missing a depends on lib64gcc1 that causes gcc to fail to
> > > link
> > > when -m64
At Tue, 05 Jul 2005 20:09:59 -0700,
Ryan Murray wrote:
> libc6-s390x is missing a depends on lib64gcc1 that causes gcc to fail to link
> when -m64 is used on an s390 system.
>
> I'm filling the bug here rather than on the gcc-VERSION packages because the
> sparc64 packages have the dependency in li
At Thu, 14 Apr 2005 10:24:01 +0200,
Matthias Klose wrote:
> - The rules outlined above should make the autobuilders build your
> packages with GCC 4.0.
>
> TODO: check for other incompatibilities for non-release
> architectures,
>
> * i.e. sparc and hppa. I.e.: hppa libgcc1 (SJLJ) -> libg
At Sun, 3 Apr 2005 17:11:02 +0200,
Matthias Klose wrote:
> Please recheck with gcc-4.0.
Yes, I confirmed it's fixed in gcc-4.0 - do you have plan to fix it
for gcc-3.3 or gcc-3.4?
Regards,
-- gotom
> GOTO Masanori writes:
> > Package: gcc-3.3
> > Version: 1:3.3.5
tags 295457 fixed-upstream
thanks
> /usr/include/pthread.h line 654-655 say:
> struct __jmp_buf_tag;
> extern int __sigsetjmp (struct __jmp_buf_tag __env[1], int __savemask)
> __THROW;
Note that in 2.3.4 it's changed as follows:
/* Function used in the macros. */
struct __jmp_buf_tag;
extern i
Package: gcc-3.3
Version: 1:3.3.5-8
Severity: normal
Debian gcc-3.3 and gcc-3.4 (Version: 3.4.3-9) on arm cannot compile
the following code derived from glibc 2.3.4 with -O option:
double
__fmax (double x, double y)
{
return (__builtin_isgreaterequal(x, y) || (s
At Sun, 12 Dec 2004 17:55:57 +0100,
Matthias Klose wrote:
> with the patch attached and an updated gcc-3.3 package, libunwind
> support for ia64 seems to work for me. I couldn't install any of the
> built packages. I'd like to ask people to install the test builds
> found at
>
> http://peopl
> Package: gcc
> Version: 2.7.2.3-4.7
> Severity: wishlist
>
> merry$ gcc -Wall -Werror -Wmissing-prototypes -g -O2 -I. -DSTDC_HEADERS=1
> -DHAVE_STRDUP=1 -DHAVE_STRERROR=1 Test.c -o Test
> cc1: /tmp/ccb04872: I/O error
>
> This happened repeatedly when /tmp filled up during compilation (Test.c
At Mon, 28 Jun 2004 10:39:08 +0200,
Jeroen van Wolffelaar wrote:
> On Mon, Jun 28, 2004 at 10:18:08AM +0900, GOTO Masanori wrote:
> > At Sun, 27 Jun 2004 09:24:36 +0200,
> > Matthias Klose wrote:
> > > The bug submitter claims that a missing /proc leads to ICE's in gc
At Sun, 27 Jun 2004 09:24:36 +0200,
Matthias Klose wrote:
> The bug submitter claims that a missing /proc leads to ICE's in gcc
> and thinks this might be a bug in glibc or gcc. Any ideas? I'm unable
> to reproduce this one.
strace give us some more hints.
BTW, why did Jeroen use 2.6.3? AFAIK som
Hi Matthias,
At Sat, 3 Apr 2004 08:23:44 +0200,
Matthias Klose wrote:
> This patch applied upstream
> http://sources.redhat.com/ml/libc-hacker/2003-12/msg00025.html
> is supposed to fix about 900 test failures in the libjava testsuite in
> gcc-3.4. Note that I didn't test the patch myself.
>
>
At Fri, 30 Apr 2004 21:55:48 +0200,
Matthias Klose wrote:
> In the release notes, alpha mips and sparc are listed to have
> changes in the binary ABI, maybe only corner cases.
Yeah, reading through the release notes, it seems there're a bunch of
modifications.
> There are currently too many unkno
severity 224593 grave
thanks
At Sat, 20 Dec 2003 12:51:50 +0100,
Antoine Sirinelli wrote:
> Package: gcc-3.3
> Version: 1:3.3.3-0pre0
> Severity: normal
> Tags: patch sid
>
> I cannot compile a program using xmmintrin.h because the file
> emmintrin.h is not present on my system. I applied this pa
At Thu, 18 Dec 2003 13:11:43 +,
Matthew Wilcox wrote:
> On Wed, Dec 17, 2003 at 09:03:16PM -0500, Nathanael Nerode wrote:
> > Matthias Klose wrote:
> > >gcc-3.3 is configured with --enable-sjlj-exceptions (done to keep
> > >compatibility with gcc-3.2). I don't know if the dwarf2 unwinder will
>
severity 211610 wishlist
reassign 211610 glibc
thanks
At Thu, 18 Sep 2003 18:17:42 -0500,
Andrés Roldán wrote:
> When trying to executing a binary with the __thread keywork, the program
> segfaults. Below is the output.
>
> [pts/0]
> [EMAIL PROTECTED]:~$ cat tls.c
> __thread int a;
>
> int
> ma
At 08 Aug 2003 13:40:42 +0100,
Philip Blundell wrote:
> On Fri, 2003-08-08 at 13:35, GOTO Masanori wrote:
> > So how to act for two bugs?:
> >
> > #203322: python2.2: Python fails with illegal instruction during
> > postinst on sparc32
> > #203324: li
At Thu, 7 Aug 2003 07:33:09 +0200,
Jan-Benedict Glaw wrote:
>
> [1 ]
> On Wed, 2003-08-06 17:22:19 -0400, Ben Collins <[EMAIL PROTECTED]>
> wrote in message <[EMAIL PROTECTED]>:
> > On Wed, Aug 06, 2003 at 11:08:22PM +0200, Matthias Klose wrote:
> > > Jan-Benedict Glaw writes:
> >
> > Someone is
At Thu, 15 May 2003 16:33:10 -0500,
Debian Bug Tracking System wrote:
> > reassign 25824 glibc
> Bug#25824: [PR other/6903] gcc could give better error message when /tmp gets
> full
> Bug reassigned from package `gcc' to `glibc'.
I don't understand why this bug is assigned to glibc. Please expla
At Sun, 20 Apr 2003 18:45:15 -0700,
Jeff Bailey wrote:
>
> On Sun, Apr 20, 2003 at 12:51:43PM -0400, Jack Howarth wrote:
>
> >I am wondering if there is a gameplan on adding the support for
> > enabling TLS support in the devtools in sid. In particular, in trying
> > to build the current debi
At Thu, 3 Apr 2003 17:30:32 -0500,
Clint Adams wrote:
> > issue. If gcc 3.3 will be back to -m64 aware, we re-enable these
> > configurations. Do you know the status of gcc-3.3 which is ready for
> > -m64?
>
> gcc-3.3 3.3-0pre3, currently in sid, builds -m64 binaries that work.
Excellent. OK,
At Tue, 25 Mar 2003 13:48:35 -0500,
Clint Adams wrote:
> > That's right. If new gcc package has ability to handle sparc64 -m64
> > (currently both gcc-3.3 and gcc-snapshot have not come), it should be
> > duploaded with appropriate changes for glibc source package.
>
> glibc_2.3.2-1 builds libc6-
At Thu, 6 Mar 2003 15:06:59 +0100,
Martin Loschwitz wrote:
> while doing the usual test builds with a new Qt version, i noticed a very
> weird problem while compiling kopete.
Which package is kopete existed?
> Have a look at the command and the error message:
>
> /usr/share/qt3/bin/uic -L /usr/l
At Mon, 17 Feb 2003 11:12:11 -0500,
Daniel Jacobowitz wrote:
> On Mon, Feb 17, 2003 at 10:58:21PM +0900, GOTO Masanori wrote:
> > Hi Guido,
> > Thanks for your explanation.
> >
> > At Sun, 16 Feb 2003 23:32:42 +0100,
> > Guido Guenther wrote:
> > > I&
Hi Guido!
At Mon, 17 Feb 2003 15:27:05 +0100,
Guido Guenther wrote:
> On Mon, Feb 17, 2003 at 10:58:21PM +0900, GOTO Masanori wrote:
> [..snip..]
> > > /usr/bin/nm __udivdi3
> > > /usr/bin/nm __umoddi3
> > > /usr/bin/strip __ucmpdi2
> > > /usr/bin/
Hi Guido,
Thanks for your explanation.
At Sun, 16 Feb 2003 23:32:42 +0100,
Guido Guenther wrote:
> I'm trying to explain how I understand these issues, but it might not be
> correct:
>
> On Mon, Feb 17, 2003 at 12:49:44AM +0900, GOTO Masanori wrote:
> > 1. Why is __fixu
At Thu, 13 Feb 2003 13:43:24 -0800,
Ryan Murray wrote:
> [1 ]
> On Fri, Feb 14, 2003 at 02:10:59AM +0900, GOTO Masanori wrote:
> > At Thu, 13 Feb 2003 08:48:14 -0600,
> > Debian Bug Tracking System wrote:
> > > Processing commands for [EMAIL PROTECTED]:
> >
At Thu, 13 Feb 2003 08:48:14 -0600,
Debian Bug Tracking System wrote:
> Processing commands for [EMAIL PROTECTED]:
>
> > reassign 179781 glibc
> Bug#179781: dcgui: relocation error: /usr/bin/dcgui: undefined symbol:
> __fixunsdfdi
> Bug#180330: libc6, relocation error (dcgui)
> Bug reassigned fro
reassign 175526 gcc-3.2
thanks
m68k gcc-3.2 is under building by me, and it's gcc bug, not glibc.
I reassign this bug from glibc to gcc-3.2.
-- gotom
At Mon, 27 Jan 2003 11:39:43 -0500 (EST),
Alan Cox wrote:
> > >GCC 3.2 still uses CMOVE instructions on -march=i686.
> > >
> > >On the other hand:
> > > {"c3", PROCESSOR_I486, PTA_MMX | PTA_3DNOW},
> > >GCC disagrees with you that the C3 is an i686.
>
> gcc uses i486 schedu
At Tue, 21 Jan 2003 23:35:07 +0100,
>
> GOTO Masanori writes:
> > > On Sun, Jan 19, 2003 at 07:48:04PM -0800, Jeff Bailey wrote:
> > > > I haven't seen mention of it on this list, so I wanted to bring it up -
> > > > Bug #175526 against glibc is m68
At Wed, 22 Jan 2003 19:04:07 +0100,
Richard Zidlicky wrote:
> On Wed, Jan 22, 2003 at 06:43:55AM +0900, GOTO Masanori wrote:
> > > On Sun, Jan 19, 2003 at 07:48:04PM -0800, Jeff Bailey wrote:
> > > > I haven't seen mention of it on this list, so I wanted to brin
> On Sun, Jan 19, 2003 at 07:48:04PM -0800, Jeff Bailey wrote:
> > I haven't seen mention of it on this list, so I wanted to bring it up -
> > Bug #175526 against glibc is m68k specific.
>
> interesting. I am running glibc-2.3 and gcc-3.2 without much problems
> here, will look if I can see som
Hi Jeff,
At Thu, 16 Jan 2003 18:14:30 -0800,
Jeff Bailey wrote:
> On Fri, Jan 17, 2003 at 09:39:44AM +0900, GOTO Masanori wrote:
>
> > We debian-glibc team plan to prepare cmov-aware libc6.
>
> Sorry I havent been around much, been busy with school. Does this mean
> we
At 16 Jan 2003 18:38:07 +,
Philip Blundell wrote:
> So, per our IRC discussion this afternoon, I think the current plan for
> this is to have ld.so treat CMOV as an optional extension, similar to
> how MMX is handled. In other words:
>
> - Add CMOV to HWCAP_IMPORTANT in glibc.
>
> - Ask th
0PM +, David Goodenough wrote:
> > >>>On Tuesday 05 November 2002 13:04, Christoph Martin wrote:
> > >>>>Am Die, 2002-11-05 um 01.34 schrieb GOTO Masanori:
> > >>>>>At Mon, 4 Nov 2002 11:07:56 +0100,
> > >>>>>
> > >>&g
At Wed, 21 Aug 2002 01:40:54 -0400 (EDT),
Jack Howarth wrote:
>The revised gcc-3.2-compatible sysdeps/powerpc/libgcc-compat.S code
> is now checked into glibc-2-2-branch. I have built both the straight
> glibc-2-2-branch checkout as well as debian glibc packages based off
> of the 2.2.5-14 sour
--no-backup-if-mismatch -R -p0 < $0;;
*)
echo >&2 "`basename $0`: script expects -patch|-unpatch as argument"
exit 1
esac
exit 0
2002-01-20 GOTO Masanori <[EMAIL PROTECTED]>
* cccp.c: avoid setlocale(LC_MESSAGES, ...) if MULTIBYTE_CHARS is not
s
Hi,
At Tue, 15 Jan 2002 01:58:36 +0100,
Matthias Klose <[EMAIL PROTECTED]> wrote:
> > Note that this problem is fixed in gcc-3.0 but I think
> > gcc-2.95 is important because it is the main C compiler
> > for Woody.
>
> How many translations are there available for gcc-2.95? Please send a
> patch
At Tue, 15 Jan 2002 02:12:52 +0100,
Martin v. Loewis <[EMAIL PROTECTED]> wrote:
>
> > Since we will have to prepare Woody's release soon, I think
> > the best way is to disable translation just now tempolarily
> > and then start the investigation of this problem.
>
> I recommend the same thing. G
45 matches
Mail list logo
