From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Grall Subject: Re: Hypervisor compilation for arm without debug=y Date: Tue, 20 Aug 2013 18:07:36 +0100 Message-ID: <5213A258.8080205@linaro.org> References: <1376925112.9708.27.camel@dagon.hellion.org.uk> <5213A069.3020400@linaro.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <5213A069.3020400@linaro.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Andrii Anisov Cc: Tim Deegan , Ian Campbell , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On 08/20/2013 05:59 PM, Julien Grall wrote: > On 08/20/2013 05:03 PM, Andrii Anisov wrote: >> BTW, >> >> > Is it a known issue? >> >> I suspect none of us has ever really used a non-debug build! >> >> >> Wiki says: >> >> Once you have a suitable cross compiler you can compile Xen with: >> $ make dist-xen XEN_TARGET_ARCH=arm32 >> CROSS_COMPILE=arm-unknown-linux-gnueabi- >> or: >> $ make dist-xen XEN_TARGET_ARCH=arm64 >> CROSS_COMPILE=aarch64-linux-gnu- >> >> >> Without debug=y flag. > > On unstable branch by default debug=y. On release branches have debug=n > by default. > > I have tried to boot a non-debug Xen on the Versatile Express: > gcc 4.8.1: Xen boots > gcc 4.6.3: Xen hangs with no output log (even early printk) I was wrong, when debug=n it's not possible to have early printk. So Xen only hangs. But, if I enable early printk (by hacking xen/arch/arm/Rules.mk) Xen is able to boot... -- Julien Grall