linux-kernel - Re: crossbuild fails in modpost

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 18 May 2008 23:42:58 +0300
From:	Adrian Bunk <bunk@...nel.org>
To:	Jan Engelhardt <jengelh@...ozas.de>
Cc:	Jiri Slaby <jirislaby@...il.com>, Sam Ravnborg <sam@...nborg.org>,
	Linux kernel mailing list <linux-kernel@...r.kernel.org>,
	Michael Buesch <mb@...sch.de>,
	Gordon Farquharson <gordonfarquharson@...il.com>
Subject: Re: crossbuild fails in modpost

On Sun, May 18, 2008 at 09:55:58PM +0200, Jan Engelhardt wrote:
> 
> On Thursday 2008-05-15 22:46, Adrian Bunk wrote:
> >>
> >> 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.
> >>...
> >
> >Unless you manually fiddle with ARCH you can only build a kernel with 
> >the same 32<->64bit setting as your currently running kernel (no matter 
> >which userspace you use)...
> 
> echo -en '#!/bin/bash\nexec gcc -m32 "$@"\n' >/usr/local/bin/i386-linux-gcc
> make CC=i386-linux-gcc
> then the if($(CC),$(HOSTCC)) check should get true.

No doubt that you can work around the problem.

But that's not a solution.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/