On Thu, Jul 1, 2010 at 2:00 AM, Paarvai Naai wrote:
> Hi Ozkan,
>
> Sorry to bug you, but can you give a little more explanation on how
> libtool is used by the configure script for -w64- support and why not
> having this fix will break things?
>
Libtool < 2.2.6/2.2.7 may not detect w64 libraries
On 7/1/2010 11:36, Paarvai Naai wrote:
> Hi Jon,
>
> Ah, it looks like a name mangling problem.
>
> /usr/local/gcc/x86_64-windows-gcc/bin/x86_64-windows-nm hello.gcc.o
> b .bss
> d .data
> r .rdata
> t .text
> T _w
On 7/1/2010 10:16, Paarvai Naai wrote:
> Hi again,
>
> Sorry for the multiple emails on this, but I forgot to mention the following:
>
> I am using upstream binutils-2.20.1, gcc 4.5.0, and
> mingw-w64-v1.0-20100604 snapshot.
>
> Also, the g++ compilation works if I use "main" instead of "wmain" and
On 7/1/2010 10:21, Paarvai Naai wrote:
> As I have mentioned in some recent emails, I am building my mingw-w64
> toolchain using upstream binutils-2.20.1, gcc 4.5.0, and
> mingw-w64-v1.0-20100604 snapshot. The host is i386-linux and the
> target is x86_64-w64-mingw32 with multilib support.
>
> I a
As I have mentioned in some recent emails, I am building my mingw-w64
toolchain using upstream binutils-2.20.1, gcc 4.5.0, and
mingw-w64-v1.0-20100604 snapshot. The host is i386-linux and the
target is x86_64-w64-mingw32 with multilib support.
I am running into a strange auto-import issue when co
Hi again,
Sorry for the multiple emails on this, but I forgot to mention the following:
I am using upstream binutils-2.20.1, gcc 4.5.0, and
mingw-w64-v1.0-20100604 snapshot.
Also, the g++ compilation works if I use "main" instead of "wmain" and
do not pass -municode.
Paarvai
On Wed, Jun 30, 2
Hi,
I have returned to using GCC 4.5.0 for my x86_64-w64-mingw32 multilib
target. I tried using the -municode option with my build and get the
following error:
] /usr/local/gcc/x86_64-windows-gcc/bin/x86_64-windows-g++ -municode
-o hello.exe hello_win_unicode.c
/usr/local/gcc/x86_64-windows-gcc/
On Wed, Jun 30, 2010 at 4:05 PM, Paarvai Naai wrote:
> Yes, I am planning on posting my find on the GCC Bugzilla. I'm pretty
> sure it's a case of over-optimization (and a critical one at that),
> but I freely admit that I'm not an expert on the internals of GCC. :)
I have some more information
Hi Doug,
> Have you filed a bugzilla report for gcc against this bug? If it is
> an optimization wrong code bug, then it probably exists for other
> targets besides mingw32.
Yes, it's a problem across targets. I first caught it when compiling
for an x86_64-linux target.
> For example, a
> comm
Hi Ozkan,
Sorry to bug you, but can you give a little more explanation on how
libtool is used by the configure script for -w64- support and why not
having this fix will break things?
I think it might be a good general education not only for me but for
others on the group.
Thanks again,
Paarvai
On Wed, Jun 30, 2010 at 3:32 PM, Paarvai Naai wrote:
> Hi all,
>
> I am trying to build a mingw-w64 cross-compiler using the instructions
> outlined on the web.
>
> Originally I was successful in building a multilib cross-compiler
> using GCC 4.5.0, but now I want to backtrack to GCC 4.4.4. This
On Wed, Jun 30, 2010 at 10:32 PM, Paarvai Naai wrote:
> Hi all,
>
> I am trying to build a mingw-w64 cross-compiler using the instructions
> outlined on the web.
>
> Originally I was successful in building a multilib cross-compiler
> using GCC 4.5.0, but now I want to backtrack to GCC 4.4.4. This
On Thu, Jul 1, 2010 at 12:00 AM, Paarvai Naai wrote:
> Hi,
>
> I want to gain an understanding for the reasoning behind the
> "libtool_patch" function used in the "Custom toolchain builds"
> distributed by Ozkan Sezer.
>
> I don't see this mentioned in the standard cross-compiler instructions
> fo
Hi,
I want to gain an understanding for the reasoning behind the
"libtool_patch" function used in the "Custom toolchain builds"
distributed by Ozkan Sezer.
I don't see this mentioned in the standard cross-compiler instructions
found on the mingw-w64 project page:
http://sourceforge.net/apps/trac/
Hi all,
I am trying to build a mingw-w64 cross-compiler using the instructions
outlined on the web.
Originally I was successful in building a multilib cross-compiler
using GCC 4.5.0, but now I want to backtrack to GCC 4.4.4. This is
because I found an optimization bug in GCC 4.5.0 that results i
15 matches
Mail list logo
