public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@cygnus.com>
To: Chris Dulya <Christopher.Dulya@sema.es>
Cc: gcc@gcc.gnu.org
Subject: Re: Port to Stratus FTX on PA-RISC 1.1
Date: Thu, 29 Jun 2000 08:38:00 -0000	[thread overview]
Message-ID: <8525.962292319@upchuck> (raw)
In-Reply-To: <395AF871.4865FBD4@sema.es>

  In message < 395AF871.4865FBD4@sema.es >you write:
  > 
  > Hi, 
  > 
  > I made port of gcc 2.95.2 (including all languages) to the
  > system Stratus FTX 3.4 with PA-RISC 1.1 or 2.0 processors.
  > The port is not to complicated and only involves the addition
  > and modification of a few files (See list below).  The new 
  > files are copies of existing files that I wanted to separate
  > out to keep the changes that I made isolated.
  > Because gas is not ready for the system and I did not port it, 
  > gcc can not compile code with debugging info.
  > 
  > Are you interested?  
Possibly.  However, much of the code you're twiddling has changed since
gcc-2.95.2; you will need to update your patches to work with the current
development sources.

There's other stuff (copyright assignments & employer disclaimers) that you
will need to fill out before we can do anything with your changes.

http://gcc.gnu.org/contribute.html

  > gcc-2.95.2/gcc/java/Makefile.in
  > gcc-2.95.2/Makefile.in
This worries me.  New ports should not need to modify those files.


  > This email is confidential and intended solely for the use of the individua
  > l to whom it is addressed. Any views or opinions presented are solely those
  >  of the author and do not necessarily represent those of Sema Group. 
  > If you are not the intended recipient, be advised that you have received th
  > is email in error and that any use, dissemination, forwarding, printing, or
  >  copying of this email is strictly prohibited. If you have received this em
  > ail in error please notify it to Sema Group sae Helpdesk by telephone on nu
  > mber
Err, is this really reasonable to include on a message sent to a public list
that is archived for the world to see?

jeff

      parent reply	other threads:[~2000-06-29  8:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-29  0:17 Chris Dulya
2000-06-29  1:11 ` Martin v. Loewis
2000-06-29  8:38 ` Jeffrey A Law [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=8525.962292319@upchuck \
    --to=law@cygnus.com \
    --cc=Christopher.Dulya@sema.es \
    --cc=gcc@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).