Date: Sun, 19 May 2013 00:38:39 +1000 From: Jason Birch <jbirch@jbirch.net> To: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: Port: U-Boot for BeagleBone Message-ID: <CAA=KUhspUwuNPW13bgZVy9CKwn6Ny_Njt0AXBH27XZPEuKgaWg@mail.gmail.com> In-Reply-To: <D3F7C462-0BD5-4F20-AE32-448BB7B5855D@bsdimp.com> References: <3B16A2E5-C92B-4248-BE98-DD5C1194CB05@freebsd.org> <20130518100512.57c47fe6@bender> <B5DE3D0D-86BF-43F8-9FA2-A803B1FAABF8@freebsd.org> <D3F7C462-0BD5-4F20-AE32-448BB7B5855D@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I'm not sure how it'd work internally in the ports tree (I'm a ports consumer, not a contributor), but I'd find it weird if a U-Boot port required me to get any devel/cross-* ports if U-Boot was able to be built by Clang native to FreeBSD 9.X+ and I had Clang set as my CC, CPP, CXX. I don't know the solution to this, given that it's probably not acceptable to have a port configuration item that says "[X] Use Clang" - that sort of compiler configuration is 'external' to the ports tree, if you get my meaning. What I mean by that is it's generally a world configuration in /etc/make.conf or set as an environmental variable before invoking make, rather than explicit port configuration. It might be enough to just have a note in the ports tree that it will require devel/cross-<whatever> - I'm unaware of any other examples you could use for precedent, but I'm sure they would exist. On Sun, May 19, 2013 at 12:28 AM, Warner Losh <imp@bsdimp.com> wrote: > > On May 18, 2013, at 10:17 AM, Tim Kientzle wrote: > > > > > On May 18, 2013, at 5:05 AM, Andrew Turner wrote: > > > >> On Fri, 17 May 2013 16:22:56 -0400 > >> Tim Kientzle <kientzle@freebsd.org> wrote: > >> > >>> I'm trying to move the actual building of boot loaders out of Crochet > >>> and into FreeBSD ports. > >>> > >>> Here's the first attempt at such a port (many thanks to Diane Bruce > >>> for patiently tutoring me through this): > >>> > >>> http://people.freebsd.org/~kientzle/u-boot-beaglebone.tgz > >>> > >>> I'd appreciate any feedback: > >>> * Can you build this? > >>> * Suggestions for improving it? > >> > >> Could you try installing devel/cross-binutils and devel/cross-gcc using > >> TGTARCH=arm and TGTABI=none-eabi and using these to build u-boot? It > >> would mean the user doesn't need to have xdev set up. > > > > I'll definitely give that a try. > > > > More importantly than the user, I'm concerned about the > > package-building cluster. One of the goals here is to > > get the packages built automatically so that not everybody > > has to build the boot loaders themselves. > > > > I've not used the devel/cross-ZZZ tools before, so > > it will take me a little while to experiment. Ideally, > > the U-Boot port would just require the cross tools. > > A long time ago I was able to build u-boot using the cross-* ports... They > even have wrapper ports so you can get the write dependencies. Make sure > these are build-time dependencies not run-time dependencies and all that > will be installed will be the u-boot images... > > Warner > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAA=KUhspUwuNPW13bgZVy9CKwn6Ny_Njt0AXBH27XZPEuKgaWg>