All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@debian.org>
To: HEISERER DANIEL <Daniel.Heiserer@bmw.de>
Cc: parisc-linux@lists.parisc-linux.org, debian-hppa@lists.debian.org
Subject: [parisc-linux] Re: octave2.1_2.1.35-6_hppa
Date: Tue, 29 Jan 2002 15:19:45 +0000	[thread overview]
Message-ID: <20020129151945.B3850@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <3C5676D9.E4B26D93@bmw.de>; from Daniel.Heiserer@bmw.de on Tue, Jan 29, 2002 at 11:18:01AM +0100

On Tue, Jan 29, 2002 at 11:18:01AM +0100, HEISERER DANIEL wrote:
> Hi,
> a buddy pointed me to the debian build archive,
> because I had problems building a 64-bit octave executable
> on AP-RISC-2 HP-UX-11.11.

Unfortunately, we don't support 64-bit userspace on PA/Linux yet.

> Honestly I have no idea what the difference between ELF-64 and PA-RISC-2
> is.
> Are both 64 bit.

No.  PA-RISC 2.0 introduced some new instructions, but does not have to be
64-bit.  64-bit can be useful, but it can also slow down applications.  So
it's a tradeoff.

> Do you build this octave for 
> o linux on PA-Risc or also for
> o HP-UX-11.11 ????

We don't build binaries for HP-UX.  Some people have suggested starting a
new port to build binaries for proprietary unices sch as Solaris and HP-UX,
but nobody has actually done so yet.

-- 
Revolutions do not require corporate support.

  reply	other threads:[~2002-01-29 15:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-29 10:18 [parisc-linux] octave2.1_2.1.35-6_hppa HEISERER DANIEL
2002-01-29 15:19 ` Matthew Wilcox [this message]
2002-01-29 16:12   ` [parisc-linux] octave2.1_2.1.35-6_hppa Christopher C. Chimelis
2002-01-29 18:59 ` [parisc-linux] octave2.1_2.1.35-6_hppa Grant Grundler
2002-01-29 19:58   ` John David Anglin

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=20020129151945.B3850@parcelfarce.linux.theplanet.co.uk \
    --to=willy@debian.org \
    --cc=Daniel.Heiserer@bmw.de \
    --cc=debian-hppa@lists.debian.org \
    --cc=parisc-linux@lists.parisc-linux.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.