From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14365 invoked by alias); 11 Apr 2009 19:33:28 -0000 Received: (qmail 13225 invoked by uid 48); 11 Apr 2009 19:33:15 -0000 Date: Sat, 11 Apr 2009 19:33:00 -0000 Message-ID: <20090411193315.13224.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug target/39738] GCC cannot build itself for win64 platform In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "ktietz at gcc dot gnu dot org" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2009-04/txt/msg01032.txt.bz2 ------- Comment #2 from ktietz at gcc dot gnu dot org 2009-04-11 19:33 ------- (In reply to comment #1) > Are you sure your entire compiler is up to date, not just the library? And the > build and install directories are clean? Because your first lines of failure > involve bits of the library which *require* a consistent simultaneous change in > the C++ front-end, and well, nobody is experiencing similar problems anywhere. > Not that this code is target-independent. > > CC-ing Jason, the author of such code, to be sure. > Well, on 4.4 branch there was a patch introducing the winsup link, which got necessary for building libstdc++. We solve this by setting up in gcc's source tree a symbolic link "winsup" pointing to the sysroot (prefix) directory. Cheers, Kai -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39738