Hi, at one point we are moving from libapr to libuv, so we would have to check if libuv's build scripts are usable too.
But what speaks for having our own configure system: What if you already have libapr/libuv installed with their dev-packages? We would just link against that without the ability to query how it was built. And even if we knew how it was built, we can't be sure that the same compiler toolchain is installed. That is basically the same trouble Perl 5 XS modules have. They query Perl 5's Config in order to get the compiler to build the module, but often the compiler used to build Perl is not installed, because it was built by a package maintainer and not by yourself. So, the question can be too: Do we want to rely on somebody else's configure that we cant tweak well? What if we want to check the given system and then want to pass options to libapr's configure? For the moment I would love to see a pull request for solaris 11. (I have a opensolaris 10 32bit somewhere in case it is needed for testing.) Cheers, FROGGS Am 24.07.2013 23:04, schrieb Andy Dougherty: > [I am sending this to perl6-compiler list because I don't know where else > to send it. Apologies if this is the wrong place.] > > I recently tried to build MoarVM on Solaris 11/x86 with Sun's compiler > suite. After cloning moarvm and running 'perl Configure.pl' , I got > the following message: > > Welcome to MoarVM! > > Checking master build settings ........................ OK > (debug: YES, optimize: no, instrument: no, clang: no) > Trying to figure out how to build on your system ...... Sorry, I'm not > sure how to build on this platform: > No recognized operating system or compiler found. found: solaris > FAILED > > It seems build/Config/BuildEnvironment.pm only knows about a few systems. > It was easy enough to hack in a 'cc' block for Solaris to get past that, > but I then noticed it went and ran an autoconf configure script down > in 3rdparty/apr. > > I was wondering . . . would it make sense to run apr's configure script > first and use those results to help set up Config/BuildEnvironment? > That way, MoarVM could avoid building yet another Configure system, > and instead could leverage the existing one that it's going to run anyway. >
