All of lore.kernel.org
 help / color / mirror / Atom feed
From: "C.Newport" <crn@netunix.com>
To: sparclinux@vger.kernel.org
Subject: Re: Was:  Problems with bridging on Sparc64
Date: Tue, 03 Feb 2004 23:02:40 +0000	[thread overview]
Message-ID: <200402032302.40799.crn@netunix.com> (raw)
In-Reply-To: <200402031553.44155.crn@netunix.com>

On Tuesday 03 February 2004 9:21 pm, Ben Collins wrote:
> > We should take pity on the developer of some nice 64 bit application
> > who tries to get his install scripts to work on all common Linux
> > distributions. Portability between distributions is a major headache
> > for application developers.
>
> With Debian, I think the goal is to make dpkg recognize the ABI aswell
> as the arch.  The binaries will go in standard places (/bin, etc..).
> Packages that support this will have ABI independent files go in a
> seperate package (config files, headers, gifs, etc...) if needed, and
> supply binary packages that are built for each ABI (sparc32, v9,
> sparc64, etc..same goes for x86, x86-64 and hppa/hppa64).

Thanks, the Debian method makes a lot of sense.
BTW, you have just reminded me of another issue :-

You mention both sparc v9 and sparc64. 
AIUI v9 is the Sun Ultrasparc and sparc64 is the slightly different
Fujitsu processor. We seem to refer to both under the confusing
sparc64 header, but I do not see much testing happening on Fujitsu
stuff. Am I misunderstanding the situation or should we consider
getting the naming sorted out ?.
Does anyone even have a Sparc64 (Fujitsu) machine working ?.


  parent reply	other threads:[~2004-02-03 23:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-03 15:53 Was: Problems with bridging on Sparc64 C.Newport
2004-02-03 20:18 ` Ben Collins
2004-02-03 21:21 ` Ben Collins
2004-02-03 21:26 ` C.Newport
2004-02-03 23:02 ` C.Newport [this message]
2004-02-03 23:17 ` Ben Collins
2004-02-03 23:20 ` David S. Miller
2004-02-04  0:14 ` C.Newport
2004-02-04  8:01 ` Baurjan Ismagulov
2004-02-04 13:46 ` Ben Collins

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=200402032302.40799.crn@netunix.com \
    --to=crn@netunix.com \
    --cc=sparclinux@vger.kernel.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 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.