linux-kernel - Re: PATCH: ARCH in builddeb

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]

Message-Id: <200909161619.33461.elendil@planet.nl>
Date:	Wed, 16 Sep 2009 16:19:31 +0200
From:	Frans Pop <elendil@...net.nl>
To:	Wei Chong Tan <weichong78@...il.com>
Cc:	sam@...nborg.org, max@...o.at, linux-kernel@...r.kernel.org
Subject: Re: PATCH: ARCH in builddeb

On Monday 14 September 2009, Frans Pop wrote:
> On Monday 14 September 2009, Wei Chong Tan wrote:
> > I was using "make ARCH=i386 deb-pkg" in the kernel on a 64bit machine
> > and found out that the .deb package created was _amd64.deb.
> > Consequently, I modify the builddeb script to take into account the
> > ARCH environment variable.
>
> Thanks for the patch. I'd like to give it some testing though as I fear
> it may break one other use case that currently somehow does work
> correctly.
>
> If I cross-compile for arm with EABI set in the config, the script
> currently correctly generates an armel package (probably through
> dpkg-cross).
>
> Possibly your change would override that and change it to arm. I don't
> know for sure it will go wrong, but it does need testing. I'll let you
> know.

Yes, it is as I feared. Your patch results in an "arm" package when I do a 
cross-build for "armel" (for which I must of course set ARCH to "arm" as 
armel is not a valid Linux architecture).

I agree that being able to build i386 on amd64 is a valuable option and I 
have actually run into that issue myself (and solved it by building in an 
i386 chroot).

A possible solution could be to check that CROSS_COMPILE is *not* set, but 
I'm not sure if that would be the correct solution. Input from others on 
this would be welcome.

Cheers,
FJP
--
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/