Re: [Sablevm-developer] actual build failure not catched (sablevm-nativelib build dep on sablevm-na
Brought to you by:
egagnon
From: Grzegorz P. <ga...@de...> - 2002-10-17 22:00:13
|
W li=B6cie z czw, 17-10-2002, godz. 22:22, Etienne M. Gagnon pisze:=20 > Hi Grzegorz, >=20 > I am unable to replicate your problem, but this is probably because all I= am=20 > doing is installing SableVM, not building a binary package (e.g. "./confi= gure;=20 > make; make install"). >=20 > Could you tell me how I can set up my environment to build a Debian packa= ge,=20 > replicating your problem? Sure. In some directory (for ex. deb-sablevm) - get current source from unstable: apt-get source sablevm sablevm-nativelib sablevm-classlib To ompile the source (you'll need this later): - change to source directroy (cd sablevm-1.0.5 for ex.) - issue dpkg-buildpackage -rfakeroot (note additional -d switch which will let you bypass build deps of the packages - or rather - build-conflicts) Above command runs clean, build install and binary targets of ./debian/rules Makefile. Calling: fakeroot ./debian/rules binary is almost the same (but it does not clean for ex.) How to check what the problems are: - remove all sablevm traces from your system (sablevm debian packages too if you created and installed your own) - apt-get install sablevm - this will install 1.0.4 version which is exactly what we need to get into trouble - put your sources of 1.0.5 into deb-sablevm dir (where you issued apt-get source) - go to debianized source dirs (sablevm-1.0.4, sablevm-nativelib-1.0.4, sablevm-classlib-1.0.4) one by one and issue sth. like uupdate ../sablevm-1.0.5.tar.gz uupdate ../sablevm-native-library-1.0.5.tar.gz uupdate ../sablevm-class-libarary-1.0.5.tar.gz Every uupdate call will unpack original source and apply debianizin patches. Some diffs will not apply (for ex. for autotools files, but those ones you can simply ignore - config.* files are copied from originals in /usr/share/misc/ if only you have autotools-dev package installed - you should have) then you can go to your newly debianized *1.0.5* dirs and issue dpkg-buildpackage -rfakeroot in every of them. [beware: in sablevm-classlib source in ./debian/rules change 1.0.4 to 1.0.5 in at the beginning of this makefile To get into trouble use -d switch which will let you compile the packages having *1.0.4* version installed. After compilation issue dpkg -i *1.0.5*.deb in deb-sable dir - to install your new version of packages. Try to run HelloWorld. And cry... This way you get into this: even that you compiled 1.0.5 version - some patches that sablevm will look for - will contain 1.0.4 Second trouble you can get into is this: - sablevm-nativelib will be nonfunctional, if you build it w/o having some version of sablevm-nativelib already installed on your system BTW: you may want to redirect output of every build to some output file, like this. dpkg-buildpackage -rfakeroot &>../output.native then tail -f ./output.native on another console I'd especially advice you to look for error: warning: strings that can show up At this very end - I almost forgot - you may find usefull to look at the content of debian-policy and debian-reference-en Hope it helps Grzegorz B. Prokopski PS: I just fetched and compiled 1.0.5 debian packages. ATM I can just say that they *don't* work. Will take closer look at this tomorrow. |