Did you happen to clean mod_perl2 first? The attached log indicates your old 5.18 build is simply being resumed: until cleaned it will continue building with 5.18 which is not what you want.
:info:build /usr/bin/clang -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_www_mod_perl2/mod_perl2/work/mod_perl-2.0.7/src/modules/perl -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_www_mod_perl2/mod_perl2/work/mod_perl-2.0.7/xs -I/opt/local/include/apr-1 -I/opt/local/include/apr-1 -I/opt/local/include -I/opt/local/apache2/include -pipe -Os -fno-common -DPERL_DARWIN -I/opt/local/include -no-cpp-precomp -fno-strict-aliasing -fstack-protector -I/opt/local/include -I/opt/local/lib/perl5/5.18.2/darwin-thread-multi-2level/CORE -DMOD_PERL -DMP_COMPAT_1X -DDARWIN -DSIGPROCMASK_SETS_THREAD_MASK -DDARWIN_10 -O3 \ On Mar 30, 2014, at 17:43, Murray Eisenberg <[email protected]> wrote: > % sudo port -ns upgrade --force mod_perl2 > ---> Computing dependencies for mod_perl2 > ---> Building mod_perl2 _______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
