This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: End of GCC 4.6 Stage 1: October 27, 2010
- From: Dave Korn <dave dot korn dot cygwin at gmail dot com>
- To: NightStrike <nightstrike at gmail dot com>
- Cc: Jonathan Wakely <jwakely dot gcc at gmail dot com>, Andrew Haley <aph at redhat dot com>, Richard Guenther <richard dot guenther at gmail dot com>, Richard Guenther <rguenther at suse dot de>, Tobias Burnus <burnus at net-b dot de>, Gerald Pfeifer <gerald at pfeifer dot com>, Mark Mitchell <mark at codesourcery dot com>, GCC <gcc at gcc dot gnu dot org>, "Joseph S. Myers" <joseph at codesourcery dot com>, Jakub Jelinek <jakub at redhat dot com>
- Date: Sat, 09 Oct 2010 03:03:36 +0100
- Subject: Re: End of GCC 4.6 Stage 1: October 27, 2010
- References: <4C7D26EA.6020807@codesourcery.com> <4C841725.4070603@net-b.de> <alpine.LNX.2.00.1009061121430.28912@zhemvz.fhfr.qr> <AANLkTi=EB-E2Vfr+qMmy1L2i_1rYHRx9dZsJaG4hFUTb@mail.gmail.com> <AANLkTinCNxzQKMrsFNK3vQSGRrO7se5Sh_iO9uw=dTGS@mail.gmail.com> <AANLkTikc2E4c3wCMJANzqdwA+U2wtrt7cbt5PA46mWb7@mail.gmail.com> <4C8523C6.10200@redhat.com> <AANLkTimYs=iewig4CR-aj4LxmxxgUTPkJy-fx=aK4dFz@mail.gmail.com> <AANLkTikBvrdvLLFhybbiXgcpaOE2fk1wgGDSQT7g7sRm@mail.gmail.com> <AANLkTinJkxUTL4AOLUrGNHZvG5GSuUn=6VDQegwSb+8Y@mail.gmail.com> <AANLkTik7meeXwdo6SxYnFmSGUbgBtxVyaNtncYDXQUeE@mail.gmail.com> <4C98B286.3090201@gmail.com> <AANLkTimwjQ08St5LWvoCO_An3WSX5ryXGh=qsvuCr-wZ@mail.gmail.com> <AANLkTin=9HsqTYu+1Xju6CBH1WqGCgLAU8vaSEKR7ZGz@mail.gmail.com> <AANLkTimFuK9_-vDT-7ZP9DJAdsuXUUsYZydYPEMK9yCQ@mail.gmail.com> <AANLkTimCyX4Yj3me37mdFoXp-_di=XkeOm83y=zEQW=i@mail.gmail.com> <AANLkTimPpBEWupP=zCWiAyP-h-jUJZ6Fb+YH==UGR=Fs@mail.gmail.com>
On 08/10/2010 19:10, NightStrike wrote:
> On Fri, Oct 8, 2010 at 2:04 PM, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
>> Most of the failing libstdc++ tests which shouldn't be
>> platform-dependent fail with this message:
>> sh: /usr/bin/stty: Bad address
>
> This Bad address stuff is due to some conflict with cygwin. We really
> need to work with cygwin folks to find a proper fix, but are having
> difficulty.
>
> Dave, can you work with Kai to help troubleshoot that, by any chance?
I'm pretty busy at the moment, and you're the one who actually has the
problem manifesting itself, plus all the log files and build dirs that you'd
need to figure out what it is that's going wrong.
cheers,
DaveK