On 12.3.2012 0:54, JonY wrote:
> On 3/12/2012 04:09, Antony Riakiotakis wrote:
>> Hi, thanks for the reply!
>>
>> I know there are nightly and personal builds but was refering to
>> official builds of official releases.
>> Maybe I oversaw them but couldn't locate these in the binary list.
>>
>> Abo
On 3/12/2012 04:09, Antony Riakiotakis wrote:
> Hi, thanks for the reply!
>
> I know there are nightly and personal builds but was refering to
> official builds of official releases.
> Maybe I oversaw them but couldn't locate these in the binary list.
>
> About libraries I meant clashes in 32bit
Hi, thanks for the reply!
I know there are nightly and personal builds but was refering to
official builds of official releases.
Maybe I oversaw them but couldn't locate these in the binary list.
About libraries I meant clashes in 32bit vs 64bit libraries when
linking with the compilers as the li
Le 2012-03-11 13:16, Antony Riakiotakis a écrit :
> Hi, I am interested in trying to add support for MinGW64 in blender3D
> but I feel there are some issues that will better be answered by
> asking here.
>
> 1) What is the state of the MinGW64 compiler? Is it considered stable
> enough to support
Hi, I am interested in trying to add support for MinGW64 in blender3D
but I feel there are some issues that will better be answered by
asking here.
1) What is the state of the MinGW64 compiler? Is it considered stable
enough to support in a big project such as blender?
2) Currently it's quite a pr
Hi all,
I'm in the process of uploading a new build of GCC 4.7, with the llibstdc++
dll fix for std::thread. No more "-static" necessary anymore!
This build still has the bug preventing WebKit from building:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52465
But I couldn't wait :)
I also discove
2012/3/11 Jim Michaels
> I looked at bits/ostream_insert.h:
>
> template
> basic_ostream<_CharT, _Traits>&
> __ostream_insert(basic_ostream<_CharT, _Traits>& __out,
> const _CharT* __s, streamsize __n)
> ...
> const bool __left = ((__out.flags()
>
2012/3/9 Ruben Van Boxem :
>
> When a 32-bit multilib GCC is called to link with -m64, it should search the
> proper lib64 directory automatically, what I propose hacks around that. I
> doubt the final compiler will find its libraries once installed. Maybe I'll
> try a multilib GCC this weekend or