On Thu, Jan 04, 2018 at 11:55:00AM +1100, David Gibson wrote: > On Wed, Jan 03, 2018 at 10:51:23AM -0600, Rob Herring wrote: > > On Tue, Jan 2, 2018 at 9:55 PM, David Gibson > > <david@xxxxxxxxxxxxxxxxxxxxx> wrote: > > > On Tue, Jan 02, 2018 at 09:29:14PM -0600, Kyle Evans wrote: > > >> On Tue, Jan 2, 2018 at 8:58 PM, David Gibson > > >> <david@xxxxxxxxxxxxxxxxxxxxx> wrote: > > >> > Fwiw, some years ago I did a bunch of work to get dtc to compile and > > >> > pass the tests on FreeBSD. Working out of the box on *BSD is > > >> > something I'd like it to have. Unfortunately, because I can't easily > > >> > test on a BSD machine, the BSD support tends to bitrot rather rapidly. > > >> > > >> > > >> Happy to hear this. =) You're not too far off, fortunately. > > > > > > Good to hear. > > > > > >> This, the > > >> alloca header situation, and an -ldl in tests/Makefile.tests are the > > >> only obstacles to being able to do a simple "gmake && gmake check" > > >> here. I've submitted patches for the first two, and as of r320872 [1] > > >> we provide a libdl on -HEAD. > > > > > > Ok sounds good. I had a look at the tests using -ldl and it looks > > > like they couldn't easily be adapted to avoid it. However, I'd be ok > > > with logic to skip those tests if libdl isn't available, if you want > > > to broaden support to older releases. > > > > > > At the moment dtc seems to be just teetering on the edge of being > > > complex enough to need some sort of configuration system (whether it > > > be hand-rolled scripts, autoconf or whatever). So far I've been > > > avoiding adding such a thing, because that introduces a bunch of > > > problems of its own: hand rolled scripts are a pain to maintain, > > > autoconf is ugly as sin, pretty much anything else is nonstandard and > > > liable to introduce a bunch of extra dependencies. But, I might have > > > to bite the bullet at some point. > > > > What about meson? All the cool kids are using it now. > > Heh, hadn't heard of that one. Too busy maintaining vital > infrastructure to follow what the cool kids are doing. Wait, no, I went to a talk about that once, and it did look pretty nice. Never had time or headspace to really do anything with it, though. Plus it would introduce Python as a build dep. Not really a problem for dtc per se, but given that libfdt is supposed to be embeddable in weird limited firmware environments, I really want to keep the build deps to a minimum. -- David Gibson | I'll have my music baroque, and my code david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_ | _way_ _around_! http://www.ozlabs.org/~dgibson
Attachment:
signature.asc
Description: PGP signature