In case anyone is interested, you the following to build gcc-4.8.1 from source using gcc-mp-48:
CC=/opt/local/bin/gcc-mp-4.8 CXX=/opt/local/bin/g++-mp-4.8 ../configure --prefix=/opt/local --build=x86_64-apple-darwin12 --enable-languages=c,c++,objc,obj-c++,lot,fortran,java --libdir=/opt/local/lib/gcc48 --includedir=/opt/local/include/gcc48 --infodir=/opt/local/share/info --mandir=/opt/local/share/man --datarootdir=/opt/local/share/gcc-4.8 --with-local-prefix=/opt/local --with-system-zlib --disable-nls --program-suffix=-mp-4.8 --with-gxx-include-dir=/opt/local/include/gcc48/c++/ --with-gmp=/opt/local --with-mpfr=/opt/local --with-mpc=/opt/local --with-ppl=/opt/local --with-cloog=/opt/local --enable-cloog-backend=isl --disable-cloog-version-check --enable-stage1-checking --enable-lto --enable-libstdcxx-time --with-as=/opt/local/bin/as --with-ld=/opt/local/bin/ld --with-ar=/opt/local/bin/ar --with-bugurl=https://trac.macports.org/newticket --with-pkgversion='MacPorts gcc48 4.8.1_1+universal' --enable-libstdcxx-threads A make, make check and make install and you're golden. -brian -- Brian McGrew br...@visionpro.com On 8/9/13 8:17 AM, "Jeremy Huddleston Sequoia" <jerem...@macports.org> wrote: > >On Aug 9, 2013, at 6:27, Brian D. McGrew <br...@visionpro.com> wrote: > >> Well I could be going in the wrong direction, I'm not the foremost >>expert >> on ports yet, but what I do know is this: >> >> If I port edit gcc48 and add --enable-libstdcxx-threads and then port >> install -s gcc48, when I run gcc -v I do see the option that I just >>added. >> No question, the option IS there. But the test program still doesn't >>run. > > >Yes, I would expect there to be no change in behavior since >--enable-libstdcxx-threads is on by default (thus your adding it has no >effect other than to show it in 'gcc -v' > >> If I rebuild gcc-4.8.1 from source by hand using the same configuration >> options from gcc-mp -v and add --enable-libstdcxx-threads at >>configuration >> time and do a make install over top of the existing gcc-mp, everything >> works fine. >> >> Now I'm really confused. > >Yes, something is different between your out-of-tree-build and your >in-tree build. I'll try to repro your working case and then bisect the >two. > >It would be great if someone without GPL3phobia could look at this. It's >probably rather simple to triage with source access, but at least having >a working and broken build configurations from the same sources will let >me bisect the build configurations. > >Thanks, >Jeremy > _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users