I’d like to test 5.2, and I don’t want to un-install 4.8.4 because it works
with our current code base. I know that 4.9.0 had problems with our code and so
I might want to re-try that with the latest version.
My major question is in the subject: Can I install both at the same time? I
know that
I saw the bug closed, and I'm not seeing anything in port update.
Should I?
David
On Aug 9, 2013, at 1:24 PM, Jeremy Huddleston Sequoia jerem...@macports.org
wrote:
We don't really need to continue this thread. I have reproduced the issue
and think I have a workaround. Feel free
So why does building the code from scratch with the --enable-libstdcxx-threads
flag work, and not when using the port or when the port file configuration adds
that option?
Jeremy has shown that the MP version does not work for std::call_once, and
gcc.org has results showing that it works fine
Can I get Brian and me on the open bug ticket as cc members?
David
On Aug 9, 2013, at 1:24 PM, Jeremy Huddleston Sequoia jerem...@macports.org
wrote:
We don't really need to continue this thread. I have reproduced the issue
and think I have a workaround. Feel free to file a ticket
McGrew
br...@visionpro.com
On 8/7/13 9:22 AM, David Barto dba...@visionpro.com wrote:
Same results with gcc 4.8 +universal
649_ rm threading ; make threading
/opt/local/bin/g++-mp-4.8 -std=c++11 -g threading.cpp -o threading
650_ ./threading
Segmentation fault: 11
Though I have
...@visionpro.com
On 8/7/13 9:22 AM, David Barto dba...@visionpro.com wrote:
Same results with gcc 4.8 +universal
649_ rm threading ; make threading
/opt/local/bin/g++-mp-4.8 -std=c++11 -g threading.cpp -o threading
650_ ./threading
Segmentation fault: 11
Though I have not made any
br...@visionpro.com
On 8/7/13 9:22 AM, David Barto dba...@visionpro.com wrote:
Same results with gcc 4.8 +universal
649_ rm threading ; make threading
/opt/local/bin/g++-mp-4.8 -std=c++11 -g threading.cpp -o threading
650_ ./threading
Segmentation fault: 11
Though I have
Sequoia jerem...@macports.org
wrote:
On Aug 8, 2013, at 8:04, David Barto dba...@visionpro.com wrote:
Interesting result of the build of libstdcxx
gcc 4.8 rebuilt because I removed the /opt/local/lib/libstdc++.6.dylib.
...
When complete however /opt/local/lib/gcc48 has a symbolic link
in __once_proxy ()
#1 0x7fff8b36eff0 in pthread_once ()
#2 0x00011195 in ?? ()
(gdb)
-brian
--
Brian McGrew
br...@visionpro.com
On 8/7/13 9:22 AM, David Barto dba...@visionpro.com wrote:
Same results with gcc 4.8 +universal
649_ rm threading ; make threading
Both are compiled/configured the same way, +universal, with whatever debug
symbols from a standard install.
David
On Aug 8, 2013, at 8:52 AM, Jeremy Huddleston Sequoia jerem...@macports.org
wrote:
On Aug 8, 2013, at 8:43, David Barto dba...@visionpro.com wrote:
The size
that will force these changes into the system?
David
On Aug 8, 2013, at 8:52 AM, Jeremy Huddleston Sequoia jerem...@macports.org
wrote:
On Aug 8, 2013, at 8:43, David Barto dba...@visionpro.com wrote:
The size of the version compiled with 4.8:
2864 -rwxr-xr-x 1 root wheel 1463728 Aug
Huddleston Sequoia jerem...@macports.org
wrote:
On Aug 8, 2013, at 13:53, Jeremy Huddleston Sequoia
jerem...@macports.org wrote:
On Aug 8, 2013, at 12:58, David Barto dba...@visionpro.com wrote:
It appears that the following is missing from the configuration for
libstdc
I've just run my monthly port update and I decided that it was time to use
std::thread/std::future to execute things in the background.
The problem is that in std::future is a call to std::call_once and that call
crashes my code:
(gdb) where
#0 0x in ?? ()
#1
On Aug 7, 2013, at 8:44 AM, Jeremy Huddleston Sequoia jerem...@apple.com
wrote:
Can you provide a reproducible test case?
Compile line is:
/opt/local/bin/g++-mp-4.7 -std=c++11 -g threading.cpp -o threading
The following is the result of the execution of the code.
Program received signal
Same results with gcc 4.8 +universal
649_ rm threading ; make threading
/opt/local/bin/g++-mp-4.8 -std=c++11 -g threading.cpp -o threading
650_ ./threading
Segmentation fault: 11
Though I have not made any changes to libstdc++, just updated to the last
version from the port on Monday.
?
On Aug 7, 2013, at 7:32, David Barto dba...@visionpro.com wrote:
I've just run my monthly port update and I decided that it was time to use
std::thread/std::future to execute things in the background.
The problem is that in std::future is a call to std::call_once and that call
crashes my
with a version that supports 'ctags'.
What is the process of doing that?
David
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
br...@visionpro.com
Subject: Re: pcb: [51393] branches/6.4/libs/gem_communication/gemcfg.c:
Remove debug
Date: June 3, 2013 7:41:46 AM PDT
To: David Barto dba...@visionpro.com
ImageMagick @6.8.0-7_2+q16 (active)
-brian
--
Brian McGrew
br...@visionpro.com
On 6/3/13
org.macports.destroot
org.macports.install
Now what? Is this a new bug in the system?
David
David Barto
dba...@visionpro.com
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports
1 root admin 82080 Apr 2 05:43 /opt/local/bin/gdbus
8 -rwxr-xr-x 1 root admin 1352 Apr 2 05:43 /opt/local/bin/gdbus-codegen
David Barto
dba...@visionpro.com
___
macports-users mailing list
macports-users@lists.macosforge.org
https
Ah, right.
Thanks,
David
David Barto
dba...@visionpro.com
On Apr 9, 2013, at 6:18 AM, Ryan Schmidt wrote:
On Apr 9, 2013, at 07:33, David Barto wrote:
I check the information on gdb and know that I'd like to update from the
MacOS version, which is quite old.
After
fails because the /usr/lib/libstdc++.so is found first. What can I do to find
the proper /opt/local/lib/libstdc++.so?
I've not modified the search paths in any way, I'm just trying to compile a c++
program using the newer standard features.
David
David Barto
dba...@visionpro.commailto:dba
22 matches
Mail list logo