[maemo-developers] maemo-optify with Chinook / conditionals in debian/rules
From: Jeff Moe moe at blagblagblag.orgDate: Mon Dec 21 03:45:01 EET 2009
- Previous message: Re: maemo-optify with Chinook / conditionals in debian/rules
- Next message: SyncEvolution in Fremantle
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sunday 20 December 2009 20:32:45 Mikko Vartiainen wrote: > > I have generally put maemo-optify in the rules file right after > > "dh_builddep" as mentioned in the README. It may be true that the builder > > doesn't need it, but it appears the SDK does (?). > > Builder runs maemo-optify-deb which you can run locally too if needed. I think I'll start doing it that way from now to keep in line with builder. As slightly related note, I have a package that was maemo-optifying fine locally for armel/i386, but the builder croaked on maemo-optify of the i386 for some reason: maemo-optify print() on closed filehandle $out at /usr/bin/maemo-optify line 220. print() on closed filehandle $out at /usr/bin/maemo-optify line 183. Bad file descriptor at /usr/bin/maemo-optify line 240. Here's full logs, if it interests you: https://garage.maemo.org/builder/fremantle/portaudio19_19+svn20071022-4/i386.build.log.FAILED.txt But like I said, I will now use maemo-optify-deb and drop maemo-optify from my debian/rules. Thanks, -Jeff
- Previous message: Re: maemo-optify with Chinook / conditionals in debian/rules
- Next message: SyncEvolution in Fremantle
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]