On Thu, Jul 1, 2010 at 1:07 PM, Anonymous wrote:
> Anonymous writes:
>
It's better to use -lstdc++ from same version of gcc by which the
program using it was compiled.
>>>
>>> Is it possible to determine which one?
>>
>> No. If there is an easy way I think strings(1) would show.
>
> Doh
Anonymous writes:
>>> It's better to use -lstdc++ from same version of gcc by which the
>>> program using it was compiled.
>>
>> Is it possible to determine which one?
>
> No. If there is an easy way I think strings(1) would show.
Doh,
$ strings $LOCALBASE/lib/libLLVM* | fgrep GCC
GCC: (GNU
Eitan Adler writes:
I have clang++ (devel/llvm-devel) built by g++45 and linked against
gcc45/libstdc++.so.6. It compiles your test case fine. But I'm running
9-current on amd64 so it may not be that useful.
IMO, gcc46 being a development branch is prone to miscompile and
>>> I have clang++ (devel/llvm-devel) built by g++45 and linked against
>>> gcc45/libstdc++.so.6. It compiles your test case fine. But I'm running
>>> 9-current on amd64 so it may not be that useful.
>>>
>>> IMO, gcc46 being a development branch is prone to miscompile and have bugs.
>>
>> I'm not t
Eitan Adler writes:
> On Tue, Jun 29, 2010 at 11:00 PM, Anonymous wrote:
>> Eitan Adler writes:
>>
One difference I notice between your environment and mine is that,
according
to your bug report, your program links against
/usr/local/lib/gcc46/libstdc++.so.6, while mine lin
On Tue, Jun 29, 2010 at 11:00 PM, Anonymous wrote:
> Eitan Adler writes:
>
>>> One difference I notice between your environment and mine is that, according
>>> to your bug report, your program links against
>>> /usr/local/lib/gcc46/libstdc++.so.6, while mine links against
>>> /usr/lib/libstdc++.s
Eitan Adler writes:
>> One difference I notice between your environment and mine is that, according
>> to your bug report, your program links against
>> /usr/local/lib/gcc46/libstdc++.so.6, while mine links against
>> /usr/lib/libstdc++.so.6.
>>
>> -Boris
>>
> I forgot about that. I use gcc46 to
>>> My bug report is here: http://llvm.org/bugs/show_bug.cgi?id=7489
>>>
>>> I want to know if this is my problem or a clang++ problem or a bug
>>> somewhere else.
>>>
>>
>> Works fine here:
>>
>> # uname -a
>> FreeBSD peer 8.0-RELEASE-p2 FreeBSD 8.0-RELEASE-p2 #2: Mon Feb 22 23:18:53
>> EST 2010
Boris Kochergin wrote:
Eitan Adler wrote:
Can anyone with FreeBSD 8.1-RC1 i386 or FreeBSD 8.1-RC2 i386 confirm
that the following code compiles and fails with the version of clang++
from ports?
This works with g++ and fails with clang++ for me.
Here is the original code
#include
int main()
{
Eitan Adler wrote:
Can anyone with FreeBSD 8.1-RC1 i386 or FreeBSD 8.1-RC2 i386 confirm
that the following code compiles and fails with the version of clang++
from ports?
This works with g++ and fails with clang++ for me.
Here is the original code
#include
int main()
{
std::cout << 1;
r
Can anyone with FreeBSD 8.1-RC1 i386 or FreeBSD 8.1-RC2 i386 confirm
that the following code compiles and fails with the version of clang++
from ports?
This works with g++ and fails with clang++ for me.
Here is the original code
#include
int main()
{
std::cout << 1;
return 1;
}
My bug re
11 matches
Mail list logo
