Hello, * Carsten Haitzler <[EMAIL PROTECTED]> wrote at [20060120 02:48]: > On Thu, 19 Jan 2006 18:39:35 +0100 Grzegorz Andrelczyk <[EMAIL PROTECTED]> > babbled: > > > Thu, Jan 19, 2006 at 12:56:16PM +0900 Carsten Haitzler <[EMAIL PROTECTED]> > > napisa$(D)H: > > > > > > oh - u are building debian packages of evas for install? no wonder. > > > rememebr we dont keep the packaging info up to date with the src all the > > > time - it lags behind. > > > > So it is better to do make && make install? > > well - unless you are willing to maintain and fix the debian build files - > yes. > don't expect them to "just work" - use them more of a guideline idea of how to > start building a proper package - AFTEr u know how evas builds and what it > builds and where it puts it and why it needs it/uses it. >
The last few times i had Problems with the Debian Packages it was rather a complete problem of the source then the packaging build. > > > it is there as a convenience for package maintainers to keep their > > > packaging info with the soruce it packages to save time. i have updated > > > the .spec file and i did some changes to the debian packageing stuff - but > > > its definitely NOT done properly. evas's build now makes packaging it for > > > debian proeprly HARD as u needto package each module separately but what > > > modules get built is dependnat on the dependencies found on the system > > > while the pakcages get built. > > > > > > > Here I'm a little bit lost. I'm not a package maintainer > > yet I found only dpkg-buildpackage very handy tool i > > debian\ exist and is valid. ;) > > then i suggets u install everything from source - in a prefix u can simply rm > -rf (eg /opt/e17) and add the lib dir to ld.so.conf and the bin dir to your or > the system''s default $PATH. > Hmm, the problem with this is, as far as i can see, that if you start building your new enlightenment checkout and then it fails somewhere, you've lost your working version of e17. Thats in my eyes the advantages of using the 'debian/' stuff directory if you are on a debian machine. Though you could also just build a .tar.gz or .tar.bz2 from the tree before starting a new build, so the point of you is maybe a good idea. Hmm. Especially as you say they are not really maintained. > > I downloaded fresh CVS and it seems modules now are in > > package libevas0. Thanks. :) But... now I get this: > > > > :~> evas_software_x11_test > > evas_software_x11_test: symbol lookup error: > > /usr/lib/evas/modules/loaders/png/linux-gnu-x86_64/module.so: > > undefined symbol: png_check_sig > > strange - as that module is LINKED to libpng: > > [ 11:46AM ~ ] > ldd /usr/local/lib/evas/modules/loaders/png/linux-gnu-x86_64/module.so > libpng12.so.0 => /usr/lib/libpng12.so.0 (0x00002aaaaabbb000) libz.so.1 > => /usr/lib/libz.so.1 (0x00002aaaaacdf000) libm.so.6 => /lib/libm.so.6 > (0x00002aaaaadf6000) ... > > > I also made make && make install. Same error. > > again - strange. works here - debian SID (amd64 AND ix86 as all of my machines > run debian across p3, p4, pentium-m and amd64 cpu's) I've seen that Problem on my checkout 2 days ago (i think). But as i checked out again yesterday morning, it was gone. I have the feeling there was just something that got fixed in CVS overnight. Anyway, just my opinion Martin Hauser -- Martin Hauser <[EMAIL PROTECTED]> GPG-Encrypted mail preferred, KEY: 0D459A72
pgpGHJS8arF7H.pgp
Description: PGP signature
