Re: glibc_2.3.1-16_sparc64.changes ACCEPTED

2003-04-03 Thread GOTO Masanori
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,

Re: glibc_2.3.1-16_sparc64.changes ACCEPTED

2003-04-03 Thread Clint Adams
> 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.

Re: glibc_2.3.1-16_sparc64.changes ACCEPTED

2003-03-25 Thread GOTO Masanori
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-

Re: glibc_2.3.1-16_sparc64.changes ACCEPTED

2003-03-25 Thread Matthias Klose
James Troup writes: > Clint Adams <[EMAIL PROTECTED]> writes: > > > -MYCC = gcc-3.2 -m64 > > +MYCC = gcc-3.3 -m64 > > Don't forget a build-depends on gcc-3.3 if you do this... I would like to wait with the next upload until the current 3.2 packages move to testing, if this happens this week. Jus

Re: glibc_2.3.1-16_sparc64.changes ACCEPTED

2003-03-25 Thread James Troup
Clint Adams <[EMAIL PROTECTED]> writes: > -MYCC = gcc-3.2 -m64 > +MYCC = gcc-3.3 -m64 Don't forget a build-depends on gcc-3.3 if you do this... -- James

Re: glibc_2.3.1-16_sparc64.changes ACCEPTED

2003-03-25 Thread Clint Adams
> 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-sparc64 and libc6-dev-sparc64 just fine with the following patch