From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21246 invoked by alias); 22 Jun 2006 10:31:09 -0000 Received: (qmail 21231 invoked by uid 22791); 22 Jun 2006 10:31:08 -0000 X-Spam-Check-By: sourceware.org Received: from ug-out-1314.google.com (HELO ug-out-1314.google.com) (66.249.92.175) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 22 Jun 2006 10:31:04 +0000 Received: by ug-out-1314.google.com with SMTP id c2so399428ugf for ; Thu, 22 Jun 2006 03:31:02 -0700 (PDT) Received: by 10.66.221.6 with SMTP id t6mr930509ugg; Thu, 22 Jun 2006 03:31:01 -0700 (PDT) Received: by 10.66.233.8 with HTTP; Thu, 22 Jun 2006 03:31:01 -0700 (PDT) Message-ID: <43a7c3700606220331t65c1a361ie424dc1300bf0058@mail.gmail.com> Date: Thu, 22 Jun 2006 10:31:00 -0000 From: "Alexander Shabanov" To: gcc-help@gcc.gnu.org Subject: Re: xgcc unable to build libgcc under mingw In-Reply-To: <85e0e3140606211344p6ee3a03ew66a19ea6847d9a25@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <43a7c3700606210206r9910791t33a35f4d7e8a81d6@mail.gmail.com> <85e0e3140606211344p6ee3a03ew66a19ea6847d9a25@mail.gmail.com> Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org X-SW-Source: 2006-06/txt/msg00172.txt.bz2 Thank you very much, your advice works. As a conclusion - in case somebody again will want compile gcc under MinGW: 1) create in your msys `local' directory folder `i686-pc-mingw32' 2) copy all(I copied all :)) content of msys' root directory to this folder (of course, except `local' directory) 3) configure & make. After `make install' you will have several gcc on your computer. Compiled gcc compiler driver will have name `i686-pc-mingw32-gcc.exe'. 2006/6/21, Niklaus : > well you have to copy the header files and library files into $prefix/$target > where target is the target given to your configure and prefix is the > prefix to configure. > usually it is like prefix is like =/home/pro and > target=i586-unknown-mingw32 . Do something alike for your target. the > header files and library are of the target. Maybe you want to look my > post at cross gcc . I gave a build procedure for build cross gcc > solaris and mingw32 from linux. > > On 6/21/06, Alexander Shabanov wrote: > > Hello! > > > > As I said in my previous question - I tried to compile gcc under > > mingw. If we want to compile gcc under mingw, we must specify path to > > `ld', like '../configure --with-ld=/mingw/bin/ld'. Compilers built > > fine - we obtain $(MINGW_OBJDIR)/gcc/cc1plus, cc1, xgcc, etc. After > > building makefile tried to build libgcc using xgcc, but unable to do > > it: > > > > --------------------- BEGIN > > make[3]: Entering directory `/d/GnuProjects/gcc/gcc-4.1.1/obj_mgw_nostdcpp/gcc' > > > > /d/GnuProjects/gcc/gcc-4.1.1/obj_mgw_nostdcpp/./gcc/xgcc > > -B/d/GnuProjects/gcc/gcc-4.1.1/obj_mgw_nostdcpp/./gcc/ > > -B/usr/local/i686-pc-mingw32/bin/ -B/usr/local/i686-pc-mingw32/lib/ > > -isystem /usr/local/i686-pc-mingw32/include -isystem > > /usr/local/i686-pc-mingw32/sys-include -O2 > > -I../../gcc/../winsup/w32api/include -O2 -g -O2 -DIN_GCC -W -Wall > > -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes > > -Wold-style-definition -isystem ./include -g -DHAVE_GTHR_DEFAULT > > -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -I. -I. -I../../gcc > > -I../../gcc/. -I../../gcc/../include -I./../intl > > -I../../gcc/../libcpp/include -DL_negdi2 -c ../../gcc/libgcc2.c -o > > libgcc/./_negdi2.o > > In file included from ../../gcc/libgcc2.c:33: > > ../../gcc/tsystem.h:90:19: error: stdio.h: No such file or directory > > ../../gcc/tsystem.h:93:23: error: sys/types.h: No such file or directory > > ../../gcc/tsystem.h:96:19: error: errno.h: No such file or directory > > ../../gcc/tsystem.h:103:20: error: string.h: No such file or directory > > ../../gcc/tsystem.h:104:20: error: stdlib.h: No such file or directory > > ../../gcc/tsystem.h:105:20: error: unistd.h: No such file or directory > > In file included from ./include/limits.h:122, > > --------------------- END > > As I understood, it happens, because makefile script unable to find > > correct path to sysincludes headers. > > > > Please, explain, how can I fix it? > > > > -- > > Best regards, > > Alexander Shabanov > > > -- Best regards, Alexander Shabanov