From: HEISERER DANIEL <Daniel.Heiserer@bmw.de>
To: parisc-linux@lists.parisc-linux.org, debian-hppa@lists.debian.org
Subject: [parisc-linux] octave2.1_2.1.35-6_hppa
Date: Tue, 29 Jan 2002 11:18:01 +0100 [thread overview]
Message-ID: <3C5676D9.E4B26D93@bmw.de> (raw)
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.
I used the gcc-3.0.2 which was a
/usr/local/bin/gcc: ELF-64 executable object file - PA-RISC 2.0
(LP64)
and it also produced such code. Unfortunately the octave builds,
but fails immediately by trivial operations.
I am also a little be astonished about the different object files
existing
on PA-Risc. There are
/usr/local/bin/perl: PA-RISC1.1 shared executable dynamically linked
-not stripped
as well as "PA-RISC2" executables.
Honestly I have no idea what the difference between ELF-64 and PA-RISC-2
is.
Are both 64 bit.
Finally I found the debian archive for octave. So my question is:
Do you build this octave for
o linux on PA-Risc or also for
o HP-UX-11.11 ????
Is it finally 64 bit? and how did you build it.
I would appreciate any comments to my open questions.
thanks, daniel
--
Mit freundlichen Gruessen
Daniel Heiserer
--------------------------------------------------------------
Dipl.-Phys. Daniel Heiserer, BMW AG, Knorrstrasse 147, 80788 Muenchen
Abteilung EK-212
Tel.: 089-382-21187, Fax.: 089-382-42820
mailto:daniel.heiserer@bmw.de
Lageplan Standort FIZ:
http://www.stadtplandienst.de/query?ORT=M&STR=Knorrstr.&HNR=147
next reply other threads:[~2002-01-29 10:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-29 10:18 HEISERER DANIEL [this message]
2002-01-29 15:19 ` [parisc-linux] Re: octave2.1_2.1.35-6_hppa Matthew Wilcox
2002-01-29 16:12 ` 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=3C5676D9.E4B26D93@bmw.de \
--to=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.