public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: James.Parker@saaconsultants.com
To: gcc-help@gcc.gnu.org
Subject: Re: installing GCC 3.4.4 on cygwin targeting AIX-4.3.3
Date: Mon, 19 Sep 2005 10:24:00 -0000	[thread overview]
Message-ID: <OFF8444372.2094481D-ON80257081.0031C218-80257081.00395C7C@SAAConsultants.com> (raw)
In-Reply-To: <200509161919.j8GJJiq26294@makai.watson.ibm.com>

> > I have $prefix/bin/$target-<cmds> files installed,
> > e.g. rs6000-ibm-aix4.3.3.0-as. 
> > 
> > My path includes $prefix/bin so these new commands are now all on the 
> > path.
> 
>    You should have the tools installed in two locations.  One as
> $prefix/bin/$target-<cmds> and another as something like
> $prefix/$target/bin/<cmds> .

Yes - I have these in both. 

> 
> > It looks like an assembler error, how do I know if my make script is 
using 
> > correct assembler?
> 
>    You can invoke the command manually and add the "-v" option.  This
> will print out information about the commands that the "gcc" driver
> program is invoking.

I observe the following:

--> $prefix/bin/$target-ld -V
GNU ld version 2.16.91 20050610
  Supported emulations:
   aixrs6

--> $prefix/bin/$target-as --version
GNU assembler 2.16.91 20050610
Copyright 2005 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License.  This program has absolutely no warranty.
This assembler was configured for a target of `rs6000-ibm-aix4.3.3.0'.


--> $prefix/$target/bin/ld -V
GNU ld version 2.16.91 20050610
  Supported emulations:
   aixrs6

--> $prefix/$target/bin/as --version
GNU assembler 2.16.91 20050610
Copyright 2005 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License.  This program has absolutely no warranty.
This assembler was configured for a target of `rs6000-ibm-aix4.3.3.0'.

I see that the same original error message was seen by the author of this 
bug:

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

Reading through the bug report it seems that he/she had an incorrect path. 
However, my path is:

/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/cygdrive/c/IBMDebug/bin:/cygdrive/c
/WINNT/system32:/cygdrive/c/WINNT:/cygdrive/c/WINNT/System32/Wbem:/cygdrive/c/PR
OGRA~1/IBM/CLIENT~1:/cygdrive/c/PROGRA~1/IBM/CLIENT~1/Shared:/cygdrive/c/PROGRA~
1/IBM/CLIENT~1/Emulator:/cygdrive/c/Program Files/Microsoft SQL 
Server/80/Tools/
Binn/:/cygdrive/c/php:/cygdrive/c/Program 
Files/vslick/win:/cygdrive/c/mysql/bin
:/usr/local/cross-tools/bin

so that when I type:

$ which as
/usr/local/bin/as
$ as --version
GNU assembler 2.16.91 20050610
Copyright 2005 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License.  This program has absolutely no warranty.
This assembler was configured for a target of `i686-pc-cygwin'.

When I installed cygwin, I simply got whatever gcc binaries came with it. 
Perhaps I should build gcc for host=target=i686-pc-cygwin before 
attempting to build the cross-compiler?

I notice this also:

$ uname -i
unknown
$ uname -p
unknown

Cygwin doesn't know what hardware platform or op sys I have (?!). Perhaps 
this confuses the configure script for gcc?

Any other thoughts on why this is not working?

Thanks!

(I should build this all on Linux - except for that means going through 
our IT guys to get permission for Linux box which they won't do until they 
can see the benefit - which is why I am attempting to demostrate cross 
compilation to them using cygwin!)

  reply	other threads:[~2005-09-19 10:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-16 14:21 James.Parker
2005-09-16 19:20 ` David Edelsohn
2005-09-19 10:24   ` James.Parker [this message]
2005-09-19 16:21     ` David Edelsohn

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=OFF8444372.2094481D-ON80257081.0031C218-80257081.00395C7C@SAAConsultants.com \
    --to=james.parker@saaconsultants.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).