From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: Thibaut VARENE <varenet@esiee.fr>
Cc: John David Anglin <dave@hiauly1.hia.nrc.ca>,
parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] arch/parisc/kernel/perf_asm.o not building
Date: Fri, 18 Jul 2003 12:51:29 -0300 [thread overview]
Message-ID: <20030718155128.GE1582@conectiva.com.br> (raw)
In-Reply-To: <20030718132619.524d8304.varenet@esiee.fr>
Em Fri, Jul 18, 2003 at 01:26:19PM +0200, Thibaut VARENE escreveu:
> On Fri, 18 Jul 2003 01:38:39 -0400 (EDT)
> "John David Anglin" <dave@hiauly1.hia.nrc.ca> wrote:
>
> > > 2.6-bk (i.e. latest linus tree in master.kernel.org), using the
> > > xc-20020118.tar.bz2 cross compiler (latest):
> >
> > This doesn't work as it doesn't have all the necessary parisc-linux
> > patches. Use the parisc-linux source.
> >
>
> fyi, there's a 3.0.4 xc for i686 (as well as many other platform) on
> pateam:
> http://pateam.esiee.fr/download.html
Thanks, I'm updating it now, just for the record, another thing I've noticed:
===== drivers/char/vt.c 1.53 vs edited =====
--- 1.53/drivers/char/vt.c Fri Jun 20 17:16:20 2003
+++ edited/drivers/char/vt.c Fri Jul 18 12:45:57 2003
@@ -2371,7 +2371,7 @@
/*
* Turn the Scroll-Lock LED off when the console is started
*/
-static void con_start(struct tty_struct *tty)
+void con_start(struct tty_struct *tty)
{
int console_num;
if (!tty)
Will download the diff Willy pointed out and try again with the new xc.
- Arnaldo
prev parent reply other threads:[~2003-07-18 15:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-18 4:14 [parisc-linux] arch/parisc/kernel/perf_asm.o not building Arnaldo Carvalho de Melo
2003-07-18 4:26 ` [parisc-linux] " Arnaldo Carvalho de Melo
2003-07-18 4:58 ` John David Anglin
2003-07-18 5:38 ` [parisc-linux] " John David Anglin
2003-07-18 11:26 ` Thibaut VARENE
2003-07-18 15:51 ` Arnaldo Carvalho de Melo [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=20030718155128.GE1582@conectiva.com.br \
--to=acme@conectiva.com.br \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=varenet@esiee.fr \
/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