public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jlm_devel at laposte dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/21698] creating first stage compiler Date: Sat, 21 May 2005 17:50:00 -0000 [thread overview] Message-ID: <20050521175048.28412.qmail@sourceware.org> (raw) In-Reply-To: <20050521154049.21698.jlm_devel@laposte.net> ------- Additional Comments From jlm_devel at laposte dot net 2005-05-21 17:50 ------- maybe, I can too using several workaround like crosstool.sh is doing.... but this lead to have the target tree be located at the same place of the crosschain.... which is a nonsens... why a target filesystem's location MUST depend on where the chain is located? anyway the issue is related to gcc/libgcc.mk seeking into the logs I found that make gcc-all was doing a make \ CFLAGS="-mtune=athlon64 -O2 -pipe -Wno-deprecated-declarations -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long " \ CONFIG_H="config.h auto-host.h ./../include/ansidecl.h" \ MAKEOVERRIDES= \ -f libgcc.mk all which fail.... on the other hand when doing a make all in gcc/ you still get the right libgcc.a so i'll make a patch.... anyway since you're using gnu make why are the Makefiles such a mess (lot of redefines, no use of include....) so I still maintain that the --with-local-prefix= in configure should be used to give information where the headers are located (all the docs I read say so....) and that there is an issue with libgcc.mk as you say peoples are doing crosscompiler everyday but look at crosstool.sh 's hacks to be sure there are a issue.... by the way : should the gcc libraries not be independant of a libc? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21698
next prev parent reply other threads:[~2005-05-21 17:50 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-05-21 15:40 [Bug bootstrap/21698] New: " jlm_devel at laposte dot net 2005-05-21 15:43 ` [Bug bootstrap/21698] " pinskia at gcc dot gnu dot org 2005-05-21 17:50 ` jlm_devel at laposte dot net [this message] 2005-05-21 18:22 ` jlm_devel at laposte dot net 2005-06-01 17:35 ` jlm_devel at laposte dot net [not found] <bug-21698-10632@http.gcc.gnu.org/bugzilla/> 2006-03-18 6:20 ` pinskia at gcc dot gnu dot org
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=20050521175048.28412.qmail@sourceware.org \ --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).