public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jv244 at cam dot ac dot uk" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/11745] Bootstrap fails when compiling insn-attrtab.c with stage1/xgcc Date: Fri, 15 Aug 2003 18:45:00 -0000 [thread overview] Message-ID: <20030815184519.10914.qmail@sources.redhat.com> (raw) In-Reply-To: <20030731140827.11745.tobias.schlueter@web.de> PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11745 ------- Additional Comments From jv244 at cam dot ac dot uk 2003-08-15 18:45 ------- Unhappily this is not working. The flag is added for some of the compiles e.g. gcc -c -DHAVE_CONFIG_H -g -Wl,--stack,8388608 -I. -I/home/vondele/gcc- g95/gcc/libiberty/../include -W -Wall -Wtraditional - pedantic /home/vondele/gcc-g95/gcc/libiberty/stpncpy.c -o pic/stpncpy.o but not for linking xgcc.exe (where I suppose it is mostly needed) gcc -g -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing- prototypes -pedantic -Wno-long-long -fno-common -DHAVE_CONFIG_H -o xgcc.exe gcc.o gccspec.o intl.o \ prefix.o version.o cygwin1.o ../libiberty/libiberty.a -lintl - liconv ../libbanshee/points- to/libandersen.a ../libbanshee/engine/libbansheeengine.a ../libbanshee/libcompa t/libbansheecompat.a the final error remains the same. (BTW using these CFLAGS also produces a lot of warnings : gcc: --stack: linker input file unused because linking not done gcc: 8388608: linker input file unused because linking not done )
next prev parent reply other threads:[~2003-08-15 18:45 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-07-31 14:08 [Bug bootstrap/11745] New: " tobias dot schlueter at web dot de 2003-07-31 14:14 ` [Bug bootstrap/11745] " tobias dot schlueter at web dot de 2003-07-31 14:16 ` tobias dot schlueter at web dot de 2003-08-05 19:39 ` pinskia at physics dot uc dot edu 2003-08-13 19:39 ` jv244 at cam dot ac dot uk 2003-08-13 21:50 ` tobias dot schlueter at web dot de 2003-08-13 21:58 ` tobias dot schlueter at web dot de 2003-08-15 3:30 ` pinskia at gcc dot gnu dot org 2003-08-15 7:21 ` jv244 at cam dot ac dot uk 2003-08-15 11:17 ` tobias dot schlueter at web dot de 2003-08-15 11:51 ` jv244 at cam dot ac dot uk 2003-08-15 18:07 ` pinskia at gcc dot gnu dot org 2003-08-15 18:45 ` jv244 at cam dot ac dot uk [this message] 2003-08-15 19:10 ` pinskia at gcc dot gnu dot org 2003-08-15 20:03 ` jv244 at cam dot ac dot uk 2003-08-15 20:06 ` [Bug bootstrap/11745] Bootstrap fails when compiling insn-attrtab.c with stage1/xgcc (stacksize too low) pinskia at gcc dot gnu dot org 2003-08-20 5:54 ` david dot billinghurst at riotinto dot com 2003-09-22 13:15 ` tobias dot schlueter at web dot de 2003-09-22 17:13 ` pinskia at gcc dot gnu dot org 2003-11-01 20:57 ` Tobias dot Schlueter at physik dot uni-muenchen dot de 2003-11-02 18:21 ` tobias dot schlueter at web dot de 2003-08-15 6:41 [Bug bootstrap/11745] Bootstrap fails when compiling insn-attrtab.c with stage1/xgcc Billinghurst, David (CRTS)
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=20030815184519.10914.qmail@sources.redhat.com \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).