Problem with gcc4.7 and call_once

[Brian D. McGrew]

Well I had to port install gcc48 to build gcc-4.8.1 from source.  Using
/usrŠgcc didn't get me there.  So installing port gcc48, building
gcc-4.8.1 from source in ~ and installing over the top of port installed
gcc worked (backing up /opt/local of course).  Circular for sure, but
effective.

I did port edit gcc48 and added the --enable-libstdcxx-threads (which
Jeremy tells me are on by default) and reinstalled libstdcxx and gcc-48
using -s so it all got rebuilt but this did not fix the problem.  So far
the only thing  that's fixing my problem is the hand cranked gcc built
with gcc-mp-48.  

If I had a clue what to diff, I'd open an issue right now.

-brian
-- 


Brian McGrew
brian at visionpro.com




On 8/9/13 1:02 PM, "Ryan Schmidt" <ryandesign at macports.org> wrote:

>
>On Aug 9, 2013, at 14:36, Brian D. McGrew <brian at visionpro.com> wrote:
>
>> 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.
>
>Obviously, MacPorts cannot use gcc48 to build gcc48 (circular
>dependencies are not supported). But if that portion of the above is not
>essential, then what would be most helpful is if you would file a bug
>report for this problem in our issue tracker, Cc the port's maintainer,
>and attach a unified diff that fixes the portfile.
>
>