All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@cygnus.com>
To: David Huggins-Daines <dhd@linuxcare.com>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] untested but building 64-bit toolchain, issues/questions
Date: Thu, 06 Jul 2000 12:16:17 -0600	[thread overview]
Message-ID: <11586.962907377@upchuck> (raw)
In-Reply-To: Your message of 06 Jul 2000 14:05:39 EDT. <874s63p218.fsf@linuxcare.com>


  In message <874s63p218.fsf@linuxcare.com>you write:
  > Urgh.  Understood.  This means that the gcc tree on
  > puffin.external.hp.com CVS is quite out of date, which is sort of what
  > I expected.  I'm looking at the possibility of merging it now.
Certainly possible.  Especially if you get a tree from the releases Cygnus
made to HP.  Lots has changed since then.

  > I know Matthew Wilcox has been pushing for using 'parisc-*-linux-gnu'
  > and 'parisc64-*-linux-gnu' as the arch strings for 32 and 64 bit
  > targets, and standardising on a 'linux' dialect of assembly language
  > for both (basically 2.0 mnemonics).  What would the chances of this
  > being accepted by the binutils/gcc/autoconf maintainers be?  (should I
  > be asking this on another list? sorry...)
  > 
  > We need to standardise on these things ASAP, since we are starting to
  > build userspace, and we will be stuck with them very soon.
I would strongly recommend hppax.y[w] and hppa64 since the GNU tools already
know about those names.  Otherwise you're going to spend a lot of time
unnecessarily hacking up configure scripts.

I believe there's a list (config@gnu.org)?  Where this kind of stuff is
usually discussed.
jeff

  reply	other threads:[~2000-07-06 18:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-05 22:25 [parisc-linux] untested but building 64-bit toolchain, issues/questions David Huggins-Daines
2000-07-05 22:39 ` Jeffrey A Law
2000-07-06 14:14   ` David Huggins-Daines
2000-07-06 14:49     ` David Huggins-Daines
2000-07-06 16:30       ` Jeffrey A Law
2000-07-06 18:05         ` David Huggins-Daines
2000-07-06 18:16           ` Jeffrey A Law [this message]
2000-07-06 17:01     ` Jeffrey A Law
2000-07-06 19:01       ` Grant Grundler
2000-07-06 19:19         ` Jeffrey A Law

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=11586.962907377@upchuck \
    --to=law@cygnus.com \
    --cc=dhd@linuxcare.com \
    --cc=parisc-linux@thepuffingroup.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.