From: Joe Buck <jbuck@synopsys.com>
To: Rick Sustek <rsustek@cisco.com>
Cc: gcc@gcc.gnu.org, zack@codesourcery.com
Subject: Re: GCC target deprecation
Date: Mon, 30 Dec 2002 14:51:00 -0000 [thread overview]
Message-ID: <20021230123931.A22345@synopsys.com> (raw)
In-Reply-To: <3E08AF08.5EEFBC0A@cisco.com>; from rsustek@cisco.com on Tue, Dec 24, 2002 at 11:01:28AM -0800
On Mon, Dec 23, 2002 at 09:54:34AM -0800, Rick Sustek wrote:
> > > Still using:
> > > m68k-sun-sunos*
> > > on Sun3 hardware platform.
I wrote:
> > Interesting. Are you using current or near-current GCC releases?
> > We haven't seen any build success reports or test results for this
> > platform, and it would be nice to have some.
> >
> > I assume you are cross-compiling?
On Tue, Dec 24, 2002 at 11:01:28AM -0800, Rick Sustek wrote:
> I'm on gcc 2.95.3.
> Cross compiling from two hosts: sparc-sun-solaris2.6 and some intel
> Redhat linux host.
>
> Planning on moving into the gcc 3.* world, but was having frustrating
> time bootstrapping
> my way up the release train, just for native compiling on the
> sparc-sun-solaris2.6 host,
> and could not get any of the 3.* releases to build. Thus, that is on
> hold for me now.
[ I'm back now after the holidays ]
For 3.2.1, we have successful reports for sparc-sun-solaris2.6, both
with binutils and with native as and ld. There were some issues with
earlier 3.x releases.
> But, it is good (???) to know that I might expect build trouble for a
> cross compiler to
> the m68k-sun-sunos* target, should I be able to get to that point. ;=)
Generally speaking, anything that no one has tested for a while tends to
break, especially for older OSes that have peculiarities that must be
worked around (e.g. SunOS). The good news, however, is that the breakage
often has a trivial fix. So don't lose hope if you get a failure, instead
please ask for help, showing the exact failure that you get. Also,
cross-compilation tends to be a bit tricky, and some things are different
now; better to ask for help than to suffer alone.
> BTW, consider my level of interest in the m68k-sun-sunos* target to be
> relatively low,
> i.e., I have no crucial business case hinging on its continued support
> in gcc. My interest
> is higher in the more generic m68k-* targets: m68k-elf and m68k-aout,
> which are not
> on your current list of deprecation targets.
Joel Sherill reported successful builds for m68k-elf and m68k-coff for
gcc 3.2.1 + binutils 2.13.1; see
http://gcc.gnu.org/ml/gcc/2002-12/msg00326.html
He didn't say anything about m68k-aout, perhaps because he had no
interest.
prev parent reply other threads:[~2002-12-30 20:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-23 10:33 Rick Sustek
2002-12-23 17:57 ` Joe Buck
[not found] ` <3E08AF08.5EEFBC0A@cisco.com>
2002-12-30 14:51 ` Joe Buck [this message]
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=20021230123931.A22345@synopsys.com \
--to=jbuck@synopsys.com \
--cc=gcc@gcc.gnu.org \
--cc=rsustek@cisco.com \
--cc=zack@codesourcery.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).