Hello List!

Okay, mystery solved.  A bogus PYTHONHOME environment variable
was defined.

(I had installed an application that used python on a removable drive.
I was one of those download and run a small web-installer application,
so I never really knew what the install process entailed.  It defined
PYTHONHOME pointing to the generally absent removable drive, a
detail I hadn't noticed.

Why not just "download this file and unzip it into a directory of your
choice, and define the following environment variable to point to that
directory"?  You know, kind of like mingw-w64 does...)

Anyway, I removed (renamed, actually) the PYTHONHOME variable,
and now gdb works just fine.  Although having gdb break because of
the bad PYTHONHOME variable does seem a little fragile.

On Fri, Oct 28, 2011 at 2:04 PM, Ruben Van Boxem
<[email protected]> wrote:
> Op 28 okt. 2011 19:03 schreef "K. Frank" <[email protected]> het
> volgende:
>> ...
>> >> I'd like to float this by you all again...
>> >>
>> >> Is there some way I can fix my gdb problem?
>> >> ...
> ...
> Apart from this, I would advise against GCC 4.7. It's still experimental,
> and for c++11, it doesn't really change much. I plan to release another
> toolchain build one of these days, if you want I could also do another GCC
> 4.7, but I don't see the pressing need for it ;-)

Well, I'm just doing this for fun -- nothing important -- so I think I'll stick
with your fun 4.7, std::thread build.

Besides, if I were to revert to an earlier, less experimental build, how
would I be able to complain about Ruben's wacky build?  Where would
the fun in that be?

> Ruben

Thanks to all who helped.


K. Frank

------------------------------------------------------------------------------
Get your Android app more play: Bring it to the BlackBerry PlayBook 
in minutes. BlackBerry App World&#153; now supports Android&#153; Apps 
for the BlackBerry&reg; PlayBook&#153;. Discover just how easy and simple 
it is! http://p.sf.net/sfu/android-dev2dev
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Reply via email to