![]() |
[ solved ][ autobuilder ] Failed to build 386 binary
I was able to push my app, stockona, to autobuilder and managed to make one successful build. I then fixed a bug and filled in the descriptions in debian/control file then uploaded again. But I have tried 4 times with slight tweaking in the long description, but all of them failed the 386 build.
This is the latest build log: https://garage.maemo.org/builder/fre...log.FAILED.txt My debian/control file is Code:
Source: stockona Also I have another question.. though i can see the app listed in the maemo package interface, I cannot see the app in FAM... anyone knows why? I am really confused by the packaging system. Btw, my environment is MS Windows + QtSDK. |
Re: [ autobuilder ] Failed to build 386 binary
If you can provide auto-builder logs that would probably help some more tech savvy people.
I've had this happen when trying to package with iw. I just charged Architecture from "any" to "armel" as a temporary workaround. It completely ignored the i386 build, but that's not used on the N900 anyway. Also, do you have the right repository (presumably, Extras-Devel, not just Extras) enabled on your device? |
Re: [ autobuilder ] Failed to build 386 binary
Quote:
https://garage.maemo.org/builder/fre...log.FAILED.txt Code:
dh_installman Quote:
|
Re: [ autobuilder ] Failed to build 386 binary
Thanks Mentalist, I got it working after using armel. And I was too impatient, this morning I saw the update icon flashing in the taskbar. Thanks again for the work-around!
|
Re: [ solved ][ autobuilder ] Failed to build 386 binary
I've got the same problem, but changing any to armel in control doesn't make the autobuilder ignore the 386 build.
The problem is that the i386 build of fcam-drivers does not inculde the N900 specific parts. EDIT: false alarm. It passed the second time I tried. |
All times are GMT. The time now is 04:07. |
vBulletin® Version 3.8.8