From: Martin Costabel <costabel@wanadoo.fr>
To: paulus@linuxcare.com.au
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: 2.2.18-pre17 candidate
Date: Wed, 25 Oct 2000 01:21:52 +0200 [thread overview]
Message-ID: <39F61990.6F29D8E@wanadoo.fr> (raw)
In-Reply-To: 14837.28240.588096.139146@argo.linuxcare.com.au
Paul Mackerras wrote:
>
> Martin Costabel writes:
>
> > First of all, you don't use CONFIG_MAGIC_SYSRQ, do you? If you do, you
>
> Not usually, no. How did you guess? :-)
>
> > Having fixed the corresponding 6 or 8 files, compilation went through to
> > the end, but in the final "ld ... -o vmlinux", there were dozens of
> > undefined symbols, like:
Sorry for the noise, my fault. I had some files in arch/ppc/kernel left
over from earlier rsync from the (now dead) hq.fsmlabs.com server that
were newer than your corresponding ones. After a careful cleanup (and
the sysrq stuff patch), it compiles now, and boots, and works. Including
new input layer like on 2.4.0 (tested only with ADB keyboard and ADB
keycodes). And MOL (patched for 603). And MAGIC_SYSRQ :-)
--
Martin
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-10-24 23:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-24 6:29 2.2.18-pre17 candidate Paul Mackerras
2000-10-24 7:32 ` Andreas Tobler
2000-10-24 11:06 ` Paul Mackerras
2000-10-24 11:53 ` Andreas Tobler
2000-10-24 9:13 ` Martin Costabel
2000-10-24 11:11 ` Paul Mackerras
2000-10-24 23:21 ` Martin Costabel [this message]
2000-10-24 20:18 ` Olaf Hering
2000-10-24 16:15 ` Is the difference in IRQ maps between 2.4/2.2 intentional? Vitaly Luban
2000-10-24 20:38 ` Matt Porter
2000-10-25 5:01 ` 2.2.18-pre17 candidate Paul Mackerras
2000-10-25 13:38 ` linux-pmac-benh off (WAS: " Benjamin Herrenschmidt
2000-10-30 15:39 ` Chris Leishman
2000-10-30 18:13 ` Michael Schmitz
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=39F61990.6F29D8E@wanadoo.fr \
--to=costabel@wanadoo.fr \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@linuxcare.com.au \
/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.