On 2014-02-14 15:43, Hiroshi Umemoto wrote: > >> This isn't a change to swig but to the binding subports. What >> arch-specific files do you see them installing? > > As you pointed out, the subports seem to install no arch-specific files at > all. However, if you try to install one of the swig subports from source, a > standard compilation process for the swig executable will begin. In my case, > I failed to install the i386 version of swig-python on Lion OS.
The 'supported_archs noarch' only refers to the files being installed. The implication when using this line is that the produced binary archive can be installed on any arch. The build process is still allowed need to execute commands to generate output files. >From a quick look at the files installed by swig-python, the noarch label was correct. Rainer _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
