public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: JAY LULLA <JAY.LULLA@Sun.COM>
To: crossgcc@sourceware.cygnus.com, gcc-help@gcc.gnu.org
Cc: jay.lulla@ebay.sun.com, hsing.yuan@ebay.sun.com, swamin@ebay.sun.com
Subject: Installing cross-compiler for PowerPC 603, pSOS
Date: Fri, 14 Jan 2000 11:35:00 -0000	[thread overview]
Message-ID: <387F7A4E.85093CF7@Sun.COM> (raw)

Hi. I would like to get some advice about cross-compiling GCC for a Sun
Solaris host, and PowerPC target.

We have already installed gcc-2.95.2, with its complete source.

Here are some issues I need to address:
- should the cross-compiler be installed in the same dir as the native
compiler, and then be called with a special flag, or should it be
installed in a whole new directory altogether?

- should we use flags such as 'with-as' 'with-ld' and 'with-headers' to
specify directories for the assembler, linker, and headers, or is it
best to leave these out, and then specify which assemblers, linkers etc
to use as flags when we actually use the cross-gcc? - If we use the
flags when we actually run gcc, we would have more flexibility in trying
different assemblers and linkers, or have the option of not linking at
all, right? - Or would you have the same flexibility by installing it
with default directories, and then overriding the defaults if you choose
to do so when running gcc?

- does it matter what version of 'make' one uses? ie whether we use
'make' from cc or from GNU?

- I've never used binutils before. What is it all about? Does it have
any useful tools for profiling the code (analyzing it to produce a
function call graph, for example)?
-----------------------------

On a related note, I notice that GCC has tools to make it compatible
with certain embedded operating systems. Are there any tools for pSOS? I
couldn't find any...

Thanks,
Jay Lulla
jay.lulla@ebay.sun.com

WARNING: multiple messages have this Message-ID
From: JAY LULLA <JAY.LULLA@Sun.COM>
To: crossgcc@sourceware.cygnus.com, gcc-help@gcc.gnu.org
Cc: jay.lulla@ebay.sun.com, hsing.yuan@ebay.sun.com, swamin@ebay.sun.com
Subject: Installing cross-compiler for PowerPC 603, pSOS
Date: Sat, 01 Apr 2000 00:00:00 -0000	[thread overview]
Message-ID: <387F7A4E.85093CF7@Sun.COM> (raw)
Message-ID: <20000401000000.M56_fwzA6f7-atsD7W00QIIZvJeukQFDbuayHUML_SI@z> (raw)

Hi. I would like to get some advice about cross-compiling GCC for a Sun
Solaris host, and PowerPC target.

We have already installed gcc-2.95.2, with its complete source.

Here are some issues I need to address:
- should the cross-compiler be installed in the same dir as the native
compiler, and then be called with a special flag, or should it be
installed in a whole new directory altogether?

- should we use flags such as 'with-as' 'with-ld' and 'with-headers' to
specify directories for the assembler, linker, and headers, or is it
best to leave these out, and then specify which assemblers, linkers etc
to use as flags when we actually use the cross-gcc? - If we use the
flags when we actually run gcc, we would have more flexibility in trying
different assemblers and linkers, or have the option of not linking at
all, right? - Or would you have the same flexibility by installing it
with default directories, and then overriding the defaults if you choose
to do so when running gcc?

- does it matter what version of 'make' one uses? ie whether we use
'make' from cc or from GNU?

- I've never used binutils before. What is it all about? Does it have
any useful tools for profiling the code (analyzing it to produce a
function call graph, for example)?
-----------------------------

On a related note, I notice that GCC has tools to make it compatible
with certain embedded operating systems. Are there any tools for pSOS? I
couldn't find any...

Thanks,
Jay Lulla
jay.lulla@ebay.sun.com

             reply	other threads:[~2000-01-14 11:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-14 11:35 JAY LULLA [this message]
2000-04-01  0:00 ` JAY LULLA
2000-01-14 12:50 Moore, Jason
2000-01-14 13:25 ` Doug Evans
2000-04-01  0:00   ` Doug Evans
2000-04-01  0:00 ` Moore, Jason

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=387F7A4E.85093CF7@Sun.COM \
    --to=jay.lulla@sun.com \
    --cc=crossgcc@sourceware.cygnus.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=hsing.yuan@ebay.sun.com \
    --cc=jay.lulla@ebay.sun.com \
    --cc=swamin@ebay.sun.com \
    /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).