On 2014-2-27 19:45 , Jeremy Huddleston Sequoia wrote: > I just noticed this issue with recent base. It wasn't an issue 4 weeks ago > because I had to have it working when I filed > http://trac.macports.org/ticket/42282 > > > $ sudo port -v -s destroot boost configure.compiler=macports-clang-3.3 > ---> Computing dependencies for boost. > ---> Configuring boost > Error: org.macports.configure for port boost returned: Invalid value for > configure.compiler: "macports-clang-3.3" > Warning: targets not executed for boost: org.macports.destroot > org.macports.configure org.macports.build > Please see the log file for port boost for details: > > /opt/local/var/macports/logs/_Volumes_Home_jeremy_src_macports_trunk_dports_devel_boost/boost/main.log > To report a bug, follow the instructions in the guide: > http://guide.macports.org/#project.tickets > Error: Processing of port boost failed > > > Note that the error line is: > set compiler [option configure.compiler] > ... > return -code error "Invalid value for configure.compiler: $compiler" > > so $configure.compiler is being set to "macports-clang-3.3" (quotes included). > > Has anyone been messing with how command options are read in from the command > line? It seems some quoting got messed up.
Ugh, that was probably me. I had to mess with the quoting in macports::worker_init to be able to set an option to a list. I'll see what I can do when I get a chance. - Josh _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
