X-Spam-Check-By: sourceware.org X-YMail-OSG: R4S5j8YVM1k0xj.wD8GfgiVQZxKC_P8NHbnBDYj8o2vXrpnSjiZguE0uBNS0gqELZulsinv6_lEuKUGPQ6zxwE3.9MCLnVbpJmDHvp.Y8.ICJo.lAzne0EugXuocd58n4cMQ9KAWznmbNvRGQ3RoO_GO0A-- Message-ID: <46047FE0.6090108@aol.com> Date: Fri, 23 Mar 2007 18:33:20 -0700 From: Tim Prince Reply-To: tprince AT computer DOT org User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Building GCC 4.3.0 on Cygwin... References: <4602FE46 DOT 50E27743 AT dessent DOT net> In-Reply-To: <4602FE46.50E27743@dessent.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com brian AT dessent DOT net wrote: > Angelo Graziosi wrote: > >> As I wrote: >> >>>> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31039 > > Ah, okay. I failed to see that you'd posted the config.log there. (And > I mentioned gmp/mpfr as I have seen that cause the build to fail in > exactly the way you described, but it's clearly not the case here.) > > The real problem seems to be that the libgcc is broken: > > configure:2121: /home/User/cvsroot/gcc-obj/./prev-gcc/xgcc > -B/home/User/cvsroot/gcc-obj/./prev-gcc/ > -B/usr/local/i686-pc-cygwin/bin/ > conftest.c >&5 > /home/User/cvsroot/gcc-obj/./prev-gcc/libgcc.a(_ctors.o): In function > `__sgetc_r': > /usr/include/stdio.h:414: undefined reference to `_ungetc' > /usr/include/stdio.h:410: undefined reference to `___srget_r' > /usr/include/stdio.h:407: undefined reference to `___srget_r' > collect2: ld returned 1 exit status > > It looks like a problem with some function being defined as a macro when > it shouldn't, or vice versa. You'll need to look into how _ctors.o is > built to see exactly, since I can't find any reference to _sgetc_r or > ungetc in any of the libgcc2.{c,h} files. You can try the trick of > going into the libgcc build directory (you may have to "make restage1" > to back up one stage), "rm _ctors.o" and then "make CFLAGS="-g -O2 > -save-temps"" (or some variant) and then look at the preprocessed source > to see what's happening. > > Brian > Just before that, there is a reported failure of the bootstrap compiler, due to the trailing -V argument supplied in configure. Most of the configure files in the recent 4.3 snapshots do this. I don't have a clue what this -V is meant for. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/