I'll just do without VirtualBox when testing custom kernel. I really don't want to mess around with VirtualBox; I've had to rebuild me VMs several times already, and it VirtualBox uninstall/install goes wrong I'd be doing it again.
Your name and email address were configured automatically based
on your username and hostname. Please check that they are accurate.
I assume incorrect email address of no significance?
There didn't seem to be any call for <ctrl X>; did I miss something?
during
fakeroot debian/rules clean
get
cd /home/alan/Data/Downloads/Ubuntu/ToInstall/kernel-custom/ubuntu-maverick/debian/build && kernel-wedge gen-control > /home/alan/Data/Downloads/Ubuntu/ToInstall/kernel-custom/ubuntu-maverick/debian/control
Use of uninitialized value $builddep in split at /usr/share/kernel-wedge/commands/gen-control line 32, <KVERS> line 9.
Use of uninitialized value $builddep in split at /usr/share/kernel-wedge/commands/gen-control line 32, <KVERS> line 10.
during
AUTOBUILD=1 NOEXTRAS=1 fakeroot debian/rules binary-generic
get
LD arch/x86/built-in.o
WARNING: arch/x86/built-in.o(.data+0x2eb8): Section mismatch in reference from the variable powernow_driver to the function .init.text:powernow_cpu_init()
The variable powernow_driver references
the function __init powernow_cpu_init()
If the reference is valid then annotate the
variable with __init* or __refdata (see linux/init.h) or name the variable:
*_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console,
WARNING: arch/x86/built-in.o(.data+0x2f78): Section mismatch in reference from the variable longrun_driver to the function .init.text:longrun_cpu_init()
The variable longrun_driver references
the function __init longrun_cpu_init()
If the reference is valid then annotate the
variable with __init* or __refdata (see linux/init.h) or name the variable:
*_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console,
and more like it.
=====================
LD arch/x86/kernel/built-in.o
WARNING: arch/x86/kernel/built-in.o(.data+0x2eb8): Section mismatch in reference from the variable powernow_driver to the function .init.text:powernow_cpu_init()
The variable powernow_driver references
the function __init powernow_cpu_init()
If the reference is valid then annotate the
variable with __init* or __refdata (see linux/init.h) or name the variable:
*_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console,
WARNING: arch/x86/kernel/built-in.o(.data+0x2f18): Section mismatch in reference from the variable longhaul_driver to the function .init.text:longhaul_cpu_init()
The variable longhaul_driver references
the function __init longhaul_cpu_init()
If the reference is valid then annotate the
variable with __init* or __refdata (see linux/init.h) or name the variable:
*_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console,
WARNING: arch/x86/kernel/built-in.o(.data+0x2f78): Section mismatch in reference from the variable longrun_driver to the function .init.text:longrun_cpu_init()
The variable longrun_driver references
the function __init longrun_cpu_init()
If the reference is valid then annotate the
variable with __init* or __refdata (see linux/init.h) or name the variable:
*_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console
==============
LD drivers/eisa/built-in.o
WARNING: drivers/eisa/built-in.o(.data+0xb0): Section mismatch in reference from the variable pci_eisa_driver to the function .init.text:pci_eisa_init()
The variable pci_eisa_driver references
the function __init pci_eisa_init()
If the reference is valid then annotate the
variable with __init* or __refdata (see linux/init.h) or name the variable:
*_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console,
===================
CC [M] drivers/ata/sata_sil.o
/home/alan/Data/Downloads/Ubuntu/ToInstall/kernel-custom/ubuntu-maverick/drivers/ata/sata_sil.c: In function ‘sil_host_intr’:
/home/alan/Data/Downloads/Ubuntu/ToInstall/kernel-custom/ubuntu-maverick/drivers/ata/sata_sil.c:442: warning: ‘serror’ may be used uninitialized in this function
Do those count as weird error messages?
Meanwhile, build continuing.
========================
Finally, I think
sudo apt-get build-dep linux
installed masses of stuff, which I'd just as soon jettison after it's clear I no longer need it. How does one work out what to uninstall? I know how to remove a specific packages, but I think build-dep linux installed a ton of stuff?
I'll just do without VirtualBox when testing custom kernel. I really don't want to mess around with VirtualBox; I've had to rebuild me VMs several times already, and it VirtualBox uninstall/install goes wrong I'd be doing it again.
Cant tell whether build-dep linux finished.
======= ======= ======= ======= ======
git revert 58e15f5029c75b4 5adbcb25cd76a36 d26a6c4297
produced:
Your name and email address were configured automatically based
on your username and hostname. Please check that they are accurate.
I assume incorrect email address of no significance?
There didn't seem to be any call for <ctrl X>; did I miss something?
during
fakeroot debian/rules clean
get
cd /home/alan/ Data/Downloads/ Ubuntu/ ToInstall/ kernel- custom/ ubuntu- maverick/ debian/ build && kernel-wedge gen-control > /home/alan/ Data/Downloads/ Ubuntu/ ToInstall/ kernel- custom/ ubuntu- maverick/ debian/ control kernel- wedge/commands/ gen-control line 32, <KVERS> line 9. kernel- wedge/commands/ gen-control line 32, <KVERS> line 10.
Use of uninitialized value $builddep in split at /usr/share/
Use of uninitialized value $builddep in split at /usr/share/
during
AUTOBUILD=1 NOEXTRAS=1 fakeroot debian/rules binary-generic
get
LD arch/x86/built-in.o
WARNING: arch/x86/ built-in. o(.data+ 0x2eb8) : Section mismatch in reference from the variable powernow_driver to the function .init.text: powernow_ cpu_init( )
The variable powernow_driver references
the function __init powernow_cpu_init()
If the reference is valid then annotate the
variable with __init* or __refdata (see linux/init.h) or name the variable:
*_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console,
WARNING: arch/x86/ built-in. o(.data+ 0x2f78) : Section mismatch in reference from the variable longrun_driver to the function .init.text: longrun_ cpu_init( )
The variable longrun_driver references
the function __init longrun_cpu_init()
If the reference is valid then annotate the
variable with __init* or __refdata (see linux/init.h) or name the variable:
*_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console,
and more like it.
======= ======= =======
LD arch/x86/ kernel/ built-in. o
WARNING: arch/x86/ kernel/ built-in. o(.data+ 0x2eb8) : Section mismatch in reference from the variable powernow_driver to the function .init.text: powernow_ cpu_init( )
The variable powernow_driver references
the function __init powernow_cpu_init()
If the reference is valid then annotate the
variable with __init* or __refdata (see linux/init.h) or name the variable:
*_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console,
WARNING: arch/x86/ kernel/ built-in. o(.data+ 0x2f18) : Section mismatch in reference from the variable longhaul_driver to the function .init.text: longhaul_ cpu_init( )
The variable longhaul_driver references
the function __init longhaul_cpu_init()
If the reference is valid then annotate the
variable with __init* or __refdata (see linux/init.h) or name the variable:
*_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console,
WARNING: arch/x86/ kernel/ built-in. o(.data+ 0x2f78) : Section mismatch in reference from the variable longrun_driver to the function .init.text: longrun_ cpu_init( )
The variable longrun_driver references
the function __init longrun_cpu_init()
If the reference is valid then annotate the
variable with __init* or __refdata (see linux/init.h) or name the variable:
*_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console
==============
LD drivers/ eisa/built- in.o
WARNING: drivers/ eisa/built- in.o(.data+ 0xb0): Section mismatch in reference from the variable pci_eisa_driver to the function .init.text: pci_eisa_ init()
The variable pci_eisa_driver references
the function __init pci_eisa_init()
If the reference is valid then annotate the
variable with __init* or __refdata (see linux/init.h) or name the variable:
*_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console,
===================
CC [M] drivers/ ata/sata_ sil.o
/home/alan/ Data/Downloads/ Ubuntu/ ToInstall/ kernel- custom/ ubuntu- maverick/ drivers/ ata/sata_ sil.c: In function ‘sil_host_intr’: Data/Downloads/ Ubuntu/ ToInstall/ kernel- custom/ ubuntu- maverick/ drivers/ ata/sata_ sil.c:442: warning: ‘serror’ may be used uninitialized in this function
/home/alan/
Do those count as weird error messages?
Meanwhile, build continuing.
======= ======= ======= ===
Finally, I think
sudo apt-get build-dep linux
installed masses of stuff, which I'd just as soon jettison after it's clear I no longer need it. How does one work out what to uninstall? I know how to remove a specific packages, but I think build-dep linux installed a ton of stuff?