Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Philipp Rumpf <prumpf@inwestnet.de>
To: Hugo.van.der.Kooij@caiw.nl
Cc: "Brian S. Julin" <bri@mojo.calyx.net>, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Cross compiler -- on Alpha?
Date: Wed, 15 Mar 2000 19:55:20 +0100	[thread overview]
Message-ID: <20000315195520.E673@abacus.local> (raw)
In-Reply-To: <Pine.LNX.4.10.10003151927530.21833-100000@bastion.hugo.vanderkooij.org>; from Hugo.van.der.Kooij@caiw.nl on Wed, Mar 15, 2000 at 07:30:40PM +0100

> > It might.  The only real difference between alpha and i386 to run a
> > cross-compiler on is sizeof(long), and I don't think we rely on that
> > too heavily in gcc.
> 
> Wouldn't big endian vs little endian be an issue?

PA-RISC is (usually) big-endian;  Alpha and i386 are little-endian.  Cross-
compiling from i386 works, so this shouldn't be an issue for cross-compiling
from Alpha.

	Philipp Rumpf

  parent reply	other threads:[~2000-03-15 19:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-15 11:39 [parisc-linux] ramdisk problem with ELF kernel Ulrich Strelow
2000-03-15 13:13 ` Philipp Rumpf
2000-03-15 16:16   ` [parisc-linux] Cross compiler -- on Alpha? Brian S. Julin
2000-03-15 17:26     ` Philipp Rumpf
2000-03-15 18:30       ` Hugo.van.der.Kooij
2000-03-15 18:48         ` willy
2000-03-15 18:55         ` Philipp Rumpf [this message]
2000-03-15 22:30         ` Brian S. Julin
2000-03-15 22:35           ` willy
2000-03-15 22:57           ` David Huggins-Daines
2000-03-15 16:21 ` [parisc-linux] ramdisk problem with ELF kernel Paul Bame
2000-03-15 17:28   ` [parisc-linux] need tftp boot and ELF Brian S. Julin
2000-03-15 17:46     ` willy
2000-03-15 18:26 ` [parisc-linux] ramdisk problem with ELF kernel Hugo.van.der.Kooij
2000-03-15 18:50   ` willy
2000-03-15 23:59 ` Helge Deller
2000-03-16  8:25   ` Gyula Matics

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=20000315195520.E673@abacus.local \
    --to=prumpf@inwestnet.de \
    --cc=Hugo.van.der.Kooij@caiw.nl \
    --cc=bri@mojo.calyx.net \
    --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