Re: CVS commit: pkgsrc/net/ocamlnet
Gary Duzan <[email protected]>
| Newsgroups | gmane.os.netbsd.devel.pkgsrc.wip.general |
|---|---|
| Message-ID | <[email protected]> |
In Message <[email protected]>, David Holland <[email protected]>wrote: =>On Sun, Jul 22, 2012 at 01:31:24PM -0400, Julio Merino wrote: => > > Keep in mind that the basic problem with Python is crosscompiling it. => > => > Why is crosscompiling Python more of a problem than crosscompiling, => > say, X11? Are there any problems with the codebase that make this => > hard? Or is it just that someone has to write the initial reachover => > Makefiles? (I certainly don't know what you are referring to.) => =>It's got a moderately nasty build system. The big problem AIUI is that =>the byte-compiled files aren't machine-independent and there's no =>support in Python for crossbuilding them. My understanding is that pyc files are Python version dependent, but machine independent, so that shouldn't be an issue. Not that there aren't others, but that shouldn't be one of them, and even if it were, it should be a straightforward workaround to use py files for a cross-build. If I manage to convert NetBSD src to Mercurial, I'd be willing to take a crack at integrating a Python release into the build system. So far I have limited success with src, miserable failure with pkgsrc, just started pkgsrc-wip, and had the xsrc conversion complete without errors. I need to evaluate the converted xsrc to see what needs to be done to get it into parity with the CVS repo and try to fix or work around the import issues with src and pkgsrc. Gary Duzan ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/