RE: scripts/mod/file2alias.c cross compile problem
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: "Andreas Schwab" <schwab@xxxxxxx>
- Subject: RE: scripts/mod/file2alias.c cross compile problem
- From: "Luck, Tony" <tony.luck@xxxxxxxxx>
- Date: Thu, 2 Aug 2007 10:40:14 -0700
- Cc: <trenn@xxxxxxx>, "Adrian Bunk" <bunk@xxxxxxxxx>, "Sam Ravnborg" <sam@xxxxxxxxxxxx>, "Jan Dittmer" <jdi@xxxxxxx>, "Len Brown" <lenb@xxxxxxxxxx>, "Linus Torvalds" <torvalds@xxxxxxxxxxxxxxxxxxxx>, "Andrew Morton" <akpm@xxxxxxxxxxxxxxxxxxxx>, <linux-acpi@xxxxxxxxxxxxxxx>, <linux-kernel@xxxxxxxxxxxxxxx>, <linux-ia64@xxxxxxxxxxxxxxx>
- In-reply-to: <jewswdvqpt.fsf@xxxxxxxxxxxxx>
- Thread-index: AcfVI0Nnai62keSmSVSgd7IchnqiEAACE2aQ
- Thread-topic: scripts/mod/file2alias.c cross compile problem
>>> struct acpi_device_id {
>>> __u8 id[ACPI_ID_LEN];
>>> + __u8 dummy[FILLUP_LEN];
>>> kernel_ulong_t driver_data;
>>> };
>>
>> What's so special about this structure that we get an error?
>
> It's special because it's a device_id structure, and those structures
> must come out identical using either the host or the target compiler.
That didn't help me understand. Are device_id structures visible
in some user-level API? If so, then I can see why they'd need to
be the same (but then I'd be confused why this structure uses a
"kernel_ulong_t" type).
-Tony
-
To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Index of Archives]
[Linux Kernel]
[Sparc Linux]
[DCCP]
[Linux ARM]
[Yosemite News]
[Linux SCSI]
[Linux x86_64]
[Linux for Ham Radio]