From: Ullas Ponnadi <uponnadi@cup.hp.com>
Cc: parisc-linux@thepuffingroup.com
Subject: [parisc-linux] Building the PA-RISC 2.0 kernel with the GCC tool chain
Date: Fri, 11 Feb 2000 11:18:57 -0800 [thread overview]
Message-ID: <38A460A1.42E46FC6@cup.hp.com> (raw)
In-Reply-To: 200002111838.NAA12763@vorlon.dynacan.org
John Curry and myself have been looking at the PA-RISC 2.0 Port. Here are
some things that I have tried using the latest GCC tool chain.
- I have been able to build an ELF-64 binary using the tool chain. The tools
that
I have used are:
- gcc version 2.9-hppa-991112
- GNU ld version 2.9-hppa-991112 (with BFD 2.9-hppa-991112)
- GNU Make version 3.77
- I have used a bare bone kernel for the build.
- Most of the assembly files are stubbed out since the assembler directives and
in
some cases, assembly tricks do not work on the 64 bit architecture.
- The purpose of the build was to test the tool chain and deal with any 64 bit
issues,
so no tests have been done:-).
Hope this information is useful for anyone trying to work on a PA-RISC 2.0
Port.
Ullas
prev parent reply other threads:[~2000-02-11 21:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-11 18:38 [parisc-linux] Some PA-RISC 2.0 Gotchas Christopher Neufeld
2000-02-11 19:18 ` Ullas Ponnadi [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=38A460A1.42E46FC6@cup.hp.com \
--to=uponnadi@cup.hp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox