public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Benjamin P Myers <dative@sukrahelitek.com>
To: gcc-help@gcc.gnu.org
Subject: linux->irix cross confusion
Date: Tue, 26 Jun 2001 02:24:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.21.0106260403340.13590-100000@vishnu.sukra.com> (raw)

Hi Folks, 

I'm having a bit of trouble building a target: mips-sgi-irix6 on 
i686-gnu-linux, host i686-gnu-linux.  I've installed binutils-2.11.2,
target mips-sgi-irix6 into /usr/local/:

> /usr/local/mips-sgi-irix6/bin/ld -v
GNU ld version 2.11.2 (with BFD 2.11.2)
> /usr/local/mips-sgi-irix6/bin/as -v
GNU assembler version 2.11.2 (mips-sgi-irix6) using BFD version 2.11.2
...

I've copied the headers and libraries from the target machine I want to
use as per the instructions in the gcc manual, i think:

scp -r <me>@<my_irix_box>:/usr/include/*
/usr/local/mips-sgi-irix6/include/

and /usr/local/mips-sgi-irix6/lib: 
acrt1.o crt1.o ldscripts libc.so.1 libdisk.so libmalloc.so rld
cpp      crtn.o  libc.a     libcpr.so  libm.a      mcrt1.o   

it was copied over from various places on the irix box... i dunno.  i
haven't gotten to the linking part yet.  Next, It looks as if the
requirement for libgcc1.a isn't there for 3.0, so i skipped that, did a:

> cd gcc-3.0
> ./configure --with-gnu-as:/usr/local/mips-sgi-irix6/bin/as
--with-gnu-ld=/usr/local/mips-sgi-irix6/bin/ld --target=mips-sgi-irix6
> make cross

and after a lengthy build process i come to this:

/vishnu/0/dative(that's me!)/gcc-3.0/gcc/xgcc
-B/vishnu/0/dative/gcc-3.0/gcc/
-B/usr/local/mips-sgi-irix6/bin/ -B/usr/local/mips-sgi-irix6/lib/ -isystem
/usr/local/mips-sgi-irix6/include -O2 -DCROSS_COMPILE -DIN_GCC -W -Wall
-Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -isystem
./include -g1 -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc -I. -I.
-I. -I./. -I./config -I./../include -DL_muldi3 -c ./libgcc2.c -o
libgcc/./_muldi3.o
/usr/local/mips-sgi-irix6/bin/as: unrecognized option `-n32'  

I, of course have absolutely no idea what this means, but that isn't to
say i didn't try fooling with various specs files to make it go away.  No
doubt this is documented in this list's FAQ, but after having spent a few
hours searching for a clue on google (god knows i need one), i'm a little
burnt out.  Any advice anyone coudl give on this issue would be
appreciated.

Thanks!
-Ben Myers (mildly sprained systems geek)


             reply	other threads:[~2001-06-26  2:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-26  2:24 Benjamin P Myers [this message]
2001-06-26 18:34 ` Benjamin P Myers

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=Pine.LNX.4.21.0106260403340.13590-100000@vishnu.sukra.com \
    --to=dative@sukrahelitek.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).