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: Tue, 24 Oct 2000 11:13:44 +0200 [thread overview]
Message-ID: <39F552C8.91856B0C@wanadoo.fr> (raw)
In-Reply-To: 14837.11341.207379.903189@argo.linuxcare.com.au
Paul Mackerras wrote:
>
> I'll be interested to hear how people go with it. I'll check the
> changes into the bitkeeper linuxppc_2_2 tree within the next day or
> so. If it goes OK I'll send the patch to Alan for inclusion in
> 2.2.18.
I have a hard time trying to compile this.
First of all, you don't use CONFIG_MAGIC_SYSRQ, do you? If you do, you
find that there is confusion over whether it is "ppc_md.kbd_sysrq_xlate"
or "ppc_md.ppc_kbd_sysrq_xlate", and then there are a couple of
"SYSRQ_KEY = 0x69" instead of "ppc_md.SYSRQ_KEY = 0x69".
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:
arch/ppc/kernel/head.o: In function `setup_disp_bat':
arch/ppc/kernel/head.o(.text+0x47ea): undefined reference to `disp_BATL'
arch/ppc/kernel/head.o(.text+0x47fa): undefined reference to `disp_BATU'
arch/ppc/kernel/kernel.o: In function `motopenpic_to_irq':
arch/ppc/kernel/kernel.o(.text+0x8a28): undefined reference to
`openpic_to_irq'
The latter is found at many places. Further:
arch/ppc/kernel/kernel.o: In function `pmac_pic_init':
arch/ppc/kernel/kernel.o(.text.init+0x7f96): undefined reference to
`open_pic_do_IRQ'
arch/ppc/kernel/kernel.o(__ksymtab+0x388): undefined reference to
`pci_dev_io_base'
arch/ppc/kernel/kernel.o(__ksymtab+0x390): undefined reference to
`pci_dev_mem_base'
arch/ppc/kernel/kernel.o: In function `sys_call_table':
arch/ppc/kernel/kernel.o(.data+0x3198): undefined reference to
`sys_pciconfig_read'
arch/ppc/kernel/kernel.o(.data+0x319c): undefined reference to
`sys_pciconfig_write'
drivers/macintosh/macintosh.o: In function `pmu_ioctl':
drivers/macintosh/macintosh.o(.text+0x2b14): undefined reference to
`get_backlight_level'
drivers/macintosh/macintosh.o: In function `via_pmu_init':
drivers/macintosh/macintosh.o(.text.openfirmware+0x5ec): undefined
reference to `register_backlight_controller'
I may have some weird config options (in particular, CONFIG_PMAC_PBOOK=y
when I don't have a Pbook), but they worked before in 2.2.17, and they
work in 2.4.0.
--
Martin
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-10-24 9:13 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 [this message]
2000-10-24 11:11 ` Paul Mackerras
2000-10-24 23:21 ` Martin Costabel
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=39F552C8.91856B0C@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).