debian/rules not running ./configure
I'm trying to create my first package, and don't know what to do to get debian/rules to run ./configure. Eg: $ dpkg-buildpackage -rfakeroot dpkg-buildpackage: source package is fastdep dpkg-buildpackage: source version is 0.15-1 dpkg-buildpackage: source maintainer is Zenaan Harkness [EMAIL PROTECTED] dpkg-buildpackage: host architecture is i386 fakeroot debian/rules clean dh_testdir dh_testroot rm -f build-stamp # Add here commands to clean up after the build process. # HELP/TODO: Need command to go into doc/ subdir and run clean, distclean /usr/bin/make distclean make[1]: Entering directory `/home/zen/src/fastdep/fastdep-0.15' Makefile:3: config/config.me: No such file or directory You must run ./configure first to create config/config.me. Use ./configure --help to get information on how to guide the configuration. The make process will now exit with an error. make[1]: *** [config/config.me] Error 1 make[1]: Leaving directory `/home/zen/src/fastdep/fastdep-0.15' make: [clean] Error 2 (ignored) cp -f /usr/share/misc/config.sub config.sub cp -f /usr/share/misc/config.guess config.guess dh_clean dpkg-source -b fastdep-0.15 dpkg-source: building fastdep using existing fastdep_0.15.orig.tar.gz dpkg-source: building fastdep in fastdep_0.15-1.diff.gz dpkg-source: cannot represent change to doc/index.html: dpkg-source: new version is symlink dpkg-source: old version is nonexistent dpkg-source: cannot represent change to config/a.out: binary file contents changed dpkg-source: cannot represent change to debian/.rules.swp: binary file contents changed dpkg-source: cannot represent change to Makefile.deb-install: dpkg-source: new version is symlink dpkg-source: old version is nonexistent dpkg-source: warning: ignoring deletion of file doc/fastdep.html dpkg-source: warning: ignoring deletion of file doc/fastdep.pdf dpkg-source: building fastdep in fastdep_0.15-1.dsc dpkg-source: unrepresentable changes to source $ fakeroot debian/rules configure make: Nothing to be done for `configure'. $ touch configure $ fakeroot debian/rules configure make: Nothing to be done for `configure'. We see that the fastdep package's config/config.me file is not being created. When I manually run ./configure, this file is created. But then dpkg-buildpackage doesn't seem to run make. Is the line $(MAKE) in the example rules file supposed to run the 'make' command? I am not that familiar with make. Perhaps a little ironic since I'm packaging fastdep, but I am also teaching myself some C++, and since I come from years of Java background, I miss having a simple hierarchical-directory build process that readily scales to large projects. TIA Zen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: debian/rules not running ./configure
On Sat, Oct 25, 2003 at 04:38:42PM +1000, Zenaan Harkness wrote: I'm trying to create my first package, and don't know what to do to get debian/rules to run ./configure. Eg: Assuming you used dh_make, debian/rules contains a configure and configure-stamp target. You want to stick ./configure into the configure-stamp target, then touch configure-stamp. I think you need to bone up on the general workings of Makefiles though. [See below..] We see that the fastdep package's config/config.me file is not being created. When I manually run ./configure, this file is created. But then dpkg-buildpackage doesn't seem to run make. Is the line $(MAKE) in the example rules file supposed to run the 'make' command? Absolutely. $(MAKE) is a variable set by make that is usually just the argv[0] of what you typed on the command line. Hence, because debian/rules uses /usr/bin/make -f, it will be GNU make in this case. I am not that familiar with make. Perhaps a little ironic since I'm packaging fastdep, but I am also teaching myself some C++, and since I come from years of Java background, I miss having a simple hierarchical-directory build process that readily scales to large projects. OK, maybe you already know this, but I'm feeling verbose tonight... The general idea of Makefiles is that they are, at their simplest, a set of small shell scripts or general rules that tell how to generate a certain file. Make determines whether this file has to be regenerated based on the target's dependencies. Take for example: foo: foo.o bar.o gcc foo.o bar.o -o foo %.o: %.c gcc -o $@ -c $ foo.o: foo.c foo.h bar.o: bar.c foo.h This tells make a number of things. Firstly, that the command for the 'foo' target will be run if foo.o OR bar.o change, because they are dependencies. foo.o will be reuilt if foo.c or foo.h changes. And a general rule for generating .o files from .c files is defined by running gcc on them, where $@ is the output target name and $ is the input name. This small concept is useful, for example, when you change - or simply update the timestamp of - foo.h. This means that even if foo.o and bar.o exist, because foo.h is NEWER in date than foo.o, foo.o must be rebuilt using the new foo.h, and then foo.o will be more recent than the .h file. But if you say make foo.o after that, make will say it's up to date because it's newer than all its dependencies and will save time for you. In Debian, this all works out. We usually run debian/rules build, which is a target that depends on build-stamp, where that depends on source configuration and making, after which it will touch build-stamp to say Hey, I'm all done, no more extra work is needed here. And the commands inside each target are simply lines of text that are run by the shell line by line. I hope maybe this can help you with your debian/rules wrangling with regards to running configure. Also watch out for the warnings that dpkg-source is giving you. Those look rather ominous. -- Joshua Kwan pgp0.pgp Description: PGP signature
Re: RFS gdal
On Fri, Oct 24, 2003 at 09:48:11PM +0200, Jochen Friedrich wrote: - as it looks like you are both Upstream and Debian maintainer and you already added the debian directory into Upstream CVS, it might make sense to build a native package (i.e. no diff file, at all). Hello, No, unless gdal is very, very, very small and Silke wants to make a fresh _upstream_ release of gdal for a change in Debian's postinst. Debian native or not usually should not be chosen on behalf of whether upstream=debian-maintainer but on whether the package is Debian specific (like dpkg or mime-support) or not.[1] Making a package native has unwanted consequences: * every upload requires uploading a new tar.gz to the Debian server by the maintainer and distributing it to all the mirrors, instead of just uploading a (small) diff.gz. * Debian versioning and upstream versioning is usually completely unrelated. You don't want to make 1.1.9.1 release, if the only change from 1.1.9.0 is changed Build-Depends or the addition of a japanese debconf translation. * something I forgot to mention. :-P cu andreas [1] Compare e.g. to man-db, it is not packaged as native either. pgp0.pgp Description: PGP signature
Re: RFS gdal
Hi Andreas, Debian native or not usually should not be chosen on behalf of whether upstream=debian-maintainer but on whether the package is Debian specific (like dpkg or mime-support) or not.[1] * Debian versioning and upstream versioning is usually completely unrelated. Yes, but then the orig.tar.gz _must_ be the last upstream stable, not a daily cvs snapshot as Silke did ;-) --jochen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Looking for a sponsor
Hi Bruno, xmms-defx: A Sound alterator plug-in for xmms All files are avalaible in: http://www.igloo.cl/~bruno/xmms-defx/ sorry, fails to build for me (on Alpha): gcc -Llib -shared src/plugin.o -o lib/libdefx.so lib/libfx.a lib/libgui.a lib/libmain.a /usr/bin/ld: src/plugin.o: gp-relative relocation against dynamic symbol plugin /usr/bin/ld: src/plugin.o: gp-relative relocation against dynamic symbol plugin collect2: ld returned 1 exit status make[1]: *** [lib/libdefx.so] Error 1 Adding -fPIC to CFLAGS makes it work, though. Please adapt your Makefiles. Additionally, you ship an empty /usr/share/man/man1 directory. Please remove from debian/dirs. Thanks, --jochen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Need help: autoreconf breaks library package?
On Sat, 18 Oct 2003 21:14:39 +0200, Marc Haber [EMAIL PROTECTED] wrote: I am currently trying to include br2684 from the upstream CVS into my package. To have br2684 built, I need to re-build the makefiles. So I install automake and autoconf, and run autoreconf. After autoreconf, the package still builds without any error message, but the library files are missing the .so suffix. This is b0rken. The reason for this failure was that upstream built the package with libtool 1.4, and unstable has libtool 1.5. Some remains of libtool 1.4 were still left in the package. I had to autoreconf with -i -f to make the package build OK again. Greetings Marc -- -- !! No courtesy copies, please !! - Marc Haber |Questions are the | Mailadresse im Header Karlsruhe, Germany | Beginning of Wisdom | Fon: *49 721 966 32 15 Nordisch by Nature | Lt. Worf, TNG Rightful Heir | Fax: *49 721 966 31 29 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: debian/rules not running ./configure
On Sat, 2003-10-25 at 17:32, Joshua Kwan wrote:
On Sat, Oct 25, 2003 at 04:38:42PM +1000, Zenaan Harkness wrote:
I'm trying to create my first package, and don't know what to do to get
debian/rules to run ./configure. Eg:
Assuming you used dh_make, debian/rules contains a configure and
configure-stamp target.
dh_make, yes
rules targets:
build, depends on build-stamp
build-stamp, yes (may be this is what you meant by configure-stamp?),
depends on config.status
config.status, depends configure
configure, no ? (only as a dependency) ?, configure-stamp, no ?
Here is the relevant portion of rules, mostly auto-generated by dh_make:
=
config.status: configure
dh_testdir
# Add here commands to configure the package.
CFLAGS=$(CFLAGS) ./configure --host=$(DEB_HOST_GNU_TYPE) \
--build=$(DEB_BUILD_GNU_TYPE) --prefix=/usr \
--mandir=\$${prefix}/share/man --infodir=\$${prefix}/share/info
build: build-stamp
build-stamp: config.status
dh_testdir
# Add here commands to compile the package.
$(MAKE)
/usr/bin/docbook-to-man debian/fastdep.sgml fastdep.1
$(MAKE) -f Makefile.deb-install
touch build-stamp
=
As you can see, although there is no configure _target_, the
config.status target appears to have the ./configure command in it
(third line of it's mini script, please excuse the wrapping).
I have tried expanding all the variables/ substitutions, and running the
resultant configure command, and that works. It seems that this part of
the make file is simply never run.
You want to stick ./configure into the configure-stamp target, then
touch configure-stamp.
If you need, I can post the whole file, but as mentioned there's no
configure-stamp, dependency or target.
I think you need to bone up on the general workings of Makefiles though.
[See below..]
Tis true.
OK, maybe you already know this, but I'm feeling verbose tonight...
[...snip make intro...]
I hope maybe this can help you with your debian/rules wrangling with
regards to running configure.
Much appreciated. The GNU manuals can be a little terse sometimes.
However, I have some more questions, as per above.
Also watch out for the warnings that dpkg-source is giving you. Those
look rather ominous.
I'm happy to tackle ominous warnings... :)
Thanks heaps
Zen
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: how to make reportbug verbose?
Paul Telford [EMAIL PROTECTED] schrieb: On Fri, 24 Oct 2003, [iso-8859-15] Frank Küster wrote: in most bugreports, there's a lot of automatically generated information besides Package name and version: At least the system information with Debian release, Architecture, Kernel and the versions of packages that $buggy_package depends on. Sometimes there's even more, I guess that's when bugs are made from sufficiently updated unstable machines. Is it possible that the user just deleted those portions of the template before he sent the message? He might well be what german's call a PISA-Opfer[1]. But why should he have done this? Is this the behavior of the old bug program? Bye, Frank [1] PISA is an international study on educational systems in which Germany was rated _very_ badly; since then, people that can say words and write letters, but not express what they mean (or make lots of spelling errors etc.) are called PISA-victims, although they should be called German-school-system-victims. -- Frank Küster, Biozentrum der Univ. Basel Abt. Biophysikalische Chemie -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS gdal
On Sat, Oct 25, 2003 at 09:50:56AM +0200, Jochen Friedrich wrote: Debian native or not usually should not be chosen on behalf of whether upstream=debian-maintainer but on whether the package is Debian specific (like dpkg or mime-support) or not.[1] * Debian versioning and upstream versioning is usually completely unrelated. Yes, but then the orig.tar.gz _must_ be the last upstream stable, not a daily cvs snapshot as Silke did ;-) Yes and know. ;-) Usually you use last upstream stable but it is basically the maintainer's call. If CVS is just stable with bugfixes[1] there is no problem at all, or if if we are just at the beginning of a Debian release cycle in can make sense to switch the Debian package to the unstable version, to have a stable package ready when unstable becomes stable. The maintainers just has to be careful with the Debian-version number, coosing one that is lower than the final version, i.e 1.1.cvs1.2.20030928-1 which is greater than 1.1 and lower than 1.2. cu andreas [1] Check e.g. inn2. -- See, I told you they'd listen to Reason, [SPOILER] Svfurlr fnlf, fuhggvat qbja gur juveyvat tha. Neal Stephenson in Snow Crash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
TRANSPARENT ENTERPRISES
My name is David Osaro, I was the chairman of the mining review panel in Liberia all through the problems and fighting in my country Liberia before the escalation of the situation in Liberia and ousting of the former president Charles taylor I recovered $25Million US dollars from Charles Taylor hidden funds. But I was a member of the opposition tribe and the ruling tribe of Charles Taylor has been against us. So I had to flee the country for a neighbouring African Country, which I am currently residing. Just before the escalation of the situation in Liberia I had not reported the recovery of my findings to the panel. So this money was in my possession and I lodged it in a security company here in Africa and currently this money has been moved to Europe by a special security person under disguise. I have been trying to fly to Europe, but it has been difficult for me to get a visa from Africa. So I want you to help me make claims of this fund ($25m) in Europe as my beneficiary and transfer the money to your account or any account of your choice before I can get a visa to fly down, so that we can share this money.Fortunately for us all now including yourself,Charles Taylor is now in exile from Liberia so we do not have any problem as he cannot lay claim to the funds neither can any Liberian government officials as they are all corrupt. I have agreed to give you 20%, of this Money for your assistance, and 75% would be mine and the other 5% would be set aside for any expenses you and I incurs during the course of this transaction. And part of my 75% would be invested in your country in any profitable business proposed by you. We have never met, but I want to trust you and please do not let me down when this fund finally gets into your account. Please if you are interested, get to me through my confidential fax number 13094378449 and the email address below to enable me feed you with more details by sending me your confidential telephone numbers. Please treat this as confidential and absolute secrecy. Yours sincerely, David Osaro [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: debian/rules not running ./configure
On Sat, Oct 25, 2003 at 10:10:03PM +1000, Zenaan Harkness wrote:
build, depends on build-stamp
build-stamp, yes (may be this is what you meant by configure-stamp?),
depends on config.status
This is correct. That means that when config.status becomes newer than
build-stamp, build-stamp must be regenerated and hence the steps taken
to create it will be re-run (new configuration variables from
config.status.)
config.status, depends configure
Ok. You may depend on a specific file without having an actual target
for it. Basically, when config.status becomes older than configure, it
should be run again.
What happens when you do debian/rules config.status?
Is there a config.status already in the package? It might have the same
timestamp as configure. This would be an error.
Here is the relevant portion of rules, mostly auto-generated by dh_make:
=
config.status: configure
dh_testdir
# Add here commands to configure the package.
CFLAGS=$(CFLAGS) ./configure --host=$(DEB_HOST_GNU_TYPE) \
--build=$(DEB_BUILD_GNU_TYPE) --prefix=/usr \
--mandir=\$${prefix}/share/man --infodir=\$${prefix}/share/info
It looks okay to me. But maybe your configure script isn't an autoconf
script, because only autoconf configure scripts produce config.status.
You want to stick ./configure into the configure-stamp target, then
touch configure-stamp.
If you need, I can post the whole file, but as mentioned there's no
configure-stamp, dependency or target.
Maybe that could help. What about just the whole Debian source you're
working with? Then maybe we could get cooking.
--
Joshua Kwan
pgp0.pgp
Description: PGP signature
Re: RFS gdal
Hi Andreas, Yes and know. ;-) Usually you use last upstream stable but it is basically the maintainer's call. Yes sure :-) I was only thinking on my duties as sponsor to check the *-orig.tar.gz. I can't do this in this case as upstream only provides the daily cvs snaphot on her site and deletes the file again the next day. I know it's a bit pendantic, but Silke applied as Debian developer, so it's better to get the package right at the beginning before having to argue with the DAM later ;-) --jochen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RFS: popfile -- Email classification tool
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi! I'm still looking for a sponsor for the popfile[1] package I made. A new upstream version has been release and I have updated the package, so I am trying once again to get someone's attention on this. POPFile is an email classification tool with a Naive Bayes classifier, a POP3 proxy and a web interface. The package and source can be downloaded from my site[2], or from mentors[3] package repository. The package is lintian clean and closes WNPP bug #203349. K. [1] http://popfile.sourceforge.net [2] http://www.kadath.com.ar/popfile/ [3] http://mentors.debian.net/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (MingW32) iD8DBQE/muvhaPMPuwG2iykRAn0iAKCPjSNsjN6dJOjYhL03tmD7Nr3YOwCfXbLe nxva+9eA0LWdms9ZYZFAWF8= =BCFT -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: debian/rules not running ./configure
Tar bz2-ing the whole tree (upstream source + my debian subdir) results in 65KB file. Is it better to post this to the list, or just to yourself? tia zen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: debian/rules not running ./configure
Maybe that could help. What about just the whole Debian source you're working with? Then maybe we could get cooking. Of course, I could upload the files and point to them - doh! Here are * entire tree, not including parent files (eg. .dsc, etc) (upstream + debian subdir): http://homepages.ihug.com.au/~zenaan/tmp/zenaan/files/fastdep/fastdep-0.15+debian.tbz2 * just the debian/ subdir: http://homepages.ihug.com.au/~zenaan/tmp/zenaan/files/fastdep/fastdep-0.15-debian-only.tgz cheers zen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: avrdude - Programmer for Atmel AVR microcontrollers
Description: Programmer for Atmel AVR microcontrollers Just a thought - perhaps, to find someone who would be personally interested in the package, is it sensible to post an RFS to a more specific list? learning zen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: debian/rules not running ./configure
Here are * entire tree, not including parent files (eg. .dsc, etc) (upstream + debian subdir): http://homepages.ihug.com.au/~zenaan/tmp/zenaan/files/fastdep/fastdep-0.15+debian.tbz2 * just the debian/ subdir: http://homepages.ihug.com.au/~zenaan/tmp/zenaan/files/fastdep/fastdep-0.15-debian-only.tgz .dsc, etc in same directory. Permissions checked. zen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
debian/rules not running ./configure
I'm trying to create my first package, and don't know what to do to get debian/rules to run ./configure. Eg: $ dpkg-buildpackage -rfakeroot dpkg-buildpackage: source package is fastdep dpkg-buildpackage: source version is 0.15-1 dpkg-buildpackage: source maintainer is Zenaan Harkness [EMAIL PROTECTED] dpkg-buildpackage: host architecture is i386 fakeroot debian/rules clean dh_testdir dh_testroot rm -f build-stamp # Add here commands to clean up after the build process. # HELP/TODO: Need command to go into doc/ subdir and run clean, distclean /usr/bin/make distclean make[1]: Entering directory `/home/zen/src/fastdep/fastdep-0.15' Makefile:3: config/config.me: No such file or directory You must run ./configure first to create config/config.me. Use ./configure --help to get information on how to guide the configuration. The make process will now exit with an error. make[1]: *** [config/config.me] Error 1 make[1]: Leaving directory `/home/zen/src/fastdep/fastdep-0.15' make: [clean] Error 2 (ignored) cp -f /usr/share/misc/config.sub config.sub cp -f /usr/share/misc/config.guess config.guess dh_clean dpkg-source -b fastdep-0.15 dpkg-source: building fastdep using existing fastdep_0.15.orig.tar.gz dpkg-source: building fastdep in fastdep_0.15-1.diff.gz dpkg-source: cannot represent change to doc/index.html: dpkg-source: new version is symlink dpkg-source: old version is nonexistent dpkg-source: cannot represent change to config/a.out: binary file contents changed dpkg-source: cannot represent change to debian/.rules.swp: binary file contents changed dpkg-source: cannot represent change to Makefile.deb-install: dpkg-source: new version is symlink dpkg-source: old version is nonexistent dpkg-source: warning: ignoring deletion of file doc/fastdep.html dpkg-source: warning: ignoring deletion of file doc/fastdep.pdf dpkg-source: building fastdep in fastdep_0.15-1.dsc dpkg-source: unrepresentable changes to source $ fakeroot debian/rules configure make: Nothing to be done for `configure'. $ touch configure $ fakeroot debian/rules configure make: Nothing to be done for `configure'. We see that the fastdep package's config/config.me file is not being created. When I manually run ./configure, this file is created. But then dpkg-buildpackage doesn't seem to run make. Is the line $(MAKE) in the example rules file supposed to run the 'make' command? I am not that familiar with make. Perhaps a little ironic since I'm packaging fastdep, but I am also teaching myself some C++, and since I come from years of Java background, I miss having a simple hierarchical-directory build process that readily scales to large projects. TIA Zen
Re: debian/rules not running ./configure
On Sat, Oct 25, 2003 at 04:38:42PM +1000, Zenaan Harkness wrote: I'm trying to create my first package, and don't know what to do to get debian/rules to run ./configure. Eg: Assuming you used dh_make, debian/rules contains a configure and configure-stamp target. You want to stick ./configure into the configure-stamp target, then touch configure-stamp. I think you need to bone up on the general workings of Makefiles though. [See below..] We see that the fastdep package's config/config.me file is not being created. When I manually run ./configure, this file is created. But then dpkg-buildpackage doesn't seem to run make. Is the line $(MAKE) in the example rules file supposed to run the 'make' command? Absolutely. $(MAKE) is a variable set by make that is usually just the argv[0] of what you typed on the command line. Hence, because debian/rules uses /usr/bin/make -f, it will be GNU make in this case. I am not that familiar with make. Perhaps a little ironic since I'm packaging fastdep, but I am also teaching myself some C++, and since I come from years of Java background, I miss having a simple hierarchical-directory build process that readily scales to large projects. OK, maybe you already know this, but I'm feeling verbose tonight... The general idea of Makefiles is that they are, at their simplest, a set of small shell scripts or general rules that tell how to generate a certain file. Make determines whether this file has to be regenerated based on the target's dependencies. Take for example: foo: foo.o bar.o gcc foo.o bar.o -o foo %.o: %.c gcc -o $@ -c $ foo.o: foo.c foo.h bar.o: bar.c foo.h This tells make a number of things. Firstly, that the command for the 'foo' target will be run if foo.o OR bar.o change, because they are dependencies. foo.o will be reuilt if foo.c or foo.h changes. And a general rule for generating .o files from .c files is defined by running gcc on them, where $@ is the output target name and $ is the input name. This small concept is useful, for example, when you change - or simply update the timestamp of - foo.h. This means that even if foo.o and bar.o exist, because foo.h is NEWER in date than foo.o, foo.o must be rebuilt using the new foo.h, and then foo.o will be more recent than the .h file. But if you say make foo.o after that, make will say it's up to date because it's newer than all its dependencies and will save time for you. In Debian, this all works out. We usually run debian/rules build, which is a target that depends on build-stamp, where that depends on source configuration and making, after which it will touch build-stamp to say Hey, I'm all done, no more extra work is needed here. And the commands inside each target are simply lines of text that are run by the shell line by line. I hope maybe this can help you with your debian/rules wrangling with regards to running configure. Also watch out for the warnings that dpkg-source is giving you. Those look rather ominous. -- Joshua Kwan pgpyX0AwdlQUM.pgp Description: PGP signature
Re: RFS gdal
On Fri, Oct 24, 2003 at 09:48:11PM +0200, Jochen Friedrich wrote: - as it looks like you are both Upstream and Debian maintainer and you already added the debian directory into Upstream CVS, it might make sense to build a native package (i.e. no diff file, at all). Hello, No, unless gdal is very, very, very small and Silke wants to make a fresh _upstream_ release of gdal for a change in Debian's postinst. Debian native or not usually should not be chosen on behalf of whether upstream=debian-maintainer but on whether the package is Debian specific (like dpkg or mime-support) or not.[1] Making a package native has unwanted consequences: * every upload requires uploading a new tar.gz to the Debian server by the maintainer and distributing it to all the mirrors, instead of just uploading a (small) diff.gz. * Debian versioning and upstream versioning is usually completely unrelated. You don't want to make 1.1.9.1 release, if the only change from 1.1.9.0 is changed Build-Depends or the addition of a japanese debconf translation. * something I forgot to mention. :-P cu andreas [1] Compare e.g. to man-db, it is not packaged as native either. pgpjgpjwFQOot.pgp Description: PGP signature
Re: RFS gdal
Hi Andreas, Debian native or not usually should not be chosen on behalf of whether upstream=debian-maintainer but on whether the package is Debian specific (like dpkg or mime-support) or not.[1] * Debian versioning and upstream versioning is usually completely unrelated. Yes, but then the orig.tar.gz _must_ be the last upstream stable, not a daily cvs snapshot as Silke did ;-) --jochen
Re: Looking for a sponsor
Hi Bruno, xmms-defx: A Sound alterator plug-in for xmms All files are avalaible in: http://www.igloo.cl/~bruno/xmms-defx/ sorry, fails to build for me (on Alpha): gcc -Llib -shared src/plugin.o -o lib/libdefx.so lib/libfx.a lib/libgui.a lib/libmain.a /usr/bin/ld: src/plugin.o: gp-relative relocation against dynamic symbol plugin /usr/bin/ld: src/plugin.o: gp-relative relocation against dynamic symbol plugin collect2: ld returned 1 exit status make[1]: *** [lib/libdefx.so] Error 1 Adding -fPIC to CFLAGS makes it work, though. Please adapt your Makefiles. Additionally, you ship an empty /usr/share/man/man1 directory. Please remove from debian/dirs. Thanks, --jochen
Re: Need help: autoreconf breaks library package?
On Sat, 18 Oct 2003 21:14:39 +0200, Marc Haber [EMAIL PROTECTED] wrote: I am currently trying to include br2684 from the upstream CVS into my package. To have br2684 built, I need to re-build the makefiles. So I install automake and autoconf, and run autoreconf. After autoreconf, the package still builds without any error message, but the library files are missing the .so suffix. This is b0rken. The reason for this failure was that upstream built the package with libtool 1.4, and unstable has libtool 1.5. Some remains of libtool 1.4 were still left in the package. I had to autoreconf with -i -f to make the package build OK again. Greetings Marc -- -- !! No courtesy copies, please !! - Marc Haber |Questions are the | Mailadresse im Header Karlsruhe, Germany | Beginning of Wisdom | Fon: *49 721 966 32 15 Nordisch by Nature | Lt. Worf, TNG Rightful Heir | Fax: *49 721 966 31 29
Re: debian/rules not running ./configure
On Sat, 2003-10-25 at 17:32, Joshua Kwan wrote:
On Sat, Oct 25, 2003 at 04:38:42PM +1000, Zenaan Harkness wrote:
I'm trying to create my first package, and don't know what to do to get
debian/rules to run ./configure. Eg:
Assuming you used dh_make, debian/rules contains a configure and
configure-stamp target.
dh_make, yes
rules targets:
build, depends on build-stamp
build-stamp, yes (may be this is what you meant by configure-stamp?),
depends on config.status
config.status, depends configure
configure, no ? (only as a dependency) ?, configure-stamp, no ?
Here is the relevant portion of rules, mostly auto-generated by dh_make:
=
config.status: configure
dh_testdir
# Add here commands to configure the package.
CFLAGS=$(CFLAGS) ./configure --host=$(DEB_HOST_GNU_TYPE) \
--build=$(DEB_BUILD_GNU_TYPE) --prefix=/usr \
--mandir=\$${prefix}/share/man --infodir=\$${prefix}/share/info
build: build-stamp
build-stamp: config.status
dh_testdir
# Add here commands to compile the package.
$(MAKE)
/usr/bin/docbook-to-man debian/fastdep.sgml fastdep.1
$(MAKE) -f Makefile.deb-install
touch build-stamp
=
As you can see, although there is no configure _target_, the
config.status target appears to have the ./configure command in it
(third line of it's mini script, please excuse the wrapping).
I have tried expanding all the variables/ substitutions, and running the
resultant configure command, and that works. It seems that this part of
the make file is simply never run.
You want to stick ./configure into the configure-stamp target, then
touch configure-stamp.
If you need, I can post the whole file, but as mentioned there's no
configure-stamp, dependency or target.
I think you need to bone up on the general workings of Makefiles though.
[See below..]
Tis true.
OK, maybe you already know this, but I'm feeling verbose tonight...
[...snip make intro...]
I hope maybe this can help you with your debian/rules wrangling with
regards to running configure.
Much appreciated. The GNU manuals can be a little terse sometimes.
However, I have some more questions, as per above.
Also watch out for the warnings that dpkg-source is giving you. Those
look rather ominous.
I'm happy to tackle ominous warnings... :)
Thanks heaps
Zen
Re: how to make reportbug verbose?
Paul Telford [EMAIL PROTECTED] schrieb: On Fri, 24 Oct 2003, [iso-8859-15] Frank Küster wrote: in most bugreports, there's a lot of automatically generated information besides Package name and version: At least the system information with Debian release, Architecture, Kernel and the versions of packages that $buggy_package depends on. Sometimes there's even more, I guess that's when bugs are made from sufficiently updated unstable machines. Is it possible that the user just deleted those portions of the template before he sent the message? He might well be what german's call a PISA-Opfer[1]. But why should he have done this? Is this the behavior of the old bug program? Bye, Frank [1] PISA is an international study on educational systems in which Germany was rated _very_ badly; since then, people that can say words and write letters, but not express what they mean (or make lots of spelling errors etc.) are called PISA-victims, although they should be called German-school-system-victims. -- Frank Küster, Biozentrum der Univ. Basel Abt. Biophysikalische Chemie
Re: RFS gdal
On Sat, Oct 25, 2003 at 09:50:56AM +0200, Jochen Friedrich wrote: Debian native or not usually should not be chosen on behalf of whether upstream=debian-maintainer but on whether the package is Debian specific (like dpkg or mime-support) or not.[1] * Debian versioning and upstream versioning is usually completely unrelated. Yes, but then the orig.tar.gz _must_ be the last upstream stable, not a daily cvs snapshot as Silke did ;-) Yes and know. ;-) Usually you use last upstream stable but it is basically the maintainer's call. If CVS is just stable with bugfixes[1] there is no problem at all, or if if we are just at the beginning of a Debian release cycle in can make sense to switch the Debian package to the unstable version, to have a stable package ready when unstable becomes stable. The maintainers just has to be careful with the Debian-version number, coosing one that is lower than the final version, i.e 1.1.cvs1.2.20030928-1 which is greater than 1.1 and lower than 1.2. cu andreas [1] Check e.g. inn2. -- See, I told you they'd listen to Reason, [SPOILER] Svfurlr fnlf, fuhggvat qbja gur juveyvat tha. Neal Stephenson in Snow Crash
TRANSPARENT ENTERPRISES
My name is David Osaro, I was the chairman of the mining review panel in Liberia all through the problems and fighting in my country Liberia before the escalation of the situation in Liberia and ousting of the former president Charles taylor I recovered $25Million US dollars from Charles Taylor hidden funds. But I was a member of the opposition tribe and the ruling tribe of Charles Taylor has been against us. So I had to flee the country for a neighbouring African Country, which I am currently residing. Just before the escalation of the situation in Liberia I had not reported the recovery of my findings to the panel. So this money was in my possession and I lodged it in a security company here in Africa and currently this money has been moved to Europe by a special security person under disguise. I have been trying to fly to Europe, but it has been difficult for me to get a visa from Africa. So I want you to help me make claims of this fund ($25m) in Europe as my beneficiary and transfer the money to your account or any account of your choice before I can get a visa to fly down, so that we can share this money.Fortunately for us all now including yourself,Charles Taylor is now in exile from Liberia so we do not have any problem as he cannot lay claim to the funds neither can any Liberian government officials as they are all corrupt. I have agreed to give you 20%, of this Money for your assistance, and 75% would be mine and the other 5% would be set aside for any expenses you and I incurs during the course of this transaction. And part of my 75% would be invested in your country in any profitable business proposed by you. We have never met, but I want to trust you and please do not let me down when this fund finally gets into your account. Please if you are interested, get to me through my confidential fax number 13094378449 and the email address below to enable me feed you with more details by sending me your confidential telephone numbers. Please treat this as confidential and absolute secrecy. Yours sincerely, David Osaro [EMAIL PROTECTED]
Re: debian/rules not running ./configure
On Sat, Oct 25, 2003 at 10:10:03PM +1000, Zenaan Harkness wrote:
build, depends on build-stamp
build-stamp, yes (may be this is what you meant by configure-stamp?),
depends on config.status
This is correct. That means that when config.status becomes newer than
build-stamp, build-stamp must be regenerated and hence the steps taken
to create it will be re-run (new configuration variables from
config.status.)
config.status, depends configure
Ok. You may depend on a specific file without having an actual target
for it. Basically, when config.status becomes older than configure, it
should be run again.
What happens when you do debian/rules config.status?
Is there a config.status already in the package? It might have the same
timestamp as configure. This would be an error.
Here is the relevant portion of rules, mostly auto-generated by dh_make:
=
config.status: configure
dh_testdir
# Add here commands to configure the package.
CFLAGS=$(CFLAGS) ./configure --host=$(DEB_HOST_GNU_TYPE) \
--build=$(DEB_BUILD_GNU_TYPE) --prefix=/usr \
--mandir=\$${prefix}/share/man --infodir=\$${prefix}/share/info
It looks okay to me. But maybe your configure script isn't an autoconf
script, because only autoconf configure scripts produce config.status.
You want to stick ./configure into the configure-stamp target, then
touch configure-stamp.
If you need, I can post the whole file, but as mentioned there's no
configure-stamp, dependency or target.
Maybe that could help. What about just the whole Debian source you're
working with? Then maybe we could get cooking.
--
Joshua Kwan
pgpJsfC6VM8Vh.pgp
Description: PGP signature
Re: RFS gdal
Hi Andreas, Yes and know. ;-) Usually you use last upstream stable but it is basically the maintainer's call. Yes sure :-) I was only thinking on my duties as sponsor to check the *-orig.tar.gz. I can't do this in this case as upstream only provides the daily cvs snaphot on her site and deletes the file again the next day. I know it's a bit pendantic, but Silke applied as Debian developer, so it's better to get the package right at the beginning before having to argue with the DAM later ;-) --jochen
RFS: popfile -- Email classification tool
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi! I'm still looking for a sponsor for the popfile[1] package I made. A new upstream version has been release and I have updated the package, so I am trying once again to get someone's attention on this. POPFile is an email classification tool with a Naive Bayes classifier, a POP3 proxy and a web interface. The package and source can be downloaded from my site[2], or from mentors[3] package repository. The package is lintian clean and closes WNPP bug #203349. K. [1] http://popfile.sourceforge.net [2] http://www.kadath.com.ar/popfile/ [3] http://mentors.debian.net/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (MingW32) iD8DBQE/muvhaPMPuwG2iykRAn0iAKCPjSNsjN6dJOjYhL03tmD7Nr3YOwCfXbLe nxva+9eA0LWdms9ZYZFAWF8= =BCFT -END PGP SIGNATURE-
error 1 après apt-get install....
Bonjour, J'ai voulu upgrader Kde 2.. en Kde 3.1 par la commande apt-get. Tout s'est bien passé SAUF que je n'ai plus la barre de menu ? ni le menu démarer ! Heureusement que j'avais pris par hasard l'habitude de mettre des reacourcis sur le bureau... Donc tout fonctionne sauf que je n'ai plus de bureau 2,3,4 et ci-dessus. Je recommence avec apt-get install spamassassin et rebelote même erreur que lors de l'upgrade Je vous joins en attachement ce que j'ai récupérer dans le terminal. QUESTION: 1- Comment puis je terminer l'install de Kde pour avoir ma barre et les menus 2- Comment remédier pour que ce message E: error 1, ne se reproduise pas et que je puisse installer les paquets deb sans problème. Merci beaucoup par avance de prendre un peu de votre temps pour me répondre. Amicalement Patrick (pas expert en Linux) philippe:/home/georges# apt-get install spamassassin Reading Package Lists... Done Building Dependency Tree... Done The following NEW packages will be installed: spamassassin 0 packages upgraded, 1 newly installed, 0 to remove and 23 not upgraded. 1 packages not fully installed or removed. Need to get 208kB of archives. After unpacking 766kB will be used. Get:1 ftp://ftp.fr.debian.org stable/main spamassassin 2.20-1woody [208kB] Fetched 208kB in 14s (14.6kB/s) Selecting previously deselected package spamassassin. (Reading database ... 78845 files and directories currently installed.) Unpacking spamassassin (from .../spamassassin_2.20-1woody_i386.deb) ... Setting up diald (0.99.4-5) ... Starting diald: fifo-created dpkg: error processing diald (--configure): subprocess post-installation script returned error exit status 1 Setting up spamassassin (2.20-1woody) ... Errors were encountered while processing: diald E: Sub-process /usr/bin/dpkg returned an error code (1) philippe:/home/georges#
Re: debian/rules not running ./configure
Tar bz2-ing the whole tree (upstream source + my debian subdir) results in 65KB file. Is it better to post this to the list, or just to yourself? tia zen
Re: debian/rules not running ./configure
Maybe that could help. What about just the whole Debian source you're working with? Then maybe we could get cooking. Of course, I could upload the files and point to them - doh! Here are * entire tree, not including parent files (eg. .dsc, etc) (upstream + debian subdir): http://homepages.ihug.com.au/~zenaan/tmp/zenaan/files/fastdep/fastdep-0.15+debian.tbz2 * just the debian/ subdir: http://homepages.ihug.com.au/~zenaan/tmp/zenaan/files/fastdep/fastdep-0.15-debian-only.tgz cheers zen
Re: RFS: avrdude - Programmer for Atmel AVR microcontrollers
Description: Programmer for Atmel AVR microcontrollers Just a thought - perhaps, to find someone who would be personally interested in the package, is it sensible to post an RFS to a more specific list? learning zen
Re: debian/rules not running ./configure
Here are * entire tree, not including parent files (eg. .dsc, etc) (upstream + debian subdir): http://homepages.ihug.com.au/~zenaan/tmp/zenaan/files/fastdep/fastdep-0.15+debian.tbz2 * just the debian/ subdir: http://homepages.ihug.com.au/~zenaan/tmp/zenaan/files/fastdep/fastdep-0.15-debian-only.tgz .dsc, etc in same directory. Permissions checked. zen
