On Mon, 2013-11-04 at 12:25 +0000, Kanevskiy, Alexander wrote: > On 04/11/13 14:09 , "Patrick Ohly" <[email protected]> wrote: > > >Hello! > > > >Thanks for pointing this out. Build issues are typically not something > >that come to a developer's attention unless a build engineer brings it > >up. > > > >On Fri, 2013-11-01 at 16:13 +0900, 주현구 wrote: > >> After I accepted the following some packages in Tizen:Mobile project > >> yesterday night, I found your libphonenumber package has been build > >> failed. > > > >I tried to reproduce this, but so far have not been able to. > >libphonenumber compiled in OBS on a variety of platforms (Tizen:IVI on > >i586, Tizen on armv7hl/armv7l/i586). I see a build failure on Tizen with > >x86_64, but that's something else. It doesn't affect any of the profiles > >on tizen.org because they currently don't build x86_64. > > > >The problem you pointed to is on Tizen:Mobile with armv7l. I can't do > >remote builds in OBS, so I tried gbs instead. Where can I find a repo > >for Tizen:Mobile with armv7l? > > > >http://download.tizen.org/releases/daily/tizen/mobile/latest/ only has > >an i32 repo. > > > try snapshosts: > > http://download.tizen.org/snapshots/tizen/rd-pq/latest/ > > > there is no yet daily release with existing ARM support for 3.0 codeline.
Okay, that worked. I had a look at the offending geocoding_data.cc file. This looks like a toolchain problem. The file which failed to compile on arm had no real syntax error and was compiled fine on i586 (tested manually). Because the file is only needed for a feature that is not in use at the moment, I worked around the issue by disabling the feature. Jerry, I added you as reviewer of the corresponding change: https://review.tizen.org/gerrit/#/c/11765/ Please give a +1 if you agree and I'll merge. Otherwise we'll need help from the toolchain maintainers to diagnose and fix this issue. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
