[Tizen-submit] 17573: Changes to Tizen:IVI:Stable/libffi

noreply at tizen.org noreply at tizen.org
Sat Nov 16 11:37:17 GMT 2013

Graydon, Tracy have made the following changes to libffi in project Tizen:IVI:Stable. Please review and accept ASAP.

Thank You,

[This message was auto-generated]


Request: #17573

  submit:       Tizen:IVI:Stable:build/libffi(cleanup) -> Tizen:IVI:Stable

Submitter: Graydon, Tracy <tracy.graydon at intel.com>
Comments: submit/tizen_ivi_stable/20131116.101340
Git project: platform/upstream/libffi
Tag: submit/tizen_ivi_stable/20131116.101340
Commit: 9afe851c146c40a137b5cf099d1e16658c3a38a3 fixed include path

State:   accepted   2013-11-16T10:36:16 tgraydon
Comment: Initial population of Tizen:IVI:Stable

History: new        2013-11-16T10:32:48 tizenrobot

spec files:

++++++ new spec file:
--- libffi.spec
+++ libffi.spec
@@ -0,0 +1,103 @@
+%global multilib_arches %{ix86}  x86_64
+Name:           libffi
+VCS:            platform/upstream/libffi#9afe851c146c40a137b5cf099d1e16658c3a38a3
+Version:        3.0.13
+Release:        0
+Summary:        A portable foreign function interface library
+License:        MIT
+Url:            http://sourceware.org/libffi
+Group:          Base/Toolchain
+Source0:        ftp://sourceware.org/pub/libffi/libffi-%{version}.tar.gz
+Source1:        ffi-multilib.h
+Source2:        ffitarget-multilib.h
+# Patches auto-generated by git-buildpackage:
+Patch0:     0001-fixed-include-path.patch
+Compilers for high level languages generate code that follow certain
+conventions.  These conventions are necessary, in part, for separate
+compilation to work.  One such convention is the "calling convention".
+The calling convention is a set of assumptions made by the compiler
+about where function arguments will be found on entry to a function.  A
+calling convention also specifies where the return value for a function
+is found.
+Some programs may not know at the time of compilation what arguments
+are to be passed to a function.  For instance, an interpreter may be
+told at run-time about the number and types of arguments used to call a
+given function.  `Libffi' can be used in such programs to provide a
+bridge from the interpreter program to compiled code.
+The `libffi' library provides a portable, high level programming
+interface to various calling conventions.  This allows a programmer to
+call any function specified by a call interface description at run time.
+FFI stands for Foreign Function Interface.  A foreign function
+interface is the popular name for the interface that allows code
+written in one language to call code written in another language.  The
+`libffi' library really only provides the lowest, machine dependent
+layer of a fully featured foreign function interface.  A layer must
+exist above `libffi' that handles type conversions for values passed
+between the two languages.
+%package	devel
+Summary:        Development files for %{name}
+Requires:       %{name} = %{version}
+Requires:       pkgconfig
+%description	devel
+The %{name}-devel package contains libraries and header files for
+developing applications that use %{name}.
+%setup -q
+# 0001-fixed-include-path.patch
+%patch0 -p1
+%configure --disable-static
+make %{?_smp_mflags}
+# Determine generic arch target name for multilib wrapper

Please refer to OBS webUI for more details about this SR.

More information about the Tizen-submit mailing list