current bk ipmi build fix

current bk ipmi build fix

Post by Oleg Droki » Thu, 26 Jun 2003 20:30:16



Hello!

   Not that I really have the hardware, but it breaks my "allyesconfig" build.
   So here is this compile fix for ipmi driver in current 2.4 bk tree.
   (I see that Alan have some similarly named fix in his tree and
    actually there is whole new version of the driver on the net somewhere,
    but it is unclear when it is planned to be pushed to 2.4 tree,
    so I'd better post this now ;) ).

Bye,
    Oleg
===== drivers/char/ipmi/ipmi_kcs_intf.c 1.3 vs edited =====
--- 1.3/drivers/char/ipmi/ipmi_kcs_intf.c       Sat May 24 01:12:48 2003

 #include <linux/acpi.h>
 /* A real hack, but everything's not there yet in 2.4. */
-#define COMPILER_DEPENDENT_UINT64 unsigned long
-#include <../drivers/acpi/include/acpi.h>
-#include <../drivers/acpi/include/actypes.h>
+#include <acpi/acpi.h>
+#include <acpi/actypes.h>
+#include <acpi/actbl.h>

 struct SPMITable {

 static unsigned long acpi_find_bmc(void)
 {
        acpi_status       status;
-       acpi_table_header *spmi;
+       struct acpi_table_header *spmi;
        static unsigned long io_base = 0;

        if (io_base != 0)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

1. hpt366.c cannot be built in current 2.4 bk snapshot

Hello!

   hpt366.c misses PCI_DEVICE_ID_TTI_HPT372N define somewhere (probably lost
   in merge with -ac). This is starting from March 24th or thereabout.
In file included from hpt366.c:70:
hpt366.h:517: `PCI_DEVICE_ID_TTI_HPT372N' undeclared here (not in a function)
hpt366.h:517: initializer element is not constant
hpt366.h:517: (near initialization for `hpt366_chipsets[5].device')
hpt366.h:526: initializer element is not constant
hpt366.h:526: (near initialization for `hpt366_chipsets[5].enablebits[0]')
hpt366.h:526: initializer element is not constant
hpt366.h:526: (near initialization for `hpt366_chipsets[5].enablebits[1]')
hpt366.h:526: initializer element is not constant
hpt366.h:526: (near initialization for `hpt366_chipsets[5].enablebits')
hpt366.h:529: initializer element is not constant
hpt366.h:529: (near initialization for `hpt366_chipsets[5]')
hpt366.h:534: initializer element is not constant
hpt366.h:534: (near initialization for `hpt366_chipsets[6]')
hpt366.c: In function `hpt_revision':
hpt366.c:183: `PCI_DEVICE_ID_TTI_HPT372N' undeclared (first use in this function)
hpt366.c:183: (Each undeclared identifier is reported only once
hpt366.c:183: for each function it appears in.)
hpt366.c: In function `init_setup_hpt366':
hpt366.c:1227: `PCI_DEVICE_ID_TTI_HPT372N' undeclared (first use in this function)
hpt366.c: At top level:
hpt366.c:1289: `PCI_DEVICE_ID_TTI_HPT372N' undeclared here (not in a function)
hpt366.c:1289: initializer element is not constant
hpt366.c:1289: (near initialization for `hpt366_pci_tbl[5].device')
hpt366.c:1289: initializer element is not constant
hpt366.c:1289: (near initialization for `hpt366_pci_tbl[5]')
hpt366.c:1290: initializer element is not constant
hpt366.c:1290: (near initialization for `hpt366_pci_tbl[6]')
make[4]: *** [hpt366.o] Error 1

Bye,
    Oleg
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

2. cannot open /dev/dsp

3. bk current build failures (xfrm.h / tpqic02.c)

4. need help

5. bk current - new module build failures

6. Restoring Session

7. fix 3c59x for current 2.5-bk

8. Cant shutdown after X!

9. fix UP links - current bk tree

10. Compile fix for current 2.5 BK.

11. nanosleep() fix for current bk

12. compile fix for dmi_scan.c in 2.4.bk-current

13. Fix for module.c in current linus-2.5 BK