All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Grant Grundler <grundler@parisc-linux.org>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Parisc List <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] Re: Fw: Another problem with making things static
Date: Sat, 10 Feb 2007 23:44:24 -0800	[thread overview]
Message-ID: <20070210234424.500ed1c9.akpm__5988.99827241457$1416624282$gmane$org@linux-foundation.org> (raw)
In-Reply-To: <20070211072552.GC22248@colo.lackof.org>

On Sun, 11 Feb 2007 00:25:52 -0700 Grant Grundler <grundler@parisc-linux.org> wrote:

> > My attempt to build a working parisc cross-compiler failed, which doesn't help.
> 
> I appreciate your attempt to build parisc-linux.
> Could you post which source tree and which build command line you used?

It was maybe a year back - I spent a couple of days wrestling with
crosstool, ended up with _some_ useful crosscompilers (alpha, arm, i386,
ia64, m68k, mips, s390, sparc, sparc64 and x86_64).  parisc was one of the
ones which I gave up on but I do not have a record of what the problem was,
sorry.  It would have been a toolchain problem, not a kernel problem.

The most usual failure mode was simply inability to find any combination of
gcc/binutils/glibc which could be compiled.

> I'm pretty sure this can be fixed.
> We've used cross compilers in the past so I know it's worked before.

I say this a lot, but...  It is in the interests of arch maintainers to
help others to build cross-compilers.  If someone were to prepare a web
page (or even a script) which could be used to generate a kernel
cross-compilation environment for parisc then the parisc maintainers would
see a lot less breakage.

For one, I do allmodconfig on all architectures on all patches I get (and
that includes all the git trees).  If stuff breaks, the breaker gets to
hear about it, before it gets merged.

_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

  parent reply	other threads:[~2007-02-11  7:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070210130136.9538498b.akpm@linux-foundation.org>
     [not found] ` <20070210214309.GP12958@stusta.de>
2007-02-11  1:47   ` [parisc-linux] Re: Fw: Another problem with making things static James Bottomley
     [not found]   ` <1171158436.3373.51.camel@mulgrave.il.steeleye.com>
2007-02-11  4:19     ` Andrew Morton
     [not found]     ` <20070210201911.7a16b5f3.akpm@linux-foundation.org>
2007-02-11  7:25       ` Grant Grundler
     [not found]       ` <20070211072552.GC22248@colo.lackof.org>
2007-02-11  7:44         ` Andrew Morton [this message]
     [not found]         ` <20070210234424.500ed1c9.akpm@linux-foundation.org>
2007-02-11 16:54           ` Kyle McMartin
     [not found]           ` <20070211075738.GD22248@colo.lackof.org>
2007-02-12 11:42             ` Thibaut VARENE
     [not found]           ` <20070211165405.GA4050@athena.road.mcmartin.ca>
2007-02-12 17:15             ` Andrew Morton
2007-02-11  7:35     ` Adrian Bunk
     [not found]     ` <20070211073520.GR12958@stusta.de>
2007-02-11 15:56       ` James Bottomley

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='20070210234424.500ed1c9.akpm__5988.99827241457$1416624282$gmane$org@linux-foundation.org' \
    --to=akpm@linux-foundation.org \
    --cc=James.Bottomley@SteelEye.com \
    --cc=grundler@parisc-linux.org \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=torvalds@linux-foundation.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.