The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>,
	Michael Buesch <mb@bu3sch.de>,
	Gordon Farquharson <gordonfarquharson@gmail.com>
Subject: Re: crossbuild fails in modpost
Date: Thu, 15 May 2008 21:19:26 +0200	[thread overview]
Message-ID: <482C8CBE.2060101@gmail.com> (raw)
In-Reply-To: <20080515174015.GA24024@uranus.ravnborg.org>

Sam Ravnborg napsal(a):
> On Thu, May 15, 2008 at 07:35:39PM +0200, Sam Ravnborg wrote:
>> On Thu, May 15, 2008 at 07:12:34PM +0200, Jiri Slaby wrote:
>>> Well, let's fix sam's email.
>>>
>>> Jiri Slaby napsal(a):
>>>> Hi,
>>>>
>>>> probably
>>>> 4ce6efed48d736e3384c39ff87bda723e1f8e041
>>>> kbuild: soften modpost checks when doing cross builds
>>>>
>>>> causes build failures on x86_64 kernel build on 32 bit machine:
>>>>
>>>> make -f /local/xslaby/hid/scripts/Makefile.modpost
>>>> YYYYYYYYYYYYYY x86_64 x86_64
>>>>  scripts/mod/modpost -m -a -o /local/xslaby/buhid/Module.symvers    -S 
>>>> -K /local/xslaby/buhid/Module.markers -M 
>>>> /local/xslaby/buhid/Module.markers   -s
>>>> XXXXXXXXXXXXXXXXXX 20: 0 (2), 4 (4), 8 (4), 12 (8)
>>>> FATAL: drivers/hid/hid-apple: sizeof(struct hid_device_id)=20 is not a 
>>>> modulo of the size of section __mod_hid_device_table=648.
>>>> Fix definition of struct hid_device_id in mod_devicetable.h
>>>> make[2]: *** [__modpost] Error 1
>>>> make[1]: *** [modules] Error 2
>>>> make: *** [sub-make] Error 2
>>>>
>>>> after sticking echo into:
>>>> __modpost: $(modules:.ko=.o) FORCE
>>>> +       @echo YYYYYYYYYYYYYY $(KBUILD_BUILDHOST) $(ARCH)
>>>>        $(call cmd,modpost) $(wildcard vmlinux) $(filter-out FORCE,$^)
>>>>
>> Your machine claims it is a x86_64 and you are building for a x86_64
>> according to the following line:
>>>> YYYYYYYYYYYYYY x86_64 x86_64
>> So it looks to me that you are building for 64 bit on a 64 bit machine.
>> So when you write:
>>  on x86_64 kernel build on 32 bit machine:
>>
>> I assume you try to say that your HOSTCC is 32 bit and your
>> kernel cc is 64 bit (or something similar).
>>
>> The commit you reference loosen up the check so we do not do the
>> check if we _know_ that the host and the target system differs.
>> The only thing I can imagine right now to solve your issue would
>> be to skip the check if we do not use the same gcc for target and host?

Well, the compiler is the same, but it's told to compile the kernel with 
-m64. It runs on x86_64 kernel and i386 userspace. It's debian i386 gcc 
package which understands x86_64 objects too. No SUBARCH option, it seems to 
default to x86_64.

> So something like this (entirely untested):
> 
> --- a/scripts/Makefile.modpost
> +++ b/scripts/Makefile.modpost
> @@ -65,7 +65,7 @@ modules   := $(patsubst %.o,%.ko, $(wildcard $(__modules:.ko=.o)))
>  # Stop after building .o files if NOFINAL is set. Makes compile tests quicker
>  _modpost: $(if $(KBUILD_MODPOST_NOFINAL), $(modules:.ko:.o),$(modules))
>  
> -ifneq ($(KBUILD_BUILDHOST),$(ARCH))
> +ifneq ($(CC),$(HOSTCC))

gcc gcc :)

>          cross_build := 1
>  endif

  reply	other threads:[~2008-05-15 19:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-15 13:44 crossbuild fails in modpost Jiri Slaby
2008-05-15 17:12 ` Jiri Slaby
2008-05-15 17:35   ` Sam Ravnborg
2008-05-15 17:40     ` Sam Ravnborg
2008-05-15 19:19       ` Jiri Slaby [this message]
2008-05-15 20:46         ` Adrian Bunk
2008-05-18 19:55           ` Jan Engelhardt
2008-05-18 20:42             ` Adrian Bunk
2008-05-18 21:15               ` Jan Engelhardt
2008-05-23 23:58                 ` David Woodhouse
2008-05-24  4:46                   ` Jan Engelhardt
2008-05-18 21:31         ` Sam Ravnborg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=482C8CBE.2060101@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=gordonfarquharson@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mb@bu3sch.de \
    --cc=sam@ravnborg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox