From: Michael Semenchenko <michael-sem@usa.net>
To: help-gcc@gnu.org
Subject: Installing gcc as a cross compiler
Date: Wed, 17 Nov 1999 20:31:00 -0000 [thread overview]
Message-ID: <38337F7E.F4527351@usa.net> (raw)
Hello !
I need to build the GNU cross compiler and cross linker:
host: i586-pc-linux
target: alpha-dec-osf
I was using sources:
gcc: gcc-2.95.2
binutils: binutils-2.9.1
When configuring 'binutils' I get the message that 'as' and 'ld' are
incompatible with specified configuration. These programs were not built.
When building 'gcc' I got the linker error:
toplev.o (.text+0x1d6a): Undefined reference to ASM_FILE_START
I shall greatly appreciate receiving answers on following questions:
- does anyone succeeded in doing this ?
- what I was doing wrong ?
- where can I get some specific information on 'gcc' as a cross-compiler ?
Can I find anywhere in the net the list of cross-configurations succesfully
installed ?
- are 'configure' options --with-as=/path/to/assembler and --with-ld=
/path/to/ld obligatory ?
- can I build the GNU cross compiler, assembler and linker without
system include files from DEC Alpha present in my computer ? In other way:
is 'configure' option --with-headers=dir obligatory ?
- can I build the GNU cross compiler, assembler and linker without
target runtime libraries present in my computer ? In other way: is
'configure' option --with-libs=dir obligatory ?
Thank you for any comments.
Yours, Michael.
WARNING: multiple messages have this Message-ID
From: Michael Semenchenko <michael-sem@usa.net>
To: help-gcc@gnu.org
Subject: Installing gcc as a cross compiler
Date: Tue, 30 Nov 1999 23:28:00 -0000 [thread overview]
Message-ID: <38337F7E.F4527351@usa.net> (raw)
Message-ID: <19991130232800.4R4if4eipPxza6GFx5LJvwr5XxRnsI-Ih99fHtZbFBM@z> (raw)
Hello !
I need to build the GNU cross compiler and cross linker:
host: i586-pc-linux
target: alpha-dec-osf
I was using sources:
gcc: gcc-2.95.2
binutils: binutils-2.9.1
When configuring 'binutils' I get the message that 'as' and 'ld' are
incompatible with specified configuration. These programs were not built.
When building 'gcc' I got the linker error:
toplev.o (.text+0x1d6a): Undefined reference to ASM_FILE_START
I shall greatly appreciate receiving answers on following questions:
- does anyone succeeded in doing this ?
- what I was doing wrong ?
- where can I get some specific information on 'gcc' as a cross-compiler ?
Can I find anywhere in the net the list of cross-configurations succesfully
installed ?
- are 'configure' options --with-as=/path/to/assembler and --with-ld=
/path/to/ld obligatory ?
- can I build the GNU cross compiler, assembler and linker without
system include files from DEC Alpha present in my computer ? In other way:
is 'configure' option --with-headers=dir obligatory ?
- can I build the GNU cross compiler, assembler and linker without
target runtime libraries present in my computer ? In other way: is
'configure' option --with-libs=dir obligatory ?
Thank you for any comments.
Yours, Michael.
next reply other threads:[~1999-11-17 20:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-17 20:31 Michael Semenchenko [this message]
1999-11-17 23:24 ` Eric Doenges
1999-11-30 23:28 ` Eric Doenges
1999-11-30 23:28 ` Michael Semenchenko
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=38337F7E.F4527351@usa.net \
--to=michael-sem@usa.net \
--cc=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).