690198 - try-linux-mobile: dpkg-architecture: Command not found

Status: NEW

(Firefox Build System :: General, defect)

Description

[Joey Armstrong [:joey]]

Byproduct of a NOP makefile job.  'dpkg-architecture' was reported for two separate jobs but not sure if it was on the same slave.

make[1]: dpkg-architecture: Command not found


=============================================================
builder: try-linux-mobile
slave: linux-ix-slave09
starttime: 1317255016.59
results: success (0)
buildid: 20110928171029
builduid: 4f7afa37c262433db3259e3991060346
revision: c8992addf950

========= Started set props: symbolsUrl packageUrl testsUrl jsshellUrl (results: 0, elapsed: 24 secs) ==========
python /builds/slave/try-lnx-mb/tools/buildfarm/utils/retry.py -s 1 -r 5 -t 2460 make upload

Running post-upload command: post_upload.py --tinderbox-builds-dir [e-mail]-c8992addf950 -p firefox -i 20110928171029 --revision c8992addf950 --who [e-mail] --builddir try-linux --release-to-try-builds
Upload complete
make[1]: Leaving directory `/builds/slave/try-lnx-mb/build/obj-firefox/mobile/installer'

Process stderr:
make[1]: dpkg-architecture: Command not found
make[1]: Entering directory `/builds/slave/try-lnx-mb/build/obj-firefox/mobile/installer'
make[1]: dpkg-architecture: Command not found
make[1]: dpkg-architecture: Command not found
make[1]: dpkg-architecture: Command not found
http://stage.mozilla.org/pub/mozilla.org/firefox/try-builds/[e-mail]-c8992addf950/try-linux/fennec-9.0a1.en-US.linux-i686.tar.bz2

Comment 1

[Nick Thomas [:nthomas] (UTC+12)]

Since this is coming from 'make upload' it's something that belongs in a build system component. There are other bugs on file too, eg bug 527740, bug 634051

NB: There are three instances in the source
 http://mxr.mozilla.org/mozilla-central/search?string=dpkg-architecture
so we hit it in xulrunner builds as well.

Comment 2

[Mike Hommey [:glandium]]

Two things to note:
- It doesn't look like mobile/installer/Makefile.in and xulrunner/installer/Makefile.in actually use the result of dpkg-architecture. Not in a way that matters anyway.
- Using dpkg-architecture the way it is used is actually wrong, because the result possibly doesn't match the actual target for which the build was done. For example, we could be building for i686 on an x86-64 machine, and dpkg-architecture would return amd64.

Comment 3

[Aki Sasaki (not active)]

Now that we're no longer supporting Maemo as a tier1/2 platform, we can probably remove this from the makefiles.