On Monday 03 June 2002 07:31, Keith Owens wrote:

> Added kbuild-2.5-common-2.5.20-1 and kbuild-2.5-i386-2.5.20-1, upgrade
> to 2.5.20.  No core changes.

I needed the small patch below to get the kernel to link in my configuration,
trivial port of the changed Makefile.

For the s390 architecture, I have made an updated patch that I'm sending 
in a seperate mail. The changes are:
- include jiffies_64 support in vmlinux.lds.S
- change asm-offsets.h generation as discussed
- update comments

I also noticed a minor problem: When you forget the '/' at the end of
KBUILD_OBJTREE, weird things can happen. For example, some .tmp_* files are 
not created in OBJTREE, but one level higher and 'make oldconfig' starts 
compiling right after finishing the config.
This problem has been present in older versions as well but maybe noone ever
noticed because shows up only when you give the KBUILD_OBJTREE as a make 
parameter, not as an environment variable.

[broken] make KBUILD_OBJTREE=/tmp/obj -f Makefile-2.5
[works]  make KBUILD_OBJTREE=/tmp/obj/ -f Makefile-2.5
[works]  KBUILD_OBJTREE=/tmp/obj make -f Makefile-2.5

Arnd <><

--- linux-2.5.20-kbuild-s390/drivers/acpi/Makefile.in.orig      Mon Jun  315:50:57 2002
+++ linux-2.5.20-kbuild-s390/drivers/acpi/Makefile.in   Mon Jun  3 15:51:01 2002
@@ -15,7 +15,7 @@
 select(CONFIG_ACPI_BUTTON      button.o)
 select(CONFIG_ACPI_EC          ec.o)
 select(CONFIG_ACPI_FAN         fan.o)
-select(CONFIG_ACPI_PCI         pci_root.o pci_link.o)
+select(CONFIG_ACPI_PCI         pci_root.o pci_link.o pci_irq.o pci_bind.o)
 select(CONFIG_ACPI_POWER       power.o)
 select(CONFIG_ACPI_PROCESSOR   processor.o)
 select(CONFIG_ACPI_THERMAL     thermal.o)

_______________________________________________________________

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

_______________________________________________
kbuild-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kbuild-devel

Reply via email to