Ticket #1102 (closed defect: fixed)
Solaris build-chain broken
Reported by: | Dan Foster <[email protected]…> | Owned by: | desai |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | bcfg2-client | Version: | |
Keywords: | Cc: |
Description
Hi,
There are are number of problems with the Makefile provided in solaris/ that prevents bcfg2 building on Solaris 10:
- setup.py expects lib/<python-version>/site-packages/ to exist
No such file or directory: '/export/home/df3804/bcfg2-1.2.1/solaris/lib/python2.6/site-packages/test-easy-install-9272.pth' The installation directory you specified (via --install-dir, --prefix, or the distutils default setting) was: /export/home/df3804/bcfg2-1.2.1/solaris/lib/python2.6/site-packages/ This directory does not currently exist. Please create it and try again, or choose a different installation directory (using the -d or --install-dir option).
- setup.py expects lib/<python-version>/site-packages/ to be in $PYTHON_PATH
/usr/local/bin/python -E -c pass TEST FAILED: /export/home/df3804/bcfg2-1.2.1/solaris/lib/python2.6/site-packages/ does NOT support .pth files error: bad install directory or PYTHONPATH You are attempting to install a package to a directory that is not on PYTHONPATH and which Python does not read ".pth" files from. The installation directory you specified (via --install-dir, --prefix, or the distutils default setting) was: /export/home/df3804/bcfg2-1.2.1/solaris/lib/python2.6/site-packages/ and your PYTHONPATH environment variable currently contains: '' Here are some of your options for correcting the problem: * You can choose a different installation directory, i.e., one that is on PYTHONPATH or supports .pth files * You can add the installation directory to the PYTHONPATH environment variable. (It must then also be on PYTHONPATH whenever you run Python and want to use the package(s) you are installing.) * You can set up the installation directory to support ".pth" files by using one of the approaches described here: http://peak.telecommunity.com/EasyInstall.html#custom-installation-locations Please make the appropriate changes for your system and try again.
- setup.py generates an "extracted egg". i.e. lib/python2.6/site-packages/Bcfg2-1.2.1-py2.6.egg/{Bcfg2,share} instead of the more traditional lib/python2.6/site-packages/Bcfg2/ & share/
- prototype.* contains an out-of-date list files to include in the package (e.g. lib/python2.6/site-packages/Bcfg2/Server/Plugins/Packages.py does not exist anymore).
It is unclear to me if an updated prototype.bcfg2 and prototype.bcfg2-server should be provided or if these should be generated dynamically. As a first attempt, I have produced gen-prototypes.sh that produces these dynamically. Although, this could be considered more dirty than updating the prototypes manually every release.
Attached to this ticket is the following:
- Makefile - A replacement solaris/Makefile that solves the issues above and also changes the build prefix from $(PWD) to $(PWD)/build.
- gen-prototypes.sh - A script to generate suitable prototype.* files.
Attachments
Change History
Changed 11 years ago by Dan Foster <[email protected]…>
- Attachment gen-prototypes.sh added
comment:1 Changed 11 years ago by solj
- Status changed from new to closed
- Resolution set to fixed
Thanks a lot! I applied this upstream although I am unable to test. Let me know if we can clear out the other stuff in that directory.
comment:2 Changed 9 years ago by Richardheef
- Version 1.0 deleted
- Milestone Bcfg2 1.2.2 Release (Bugfix) deleted
The n muscle was the most first armoured dornier research. [https://my.swu.edu/ICS/icsfs/tabfen82.html?target=de01a38d-0d73-40c5-8be6-86dd27693780 where to get phentermine diet pills - Winds of shapes of residents, the beta and fragrance of britain tracked the oral plants over father.
Dynamically generate Solaris pkg prototype