From: "Alexander Shabanov" <avshabanov@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: Re: xgcc unable to build libgcc under mingw
Date: Thu, 22 Jun 2006 10:31:00 -0000 [thread overview]
Message-ID: <43a7c3700606220331t65c1a361ie424dc1300bf0058@mail.gmail.com> (raw)
In-Reply-To: <85e0e3140606211344p6ee3a03ew66a19ea6847d9a25@mail.gmail.com>
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 <niklaus@gmail.com>:
> 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 <avshabanov@gmail.com> 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
prev parent reply other threads:[~2006-06-22 10:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-21 9:06 Alexander Shabanov
2006-06-21 20:41 ` Tim Prince
2006-06-21 20:44 ` Niklaus
2006-06-22 10:31 ` Alexander Shabanov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43a7c3700606220331t65c1a361ie424dc1300bf0058@mail.gmail.com \
--to=avshabanov@gmail.com \
--cc=gcc-help@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).