Re: New ACPI diffs ready for testing

From: Marcel Moolenaar <marcel_at_xcllnt.net>
Date: Fri, 25 Apr 2003 19:25:51 -0700
On Fri, Apr 25, 2003 at 07:09:38PM -0700, Nate Lawson wrote:
> > I'll kludge around this for now, but it's probably a good idea to
> > get rid of them in the final version...
> 
> Impedance mismatch.  Some support functions are required for 0228 and some
> more for 0328.  I accidentally let a couple from 0328 slip into the 0228
> diff (where they go unused and unprototyped by the acpica code).  I'll
> regen the 0228 diff in place without them.

Yeah, I ifdef'd them out after noticing they weren't used at all.

I now got a link failure:
 
linking kernel.debug
evevent.o: In function `AcpiEvInitialize':
ACPI_ADR_SPACE_SETUP/../../../contrib/dev/acpica/evevent.c:168: undefined reference to `AcpiEvGpeInitialize'
*** Error code 1

I'll keep you posted...

> BTW, I had tried to cross-compile the acpi module and ran into a problem
> in that -mconstant-gp did not work for the i386 compiler.  Also, there is
> no rule to build acpi_wakecode.S on ia64 apparently:

You probably should be using a cross-compiler for cross-builds :-)

> > make MACHINE_ARCH=ia64
> Warning: Object directory not changed from original
> /usr/src/sys/modules/acpi
> _at_ -> /usr/src/sys
> machine -> /usr/src/sys/ia64/include
> touch opt_acpi.h
> touch opt_bus.h
> echo -n > opt_ddb.h
> awk -f _at_/tools/makeobjops.awk _at_/kern/device_if.m -h
> awk -f _at_/tools/makeobjops.awk _at_/kern/bus_if.m -h
> awk -f _at_/tools/makeobjops.awk _at_/dev/pci/pci_if.m -h
> awk -f _at_/tools/makeobjops.awk _at_/dev/pci/pcib_if.m -h
> awk -f _at_/tools/makeobjops.awk _at_/isa/isa_if.m -h
> make: don't know how to make acpi_wakecode.S. Stop
> 
> If you can help fix cross-compilation, I would appreciate it.

The acpi module does not build on ia64 at all. ACPI is non-optional
on ia64, so there's no need for a module. It may not be a bad idea
to make the module buildable for testing purposes, but it will not
be useful beyond mere building.

The best way to cross-build is by starting a cross-world, which you
then abort after the headers are installed in the object tree. This
should leave a usable set of cross-tools you can use for buildkernel.

-- 
 Marcel Moolenaar	  USPA: A-39004		 marcel_at_xcllnt.net
Received on Fri Apr 25 2003 - 17:25:53 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:05 UTC