I tried compiling the bootloader with the version of waf in r1609, and
got this:
PS C:\Users\b\p\tst\d\pyinstaller-trunk-r1609m\source> python waf
configure build install
Windows-32bit detected
Checking for program gcc or cc : C:\MinGW\bin\gcc.exe
Checking for program cpp : C:\MinGW\bin\cpp.exe
Checking for program ar : C:\MinGW\bin\ar.exe
Checking for program ranlib : C:\MinGW\bin\ranlib.exe
Checking for program python : C:\Python27\python.exe
Checking for Python version : 2.7.1
Checking for library python27 : yes
Checking for program python2.7-config : not found
Checking for program python-config-2.7 : not found
Checking for custom code : Could not find the python
development headers
C:\Users\b\p\tst\d\pyinstaller-trunk-r1609m\source\wscript:111: error:
the configuration failed (see 'C:\\Users\\b\\p\\tst\\d\\pyinstaller-
trunk-r1609m\\source\\build\\config.log')
PS C:\Users\b\p\tst\d\pyinstaller-trunk-r1609m\source>
The last bit of C:\\Users\\b\\p\\tst\\d\\pyinstaller-trunk-r1609m\
\source\\build\\config.log is:
----------------------------------------
Checking for program python2.7-config
find program=['python2.7-config'] paths=[] var='PYTHON_CONFIG'
-> ''
----------------------------------------
Checking for program python-config-2.7
find program=['python-config-2.7'] paths=[] var='PYTHON_CONFIG'
-> ''
Include path for Python extensions (found via distutils module): 'C:\\\
\Python27\\\\include'
----------------------------------------
Checking for custom code
==>
#include "Python.h"
#ifdef __cplusplus
extern "C" {
#endif
void Py_Initialize(void);
void Py_Finalize(void);
#ifdef __cplusplus
}
#endif
int main()
{
Py_Initialize();
Py_Finalize();
return 0;
}
<==
[1/2] [32mcc: build\.conf_check_0\test.c -> build
\.conf_check_0\testbuild\default\test_1.o
[0mcc1.exe: warnings being treated as errors
..\test.c:6:7: error: 'Py_Initialize' redeclared without dllimport
attribute: previous dllimport ignored
..\test.c:7:7: error: 'Py_Finalize' redeclared without dllimport
attribute: previous dllimport ignored
['C:\\MinGW\\bin\\gcc.exe', '-Wdeclaration-after-statement', '-
Werror', '-fno-strict-aliasing', '-IC:\\\\Python27\\\\include', '..\
\test.c', '-c', '-o', 'default\\test_1.o']
command returned 'Build failed: -> task failed (err #1): \n\t{task:
cc test.c -> test_1.o}'Could not find the python development headers
I found very little on Google about this problem. I do have a
populated c:\Python27\include folder, and I don't know why it's
failing with the above error.
Brian
On Oct 7, 6:02 am, Martin Zibricky <[email protected]> wrote:
> Brian píše v Čt 06. 10. 2011 v 07:21 -0700:
>
> > Here's an example:
>
> I can confirm that your issue is related to this bug:
>
> http://www.pyinstaller.org/ticket/182
>
> If I did the following change and recompilled bootloader then your
> example seems working.
>
> Could you please recompile bootloader with the foolowing change and let
> me know if your app works then?
>
> If you want me to send you compilled bootloader with this change, let me
> know.
>
> --- source/common/launch.c (revision 1609)
> +++ source/common/launch.c (working copy)
> @@ -1296,7 +1296,7 @@
> * as subprocess, this subprocess will not fooled into thinking that
> it
> * is already unpacked.
> */
> - unsetenv("_MEIPASS2");
> + //unsetenv("_MEIPASS2");
>
> /* Iterate through toc looking for scripts (type 's') */
> while (ptoc < status->tocend) {
--
You received this message because you are subscribed to the Google Groups
"PyInstaller" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/pyinstaller?hl=en.
