public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dhazeghi@yahoo.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/10815] C compiler cannot create executables
Date: Mon, 26 May 2003 17:46:00 -0000	[thread overview]
Message-ID: <20030526174041.8958.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030516055600.10815.rolf-alois.walter@db.com>

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10815



------- Additional Comments From dhazeghi@yahoo.com  2003-05-26 17:40 -------
Hello,

well all I can see from the report is that the linker's not very happy.

I'm not sure if this will help, but can you do the following. 

/software/gcc-3.3-obj/gcc/xgcc -B/software/gcc-3.3-obj/gcc/ 
-B/usr/local/powerpc-ibm-aix5.1.0.0/bin/ -B/usr/local
/powerpc-ibm-aix5.1.0.0/lib/ -isystem 
/usr/local/powerpc-ibm-aix5.1.0.0/include -maix64 -v -o conftest.o -O2 -c -g 
-O2 conftest.c

Then run the following:

/software/gcc-3.3-obj/gcc/collect2 -v -bpT:0x10000000 -bpD:0x20000000 
-btextro -bnodelcsect -b64 -o conftest /lib/crt0_64.o -L/software/gcc-3.3-obj/gcc/ppc64 -L/
software/gcc-3.3-obj/gcc -L/usr/local/powerpc-ibm-aix5.1.0.0/bin -L/usr/local/powerpc-ibm-
aix5.1.0.0/lib -L/usr/local/lib/gcc-lib/powerpc-ibm-aix5.1.0.0/../../../powerpc-ibm-aix5.1.0.0/
lib -L/usr/local/lib/gcc-lib/powerpc-ibm-aix5.1.0.0/../../ppc64 -L/usr/local/lib/gcc-lib/
powerpc-ibm-aix5.1.0.0/../.. conftest.o /software/gcc-3.3-obj/gcc/ppc64/libgcc.a /
software/gcc-3.3-obj/gcc/ppc64/libgcc_eh.a -lc /software/gcc-3.3-obj/gcc/ppc64/libgcc.a /
software/gcc-3.3-obj/gcc/ppc64/libgcc_eh.a

Hopefully, we can find out exactly why the linker is not happy (ie an error message). If this doesn't 
work, I suggest we forward the report to our AIX maintainer who will probably be able to figure the 
problem out in a matter of a minute or two :-)

Dara



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  parent reply	other threads:[~2003-05-26 17:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030516055600.10815.rolf-alois.walter@db.com>
2003-05-26  8:29 ` dhazeghi@yahoo.com
2003-05-26  9:25 ` rolf-alois.walter@db.com
2003-05-26 17:46 ` dhazeghi@yahoo.com [this message]
2003-05-26 17:53 ` pinskia@physics.uc.edu
2003-05-27  5:43 ` rolf-alois.walter@db.com
2003-05-27  6:58 ` dhazeghi@yahoo.com
2003-05-27  7:22 ` rolf-alois.walter@db.com
2003-05-27  7:36 ` dhazeghi@yahoo.com
2003-05-27  7:59 ` dhazeghi@yahoo.com
2003-05-27 14:34 ` dje@watson.ibm.com
2003-06-02  0:15 ` [Bug bootstrap/10815] [AIX] " dhazeghi@yahoo.com
2003-06-02  5:47 ` rolf-alois.walter@db.com
2003-06-02  6:21 ` dhazeghi@yahoo.com
2003-06-02  6:37 ` rolf-alois.walter@db.com
2003-06-02 17:37 ` dje@watson.ibm.com
2003-06-04  6:36 ` dhazeghi@yahoo.com
2003-06-04 17:02 ` dje@gcc.gnu.org
2003-06-04 17:04 ` dje@gcc.gnu.org
2003-06-04 17:15 ` dje@watson.ibm.com

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=20030526174041.8958.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: 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).