Ruben Van Boxem added the comment:
Paul,
Thank you for your serious take on the issue.
I'm Ruben, a long-time contributor and 3-ish year toolchain builder for
MinGW-w64. I originally helped patching Qt 4.5/4.6 so that it worked with
MinGW-w64 on 64-bit Windows.
I can help liaison between
Ruben Van Boxem added the comment:
Paul,
OK, I understand your point of view. As you say, there is no single MinGW
community, nor a guiding body that takes these decisions. If you're not willing
to choose one, all I can say is this: it will probably not matter which version
you choose (all
Ruben Van Boxem added the comment:
Checking for a compiler's file name is stupid. Native Windows gcc is just
gcc.exe, Cygwin native GCC is also gcc. Some have a lot of toolchains in
PATH at the same time. That's not the right way to handle this kind of thing
Ruben Van Boxem vanboxem.ru...@gmail.com added the comment:
Does anyone have more official documentation?
The commit I linked to has the full option removal at October 7 2010 (see the
fifth item in the changelog entry). Any GCC (major) version released after that
will have it completely
Ruben Van Boxem vanboxem.ru...@gmail.com added the comment:
I can confirm the option has been removed. For those that don't want to believe
a random person's comment on a bugtracker, here's the commit:
http://repo.or.cz/w/official-gcc.git/commit/2637551aa9314c46cf4205d435ab5e8944e9ac8a
2011/5/15 Ruben Van Boxem vanboxem.ru...@gmail.com:
2011/5/15 Ruben Van Boxem vanboxem.ru...@gmail.com:
2011/5/15 Ruben Van Boxem vanboxem.ru...@gmail.com:
2011/5/14 Doug Evans d...@google.com:
On Sat, May 14, 2011 at 2:09 AM, Ruben Van Boxem
vanboxem.ru...@gmail.com wrote:
2011/5/14 Doug
2011/5/14 Doug Evans d...@google.com:
On Sat, May 14, 2011 at 2:09 AM, Ruben Van Boxem
vanboxem.ru...@gmail.com wrote:
2011/5/14 Doug Evans d...@google.com:
On Thu, May 12, 2011 at 9:19 AM, Ruben Van Boxem
vanboxem.ru...@gmail.com wrote:
(now in plain-text as required by gdb mailing list
2011/5/15 Ruben Van Boxem vanboxem.ru...@gmail.com:
2011/5/14 Doug Evans d...@google.com:
On Sat, May 14, 2011 at 2:09 AM, Ruben Van Boxem
vanboxem.ru...@gmail.com wrote:
2011/5/14 Doug Evans d...@google.com:
On Thu, May 12, 2011 at 9:19 AM, Ruben Van Boxem
vanboxem.ru...@gmail.com wrote
2011/5/15 Ruben Van Boxem vanboxem.ru...@gmail.com:
2011/5/15 Ruben Van Boxem vanboxem.ru...@gmail.com:
2011/5/14 Doug Evans d...@google.com:
On Sat, May 14, 2011 at 2:09 AM, Ruben Van Boxem
vanboxem.ru...@gmail.com wrote:
2011/5/14 Doug Evans d...@google.com:
On Thu, May 12, 2011 at 9:19 AM
2011/5/14 Doug Evans d...@google.com:
On Thu, May 12, 2011 at 9:19 AM, Ruben Van Boxem
vanboxem.ru...@gmail.com wrote:
(now in plain-text as required by gdb mailing list)
Hi,
I am currently trying to integrate Python support into my toolchain
build (including GDB of course
2011/5/14 Eli Zaretskii e...@gnu.org:
Date: Sat, 14 May 2011 11:09:13 +0200
From: Ruben Van Boxem vanboxem.ru...@gmail.com
Cc: g...@sourceware.org, python-list@python.org
1. Check hardcoded path; my suggestion would be gdb
executable/../lib/python27
2. If this fails to find the necessary
Hi,
I am currently trying to integrate Python support into my toolchain build
(including GDB of course). It is a sysrooted binutils+GCC+GDB+mingw-w64
toolchain.
I currently have the basic setup working: I can link gdb with my manually
generated import lib to the python dll from the official
(now in plain-text as required by gdb mailing list)
Hi,
I am currently trying to integrate Python support into my toolchain
build (including GDB of course). It is a sysrooted
binutils+GCC+GDB+mingw-w64 toolchain.
I currently have the basic setup working: I can link gdb with my
manually
Ruben Van Boxem vanboxem.ru...@gmail.com added the comment:
Has anyone looked at this? I'm trying to build gdb with Python enabled with
mingw-w64 (Python 2.7.1 with manually created import libraries), but have to
manually define MS_WIN64 in the CFLAGS. The patch only does what's right (i.e
14 matches
Mail list logo
