public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ken Wolcott <ken.wolcott@med.ge.com>
To: "Carl B. Constantine" <cconstan@csc.uvic.ca>
Cc: gcc-help@gcc.gnu.org, crossgcc@sources.redhat.com
Subject: Re: compiling gcc for multiple targets?
Date: Wed, 31 Mar 2004 19:36:00 -0000	[thread overview]
Message-ID: <1080747990.26873.50.camel@tuba.moneng.mei.com> (raw)
In-Reply-To: <20040330232033.GA1522@csc>

Hi Carl;

  You must be mistaken about the crossgcc mailing list.  I am a
subscriber and there is recent traffic and there are some very *nice*,
*helpful* and *knowledgeable* subscribers.  There is also crosstool
(http://www.kegel.com/crosstool/), a very nice tool written by Dan
Kegel, that might help you, I'm not sure.

http://sources.redhat.com/ml/crossgcc/
crossgcc@sources.redhat.com

Ken

On Tue, 2004-03-30 at 17:20, Carl B. Constantine wrote:
> I've done a google search on this, but most of the information I found
> was old and the crossgcc list no longer exists, so I thought I would
> bring it up again.
> 
> Is there any way to compile gcc and related utils (binutils, gdb) for
> multiple targets in one binary? So I want to compile it to support both
> Solaris intel and m68hc11 in one gcc instead of having separate binaries
> for each?
> 
> If I cannot do this, but have to compile separate versions
> (--program-prefix=m6811-elf) are there any issues wrt to libraries if
> they are installed to the same place? libiberty.so for example?
> 
> Thanks in advance.


  parent reply	other threads:[~2004-03-31 15:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-31  8:17 Carl B. Constantine
2004-03-31 11:40 ` Ian Lance Taylor
2004-03-31 19:36 ` Ken Wolcott [this message]
2004-04-01  6:40   ` Bernd Jendrissek

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=1080747990.26873.50.camel@tuba.moneng.mei.com \
    --to=ken.wolcott@med.ge.com \
    --cc=cconstan@csc.uvic.ca \
    --cc=crossgcc@sources.redhat.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).