On Thu, Jan 14, 2016 at 11:45 AM, Albert Lee <[email protected]> wrote: > On Jan 14, 2016 9:38 AM, "Alan Somers" <[email protected]> wrote: >> >> Thanks Albert. I never would've figured that out myself. I added >> ISALIST=i386 to my env file and now I can build Illumos again. >> Shouldn't this be part of the default >> /opt/onbld/env/omnios-illumos-gate file? As it is, you can build and >> install Illumos once, but then you can't do it again. I've reproduced >> this problem again on a clean install. >> >> -Alan >> > > Hi Alan, > > The specific sequence that triggers this is if you start with a system that > includes Sun::Solaris modules for targets other than PERL_ARCH, ONU a > vanilla illumos-gate build, and then attempt to build illumos-gate on it. > illumos-omnios has been modified to build both 32- and 64-bit copies of the > modules so I would assume that is what you ONU'ed from. > > Your /usr/perl5/bin/perl (that's the Perl specifically used for the system > tools/build rather than /usr/bin/perl which can be an arbitrary version) > still expects the 64-bit modules while illumos-gate only shipped the modules > for PERL_ARCH. > > I think it is unfortunate our build system has a mild circular dependency on > the previously installed modules for build-time use of /usr/perl5. It might > be possible to satisfy it with a build for the host arch of the modules, > independent of PERL_ARCH. Upstreaming some version of the illumos-omnios > Perl changes should also avoid the problem. > > -Albert
Actually, I ONUed from the openzfs repository, which is very close to illumos-gate. I used the omnios-illumos-gate env file. I don't know enough about Illumos to fix the problem correctly, but adding ISALIST=i386 to my env file is at least good enough to let me make progress with openzfs. Thanks for all the help. -Alan _______________________________________________ developer mailing list [email protected] http://lists.open-zfs.org/mailman/listinfo/developer
