Rainer Orth wrote: > [EMAIL PROTECTED] writes: > > >>> ... which would be a nightmare if you regularly had to build them from >>> source just to be able to build ON. SFW alone takes about as long to >>> compile as ON, and (unlike ON) requires a 64-bit machine to build. >>> >> When we started with the Solaris 64 bit builds, you needed to >> set an environment variable "WYOMING_TOOLS" to point to a linker >> capable of building 64 bit binaries. Later you could just point it >> to the installed tools. >> > > Unfortunately, fixing this (CR 6401063) is hard since in general autoconf > tests require that test binaries can run on the build machine. Everything > else is handled as cross-compilation, which isn't well supported by most > packages. I've done a couple of fixes to avoid the build failures where > possible, but didn't yet get around to submitting them. > > Rainer > _______________________________________________ > opensolaris-code mailing list > [email protected] > http://mail.opensolaris.org/mailman/listinfo/opensolaris-code >
In my opinion, if a library is required to build ON, then it should probably be moved into ON. This might mean that libxml should be moved. If it were moved, then the autoconf code could be removed and replaced with hardcoded Makefiles. It probably wouldn't be too hard. This is the way the BSDs have been doing thing things for years now. :-) (Except they call "on" either "base" or "core" and the other bits go into "pkgsrc" or "ports".) -- Garrett D'Amore, Principal Software Engineer Tadpole Computer / Computing Technologies Division, General Dynamics C4 Systems http://www.tadpolecomputer.com/ Phone: 951 325-2134 Fax: 951 325-2191 _______________________________________________ opensolaris-code mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
