detlefsend at enovatia.com
Thu Aug 7 17:50:10 CEST 2003
On 8/4/03 3:15 PM, "Skip Montanaro" <skip at pobox.com> wrote:
Thanks Skip for the following....
> I think Modules/Setup is about it. If I had to do this today, here's what
> I'd do.
> 1. Starting from a clean source tree, run the 'script' command to get
> a log of the session in a file named 'typescript'.
> 2. Exit the script session.
> 3. Run the usual 'configure ; make' commands.
> 4. Edit Modules/Setup, uncommenting those modules which you want built
> statically. Many are simple and require no extra compile or link
> flags. For others, use the build commands found in the typescript
> file to identify -I..., -L..., and -l... flags. Obviously, omit or
> modify any flags that would be used to generate a shared library
> (-shared, -Bshared, -fPIC, etc).
> 5. Run 'make clean ; make'
> 6. Test the resulting executable.
> 7. Repeat steps 4-6 as necessary.
> 8. Congratulate yourself on a job well done and buy yourself a beer.
I'm to the point where two modules are not found by freeze:
Warning: unknown modules remain: pcre strop
There is no mention of these in my Modules/Setup file. Any suggestions.
More information about the Python-list