[meta-xilinx] gcc-cross-initial libgcc configure/compilation problems

Thu Nov 28 16:37:28 PST 2013

Hi Martin,

Sorry I should have been a little bit more specific, unfortunately it is bitbake that is causing the patch failures, so you will need to switch poky back to dora as well as meta-xilinx.

Regards,
Nathan

> -----Original Message-----
> From: Martin Townsend [mailto:martin.townsend at xsilon.com]
> Sent: Friday, November 29, 2013 1:47 AM
> To: Nathan Rossi; Elvis Dowson
> Cc: meta-xilinx at yoctoproject.org
> Subject: Re: [meta-xilinx] gcc-cross-initial libgcc configure/compilation
> problems
> 
> Hi Nathan,
> 
> Thanks for the info, I've pulled the latest code and found that it fails
> to patch the Microblaze Toolchain as you said it would.  I switched to the
> dora branch and this also failed to patch with the same error so I'll
> await the fix and if there's anything I can do please let me know.
> 
> Best Regards,
> Martin.
> 
> 
> 
> On 28/11/13 15:14, Nathan Rossi wrote:
> 
> 
> 	Hi Martin,
> 
> 	The error you see with attr has been fixed in the newest poky (make
> sure you do a pull). There was a bug in the attr release tarball that
> prevents the build from using a newer configure/config.sub.
> 
> 	Also regarding the unrecognized options warning, you can safely
> ignore them, the attr bug also causes these warnings (as the older
> ./configure does not support them).
> 
> 	However for master the microblaze toolchain is broken (well
> technically not the toolchain but the recipe), you may have noticed a
> message to meta-xilinx mailing list that went out earlier about patch
> failure. Still working on resolving it. However if you are after a
> functional build you should use dora for the time being.
> 
> 	Regards,
> 	Nathan
> 
> 
> ________________________________
> 
> 	From: meta-xilinx-bounces at yoctoproject.org [meta-xilinx-
> bounces at yoctoproject.org] on behalf of Martin Townsend
> [martin.townsend at xsilon.com]
> 	Sent: Friday, 29 November 2013 12:16 AM
> 	To: Elvis Dowson
> 	Cc: meta-xilinx at yoctoproject.org
> 	Subject: Re: [meta-xilinx] gcc-cross-initial libgcc
> configure/compilation problems
> 
> 
> 	Hi Elvis,
> 
> 	Thanks for the info, this is what I was starting to do so it was
> good to see I was on the right lines.  I have created myself a layer and
> added an ml605-microblazeel.conf file to setup my machine and I have got a
> lot further.   I've been tripped up by the attr package which gives me the
> following output:
> 
> 	| configure: WARNING: unrecognized options: --disable-silent-rules,
> --disable-dependency-tracking, --with-libtool-sysroot, --enable-nls
> 	| checking build system type... x86_64-pc-linux-gnu
> 	| checking host system type... Invalid configuration `microblazeel-
> poky-linux': machine `microblazeel-poky' not recognized
> 	| configure: error: /bin/bash ./config.sub microblazeel-poky-linux
> failed
> 
> 
> 	So it looks like I've got a bunch of unrecognized options which are
> Warnings but the error occurs as it doesn't understand microblazeel-poky-
> linux.  Looking through the work area I see that config.sub supports
> microblaze but not microblazeel.  So I hacked config.sub to add in
> microblazeel and it has built.  Is this the correct thing to do or should
> I be telling configure to use microblaze-poky-linux.
> 
> 	Best Regards,
> 	Martin.
> 
> 
> 	On 28/11/13 12:45, Elvis Dowson wrote:
> 
> 
> 		Hi Martin,
> 
> 		On Nov 28, 2013, at 4:04 PM, Martin Townsend
> <martin.townsend at xsilon.com> wrote:
> 
> 
> 			I did try and received the following error
> 			ERROR:  OE-core's config sanity checker detected a
> potential misconfiguration.
> 			   Either fix the cause of this error or at your own
> risk disable the checker (see sanity.conf).
> 			   Following is the list of potential problems /
> advisories:
> 
> 			   Please set a valid MACHINE in your local.conf or
> environment
> 
> 			So I tried microblaze as well as microblazeel for the
> MACHINE with no joy.
> 
> 
> 
> 		If you look at the meta-xilinx repository, it currently lists
> the following machines
> 
> 		http://git.yoctoproject.org/cgit/cgit.cgi/meta-
> xilinx/tree/conf/machine
> 
> 		kc705-trd-microblazeel.conf
> 		qemumicroblaze.conf
> 		qemuzynq.conf
> 		zc702-zynq7.conf
> 		zc706-zynq7.conf
> 		zedboard-zynq7.conf
> 
> 		If you're using an ML605 board, try to create a new ml605-
> microblazeel.conf file with the following contents, but obtain the correct
> *.dts and xparameters.h file and .kconfig.cfg file from say the Petalinux
> distribution.
> 
> 		Filename: ml605-microblazeel.conf
> 
> 		#@TYPE: Machine
> 		#@NAME: ml605-microblazeel
> 		#@DESCRIPTION: Machine support for Xilinx ML605 Evaluation
> Board.
> 		#
> 
> 		TARGET_CPU = "microblazeel"
> 		MACHINE_FEATURES := ""
> 
> 		require conf/machine/include/tune-microblaze.inc
> 		require conf/machine/include/machine-xilinx-default.inc
> 		TUNE_FEATURES_tune-microblaze += "v8.50 little-endian barrel-
> shift pattern-compare reorder multiply-low"
> 
> 		SERIAL_CONSOLE = "115200 ttyS0"
> 
> 		# Note: Obtain the correct files for the ML605
> 		#MACHINE_DEVICETREE := "ml605/ml605-microblazeel.dts"
> 		#MACHINE_KCONFIG := "ml605/ml605-microblazeel.kconfig.cfg"
> # try using the kernel defaults first
> 		#MACHINE_XPARAMETERS := "ml605/ml605-
> microblazeel.xparameters.h"
> 
> 
> 		Then set your machine to ml605-microblazeel, and you should be
> able to build a toolchain.
> 
> 		However, the kernel build process will fail if you dont have
> the correct dts and xparameters.h file, you might need to tweak the *.dts,
> .kconfig.cfg and xparameters.h file, till you get it right, to build the
> kernel and execute in on the board.
> 
> 		You should do it in two steps,
> 		- build the toolchain using yocto
> 		- build the kernel, using the xilinx linux kernel repository,
> and the kernel to boot properly. After that, you can include the dts, and
> xparameters.h files, and have yocto build the kernel.
> 
> 		Best regards,
> 
> 		Elvis Dowson
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 	This email and any attachments are intended for the sole use of the
> named recipient(s) and contain(s) confidential information that may be
> proprietary, privileged or copyrighted under applicable law. If you are
> not the intended recipient, do not read, copy, or forward this email
> message or any attachments. Delete this email message and any attachments
> immediately.
> 
> 
> 
> 