public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "北斗 星君" <huangxiangkui@msn.com>
To: gcc-help@gcc.gnu.org
Subject: I couldn't build gcc.
Date: Mon, 27 Jun 2005 20:52:00 -0000	[thread overview]
Message-ID: <BAY11-F24F3C27EFD1BB32C4201B8BEEE0@phx.gbl> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb2312; format=flowed, Size: 2844 bytes --]

I am a middle school student in China.

I build gcc-3.3.3 on my computer.But it is some error on it.

make[1]: Entering directory `/cygdrive/e/ToolBuild/gcc-build/libiberty'
make[2]: Entering directory 
`/cygdrive/e/ToolBuild/gcc-build/libiberty/testsuite
'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory 
`/cygdrive/e/ToolBuild/gcc-build/libiberty/testsuite'

make[1]: Leaving directory `/cygdrive/e/ToolBuild/gcc-build/libiberty'
make[1]: Entering directory `/cygdrive/e/ToolBuild/gcc-build/gcc'
(cd intl && make all)
make[2]: Entering directory `/cygdrive/e/ToolBuild/gcc-build/gcc/intl'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/cygdrive/e/ToolBuild/gcc-build/gcc/intl'
(MAKE="make"; srcdir=`cd ../../gcc-3.3.3/gcc/fixinc && ${PWDCMD-pwd}` ; \
CC="gcc"; CFLAGS="  -g -O2 -DIN_GCC -DCROSS_COMPILE  -W -Wall 
-Wwrite-strings -W
strict-prototypes -Wmissing-prototypes -Wtraditional -pedantic 
-Wno-long-long
-DHAVE_CONFIG_H -DGENERATOR_FILE"; LDFLAGS=""; \
WARN_CFLAGS="-W -Wall -Wwrite-strings -Wstrict-prototypes 
-Wmissing-prototypes -
Wtraditional -pedantic -Wno-long-long "; 
LIBERTY=`pwd`/"../libiberty/libiberty.a
"; \
export MAKE srcdir CC CFLAGS LDFLAGS WARN_CFLAGS LIBERTY; \
cd ./fixinc && \
/bin/sh ${srcdir}/mkfixinc.sh i686-pc-cygwin i386-pc-elf)
constructing ../fixinc.sh for i386-pc-elf to run on i686-pc-cygwin
make TARGETS=oneprocess SHELL="/bin/sh" CC="gcc" CFLAGS=" -g -O2 -DIN_GCC 
-DCROS
S_COMPILE -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes 
-Wtr
aditional -pedantic -Wno-long-long -DHAVE_CONFIG_H -DGENERATOR_FILE" 
LDFLAGS=""
LIBERTY="/cygdrive/e/ToolBuild/gcc-build/gcc/../libiberty/libiberty.a" 
install-b
in
make[2]: Entering directory `/cygdrive/e/ToolBuild/gcc-build/gcc/fixinc'
/bin/sh ../../../gcc-3.3.3/gcc/fixinc/genfixes machname.h
-uϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
make[2]: *** [machname.h] Error 1
make[2]: Leaving directory `/cygdrive/e/ToolBuild/gcc-build/gcc/fixinc'
make[1]: *** [fixinc.sh] Error 2
make[1]: Leaving directory `/cygdrive/e/ToolBuild/gcc-build/gcc'
make: *** [all-gcc] Error 2

Because it is lacking of machname.h,I couldn't build it.

Somebody in gcc maillist tell me ask the question to Cygwin.

But the error is not Cygwin.Some people use Linux to build cross-gcc also 
appear this problem.

And I couldn't find the Cygwin's maillist.

And,the person who tell me to ask Cygwin,tell me that cygwin is not good to 
use gcc.But what can I use?Which GCC can I use on Win32?Which cross-GCC can 
I use on Win32?NO!No any one except Cygwin.

I do feel that the GCC source's error must ask GCC.
So give me some advise,please.I must build it.

_________________________________________________________________
ÓëÁª»úµÄÅóÓѽøÐн»Á÷£¬ÇëʹÓà MSN Messenger:  http://messenger.msn.com/cn  

             reply	other threads:[~2005-06-27 20:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-27 20:52 北斗 星君 [this message]
2005-06-28 15:02 ` Lionel B
2005-06-30 13:59 北斗 星君
2005-06-30 17:15 ` Arturas Moskvinas

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=BAY11-F24F3C27EFD1BB32C4201B8BEEE0@phx.gbl \
    --to=huangxiangkui@msn.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).