public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Dara Hazeghi <dhazeghi@yahoo.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: bootstrap/10815: C compiler cannot create executables Date: Sat, 17 May 2003 00:36:00 -0000 [thread overview] Message-ID: <20030517003601.11223.qmail@sources.redhat.com> (raw) The following reply was made to PR bootstrap/10815; it has been noted by GNATS. From: Dara Hazeghi <dhazeghi@yahoo.com> To: gcc-gnats@gcc.gnu.org, rolf-alois.walter@db.com, nobody@gcc.gnu.org Cc: Subject: Re: bootstrap/10815: C compiler cannot create executables Date: Fri, 16 May 2003 17:25:44 -0700 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit- trail&database=gcc&pr=10815 Hello, next time you send such a bug report, it would help to know what directory gmake failed in. But anyhow, it looks like the stage1 gcc isn't happy building 64 bit stuff. Can you cd into powerpc-ibm-aix5.1.0.0/ppc64/libiberty/ (in your build directory) and create the following file conftest.c: #include "confdefs.h" main(){return(0);} and then run this command: /software/gcc-3.3-obj/gcc/xgcc -B/software/gcc-3.3-obj/gcc/ -B/u sr/local/powerpc-ibm-aix5.1.0.0/bin/ -B/usr/local/powerpc-ibm-aix5.1.0.0/lib/ -i system /usr/local/powerpc-ibm-aix5.1.0.0/include -maix64 -v -o conftest -O2 -g -O2 conftest.c And post back the output? It looks like the linker is for some reason unhappy (according to config.log), but hopefully this will make it possible to figure out why. Thanks, Dara
next reply other threads:[~2003-05-17 0:36 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-17 0:36 Dara Hazeghi [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-16 5:56 rolf-alois.walter
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=20030517003601.11223.qmail@sources.redhat.com \ --to=dhazeghi@yahoo.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).