[issue13011] Frozen programs require the original build directory in order to run.

2022-03-23 Thread Irit Katriel


Irit Katriel  added the comment:

Closing, please reopen or create a new issue if this is still a problem after 
all these years.

--
stage: needs patch -> resolved
status: pending -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue13011] Frozen programs require the original build directory in order to run.

2022-01-24 Thread Irit Katriel


Irit Katriel  added the comment:

This seems very outdated, can we close it?

--
nosy: +iritkatriel
resolution:  -> out of date
status: open -> pending

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue13011] Frozen programs require the original build directory in order to run.

2011-10-17 Thread Éric Araujo

Éric Araujo mer...@netwok.org added the comment:

Thanks for the report.  In 2.7 and 3.2, Python initialization was changed to 
use the new sysconfig module, which depends on the sysconfig.cfg file.  freeze 
needs to special-case the sysconfig module in its detection code to include the 
cfg file.

Do you want to work on a patch?

--
nosy: +eric.araujo
stage:  - needs patch

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13011
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue13011] Frozen programs require the original build directory in order to run.

2011-09-19 Thread Malcolm Purvis

New submission from Malcolm Purvis malc...@purvis.id.au:

In Python 2.7.2, Linux executables built with freeze.py will only run on the 
machine that contains the original build directory.  This defeats the purpose 
of having frozen programs.  This problem did not exist in Python 2.5.

The following steps reproduce the problem:

1) Build a copy of python:

$ tar -xf Python-2.7.2.tar.bz2
$ cd Python-2.7.2
$ ./configure --prefix=`pwd`/install
$ make
$ make install

2) In another directory, build a frozen program:

$ echo 'print Hello World' hello.py
$ ~/src/Python-2.7.2/python ~/src/Python-2.7.2/Tools/freeze/freeze.py hello.py
$ make
$  ./hello 
Hello World

Copy the binary to another machine:

$ $ ./hello 
Traceback (most recent call last):
  File /home/malcolmp/src/Python-2.7.2/Lib/site.py, line 563, in module
  File /home/malcolmp/src/Python-2.7.2/Lib/site.py, line 545, in main
  File /home/malcolmp/src/Python-2.7.2/Lib/site.py, line 278, in 
addusersitepackages
  File /home/malcolmp/src/Python-2.7.2/Lib/site.py, line 253, in 
getusersitepackages
  File /home/malcolmp/src/Python-2.7.2/Lib/site.py, line 243, in getuserbase
  File /home/malcolmp/src/Python-2.7.2/Lib/sysconfig.py, line 520, in 
get_config_var
  File /home/malcolmp/src/Python-2.7.2/Lib/sysconfig.py, line 419, in 
get_config_vars
  File /home/malcolmp/src/Python-2.7.2/Lib/sysconfig.py, line 287, in 
_init_posix
IOError: invalid Python installation: unable to open 
/home/malcolmp/src/Python-2.7.2/install/lib/python2.7/config/Makefile (No such 
file or directory)

--
components: Demos and Tools
messages: 144315
nosy: malcolmp
priority: normal
severity: normal
status: open
title: Frozen programs require the original build directory in order to run.
type: behavior
versions: Python 2.7

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13011
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com