Linux PARISC architecture development
 help / color / mirror / Atom feed
From: "Carlos O'Donell Jr." <carlos@baldric.uwo.ca>
To: parisc-linux@parisc-linux.org, debian-hppa@lists.debian.org
Cc: baldric-admin@baldric.uwo.ca
Subject: [parisc-linux] Cross Compiler HOWTO - v1.2 (GCC 3.1 updates and more)
Date: Sat, 20 Apr 2002 12:02:48 -0400	[thread overview]
Message-ID: <20020420120248.D22674@systemhalted> (raw)

Parisc, Debian-hppa,

-----------------------------------------
PARISC-Linux Cross Compiler HOWTO - v1.2 
-----------------------------------------

When you're 715/50 just can't compile fast enough...

http://www.baldric.uwo.ca/~carlos/HOWTO-Parisc/

- Updated examples.
- Updated many things.
- Printable pdf version online (as requested by some people).
- GCC section includes info on building GCC 3.1 from upstream CVS.
- Fixed tpyos.

I've tested this from start to end and it's getting really easy
to roll your own tool-chain! Thank go to all the hard-working people
who make it happen :)

I tested:

GCC 3.0.2 20010905
Binutils 2.12.90.0.4-1

To build a cross-compiler from:

GCC 3.1 20020418
Binutils 2.12.90.0.1-4 (latest in debian pool)
Glibc 2.2.5-4 (latest in debian pool)

-----

If you would like to link against something then link against:
http://www.baldric.uwo.ca/HOWTO/

Which is where the document will reside soon.

You can grab a tarball of the directory at:
http://www.baldric.uwo.ca/~carlos/HOWTO-Parisc/HOWTO-Parisc.tar.gz

-----

Many thanks to Dave, Randolph and Willy who tolerate my incessant
24/7 learning... :)

Cheers,
Carlos.

             reply	other threads:[~2002-04-20 16:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-20 16:02 Carlos O'Donell Jr. [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-20 16:02 [parisc-linux] Cross Compiler HOWTO - v1.2 (GCC 3.1 updates and more) Carlos O'Donell Jr.

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=20020420120248.D22674@systemhalted \
    --to=carlos@baldric.uwo.ca \
    --cc=baldric-admin@baldric.uwo.ca \
    --cc=debian-hppa@lists.debian.org \
    --cc=parisc-linux@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox