[Dev] [Important]Build problems Tizen 3.0 public

Dong, Junfeng junfeng.dong at intel.com
Fri Oct 11 04:22:33 GMT 2013

Dear Jinmin and GangHeok,

I wrote to you, because you are set as the maintainer and integrator of "platform/upstream/cups" in Tizen public. This package isn't updated with what is in 2.2 and make "mobileprint" fail to build.
The error is as follows:
[   70s] /usr/lib/gcc/i586-tizen-linux/4.8/../../../libprint-service.so: undefined reference to `ippGetValueTag'
[   70s] /usr/lib/gcc/i586-tizen-linux/4.8/../../../libprint-service.so: undefined reference to `ippFirstAttribute'
[   70s] /usr/lib/gcc/i586-tizen-linux/4.8/../../../libprint-service.so: undefined reference to `ippNextAttribute'
[   70s] /usr/lib/gcc/i586-tizen-linux/4.8/../../../libprint-service.so: undefined reference to `ippGetName'
[   70s] /usr/lib/gcc/i586-tizen-linux/4.8/../../../libprint-service.so: undefined reference to `ippGetInteger'
[   70s] /usr/lib/gcc/i586-tizen-linux/4.8/../../../libprint-service.so: undefined reference to `ippGetString'
[   70s] /usr/lib/gcc/i586-tizen-linux/4.8/../../../libprint-service.so: undefined reference to `ippGetGroupTag'
[   70s] /usr/lib/gcc/i586-tizen-linux/4.8/../../../libprint-service.so: undefined reference to `ippGetStatusCode'

Could you please update "tizen" branch of cups to the latest version (1.6.1) used in 2.2 branch. Please note the new development model in 3.0, you need to update "upstream" branch first. The guide of managing upstream package is https://source.tizen.org/documentation/reference/git-build-system/upstream-package

If you have any questions, please contact me. 


-----Original Message-----
From: dev-bounces at lists.tizen.org [mailto:dev-bounces at lists.tizen.org] On Behalf Of ANUJ MISHRA
Sent: Thursday, October 10, 2013 10:52 AM
Cc: dev at lists.tizen.org
Subject: Re: [Dev] [Important]Build problems Tizen 3.0 public

Look like some of the fixes being Merged to git but SR request is not raised. All Merged code should raise the SR for getting included in build. 
Today, still there are 16 failures for ARM build and not much SR visible yesterday. gst packages are still failing. Below of this mail is the URL to documentation of SR Process. 

No one came forwrard to fix one of the very important package "webkit2efl" package build failure. Hope maintainer looking into this email. 

No decision by Security team being made to solve the build failure of osp-installer. I would see the fix of osp-installer is very easy at the moment, once somebody look into this error. 
Therre is missing type "app_path_type_t" from smack module wheras similar type "app_type_t" is available to osp-installer. Why not add "app_path_type_t" declaration for the time being to solve this build error?

Also, for some packages maintainer planning to ugrade. Is it not feasible first to solve build error then go for upgrading upstream packages? If it is really 'unavoidable' then there is no other way. 
If not, simple fix in existing package is desirable to proceed further.  Once, everything building properly & running, it would be easy to verify upgrades. 

osp-media still waiting to be fixed. The lower layer maintainer should pay attention to this. 
Here is the current list of failed packeges. 

Hope to see some improvement today. 


------- Original Message -------
Sender : Lukasz Stelmach<l.stelmach at samsung.com> Software Engineer/SRPOL-Kernel & System Framework (SSD)/Samsung Electronics Date : Oct 09, 2013 19:59 (GMT+09:00) Title : Re: [Dev] [Important]Build problems Tizen 3.0 public

> https://wiki.tizen.org/wiki/OSDev/Development_guide#How_to_trigger_sub
> mission_to_OBS
Dev mailing list
Dev at lists.tizen.org

More information about the Dev mailing list