From: Alberto G. <al...@ti...> - 2002-01-03 20:07:38
|
> As for determining what happens with pyallegro that it doesn't load > it's modules, you only need to have one module, it doesn't matter which > one, to know if it get's loaded or not. I have for example modified > allegro/src/linux/fbcon.c, around line 956 in function _module_init to > make the following first call: > > printf("Entering fbcon module initialization\n"); > I think I found the problem: if you uncomment line 110 of src/unix/umodules.c, and then execute this: >>> import alpy >>> alpy.allegro_init() you should get something like this: Error loading module: /usr/local/lib/allegro/4.0/alleg-vga.so: undefined symbol: _drawing_mode Error loading module: /usr/local/lib/allegro/4.0/alleg-fbcon.so: undefined symbol: empty_string Error loading module: /usr/local/lib/allegro/4.0/alleg-svgalib.so: undefined symbol: empty_string Error loading module: /usr/local/lib/allegro/4.0/alleg-dga2.so: undefined symbol: XextCreateExtension Error loading module: /usr/local/lib/allegro/4.0/alleg-esddigi.so: undefined symbol: empty_string That is, the problem is not in the path, but in the external symbols lookup. I've found a possible solution to this problem: it seems to work, but I've not tested it very much, so there might be some pitfalls. Anyway, you can get it from CVS. Of course, tell me if something goes wrong: at the moment all the examples should work. Alberto Griggio |