Closed
Bug 1011481
Opened 11 years ago
Closed 11 years ago
Flame build broken due to not finding libgps.utils.so (and others) in backup-flame
Categories
(Firefox OS Graveyard :: GonkIntegration, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: kats, Unassigned)
References
Details
As of bug 1010212, I am unable to build flame using the basic setup which was working for me before. Specifically, the new libs added in that bug are not in my backup-flame folder, and so the build errors out because it can't find them.
The first time I did a flame build (which is when the backup-flame folder was created), I don't recall exactly what I had on my device, but it was either the latest 1.4 eng pvtbuild or the latest master eng pvtbuild.
Reflashing the current latest master eng pvtbuild still does not have these libs, so I suspect this might be broken for a lot of people.
Reporter | ||
Comment 1•11 years ago
|
||
workaround |
As a workaround for now I went into device/t2m/flame and ran "git revert 45bc538a07".
Reporter | ||
Comment 2•11 years ago
|
||
Also to clarify, none of the libs added in bug 1010212 were present in my backup-flame folder.
Summary: Flame build broken due to not finding libgps.utils.so in backup-flame → Flame build broken due to not finding libgps.utils.so (and others) in backup-flame
Reporter | ||
Comment 3•11 years ago
|
||
(In reply to Kartikaya Gupta (email:kats@mozilla.com) from comment #0)
> The first time I did a flame build (which is when the backup-flame folder
> was created), I don't recall exactly what I had on my device, but it was
> either the latest 1.4 eng pvtbuild or the latest master eng pvtbuild.
Note that in order flash the pvtbuilds, the process I used was to download the flame.zip file, unpack it, and run ./flash.sh inside the b2g-distro folder. It flashed all the .img files as expected and spit out an error when setting the time. The device rebooted and started up as expected so I never suspected anything was amiss there.
Comment 4•11 years ago
|
||
(In reply to Kartikaya Gupta (email:kats@mozilla.com) from comment #3)
> (In reply to Kartikaya Gupta (email:kats@mozilla.com) from comment #0)
> > The first time I did a flame build (which is when the backup-flame folder
> > was created), I don't recall exactly what I had on my device, but it was
> > either the latest 1.4 eng pvtbuild or the latest master eng pvtbuild.
>
> Note that in order flash the pvtbuilds, the process I used was to download
> the flame.zip file, unpack it, and run ./flash.sh inside the b2g-distro
> folder. It flashed all the .img files as expected and spit out an error when
> setting the time. The device rebooted and started up as expected so I never
> suspected anything was amiss there.
My understanding of this is the following:
- pvtbuilds are built from:
- git clone git://github.com/mozilla-b2g/B2G.git
- BRANCH=master ./config.sh flame
- ./build.sh
- flash.sh flashed the system partition that has been built by the process above.
Which means that your /system partition you made your backup from was lacking the libs. That's the reason for fixing bug 1010212. There should be those libs in the next pvtbuilds including bug 1010212, if the backup-flame used contains them.
Reporter | ||
Comment 5•11 years ago
|
||
(In reply to Alexandre LISSY :gerard-majax from comment #4)
> Which means that your /system partition you made your backup from was
> lacking the libs. That's the reason for fixing bug 1010212. There should be
> those libs in the next pvtbuilds including bug 1010212, if the backup-flame
> used contains them.
Yeah, confirmed. If I use the latest b2g-inbound-flame-eng pvtbuild and flash that on my device, then I get the missing libs. I can then delete my backup-flame dir and rebuild as normal and it works. The latest master pvtbuild hasn't picked up your change yet so it won't work with that.
Reporter | ||
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Comment 6•11 years ago
|
||
Also I posted about this to dev-b2g: https://groups.google.com/forum/#!topic/mozilla.dev.b2g/lMXyMgBrYuk
You need to log in
before you can comment on or make changes to this bug.
Description
•