| 6 | |
| 7 | Edit, Dec 25 : I see *another* build problem with PIL and freetype. but I could diagnose it only by creating a new sage tree and git'ing !#15661 directly : adding #15561 to an already compiled tree does not force recompilation of PIL. |
| 8 | |
| 9 | The problem : |
| 10 | |
| 11 | {{{ |
| 12 | [ ... ] |
| 13 | |
| 14 | gcc -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -I/home/charpent/sagebis/sage/local/include/freetype2 -IlibImaging -I/home/charpent/sagebis/sage/local/include -I/usr/include -I/home/charpent/sagebis/sage/local/include/python2.7 -c _imagingft.c -o build/temp.linux-x86_64-2.7/_imagingft.o |
| 15 | _imagingft.c:68:31: fatal error: freetype/fterrors.h: Aucun fichier ou dossier de ce type |
| 16 | #include <freetype/fterrors.h> |
| 17 | ^ |
| 18 | compilation terminated. |
| 19 | error: command 'gcc' failed with exit status 1 |
| 20 | |
| 21 | [ ... ] |
| 22 | }}} |
| 23 | This happens twice (PIL attemps compilation with and without Tkinter support). This is caused by the fact that the directory containing freetype headers is no longer local/include/freetype but local/include/freetype2. |
| 24 | |
| 25 | Since Pillow is now accepted in the next sage, my plan is : |
| 26 | |
| 27 | * start a new tree |
| 28 | * fetch the Pillow branch (for rebase ?) |
| 29 | * fetch !#15561 and adjust it. |
| 30 | |
| 31 | Your thoughts ? |