for:
#include <stdio.h>
int main(int argc, char *argv[])
{
printf("I am %s\n", argv[0]);
return 0;
}
built like this:
gcc -o test test.c -mconsole -lmsvcr90
I get this:
Runtime Error!
Program: C:...
R6034
An application has made an attempt to load the C runtime library incorrectly.
Please contact the application's support team for more information.
This is with msvcr90.dll in copied to some path other than \WINDOWS\WinSxS . If
I try adding WinSxS to the path it is just ignored. I gather it has something
to do with a missing manifest.
Lenard
Quoting Brian Fisher <[EMAIL PROTECTED]>:
> I'm curious - what exactly is the error you are getting?
>
> On Fri, Apr 25, 2008 at 11:03 PM, Lenard Lindstrom <[EMAIL PROTECTED]> wrote:
>
> > Maybe Python 2.6 extensions will compile with MinGW and distutils. I don't
> > know
> > enough about manifests to know why they exist, let alone how to use them.
> > But
> > building with Msys is another matter. Clearly the necessary manifest files
> > don't exist in this case. That leaves compiling the Pygame for Python 2.6
> > dependencies with Visual Studio 2008, a process that will take
> > considerable
> > time to set up, or link them against msvcrt.dll (like Internet Explorer).
> >
> > Lenard
> >
> >
> > Quoting Brian Fisher <[EMAIL PROTECTED]>:
> >
> > > dang - I didn't even know they had another new runtime...
> > >
> > > according to this post though, this should already be fixed?
> > > http://mail.python.org/pipermail/python-dev/2007-November/075473.html
> > >
> > >
> > > On Fri, Apr 25, 2008 at 4:17 PM, Lenard Lindstrom <[EMAIL PROTECTED]>
> > wrote:
> > >
> > > > I thought while I had the chance I would try linking the Pygame
> > > > dependencies against msvcr90.dll using MinGW. It failed. The
> > msvcr90.dll
> > > > that Python 2.6 uses is connected to a manifest. I don't know anything
> > > about
> > > > them. And neither do the unix build tools ./configure and make. So
> > when
> > > > ./configure goes about creating its first little test program the
> > program
> > > > fails because Windows prevents msvcr90.dll from loading. No manifest
> > file.
> > > > And this is with XP yet. So I am stumped. I am putting this particular
> > > side
> > > > excursion on indefinite hold. I just post this as a forewarning about
> > what
> > > > lies ahead.
> >
> >
> >
>
--
Lenard Lindstrom
<[EMAIL PROTECTED]>
