| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
When the %rpmhome is not set to libdir the install order is wrong.
Change-Id: I5f79075298731ec1c60333c3ee0f5c583b07f16b
Signed-off-by: Slava Barinov <v.barinov@samsung.com>
|
|
This change will not have below error on aarch64 caused by rpmconfigdir
error: Unable to open /usr/lib/rpm/rpmrc for reading: Too many levels of symbolic links.
Change-Id: Ic896e64c80bd91a36f0bf4214c9ad4cfe55da2a7
Signed-off-by: Dongkyun, Son <dongkyun.s@samsung.com>
|
|
*.so at build time
The command strip has been in use building for chromium-efl like below.
$ strip --remove-section=.comment -o /PATH/TO/libchromium-ewk.so.debug /PATH/TO/libchromium-ewk.so
Also, it has been expected that
the argument libchromium-ewk.so.debug will have section .debug_*
and another argument libchromium-ewk.so will be stripped.
Btw, the libchromium-ewk.so.debug doesn't have the section .debug_*
but the libchromium-ewk.so still has the section.
The argument files need to be switched each other.
With this CL, the libchromium-ewk.so.debug properly has
the section .debug_* like below and libchromium-ewk.so is stripped.
> ...
> 28 .debug_line 048e8963 00000000 00000000 0231a318 2**0
> CONTENTS, READONLY, DEBUGGING
> 29 .debug_info b61b6cbd 00000000 00000000 06c02c7b 2**0
> CONTENTS, READONLY, DEBUGGING
> 30 .debug_abbrev 0349bf7f 00000000 00000000 bcdb9938 2**0
> CONTENTS, READONLY, DEBUGGING
> 31 .debug_aranges 004047a0 00000000 00000000 c02558b8 2**3
> CONTENTS, READONLY, DEBUGGING
> 32 .debug_ranges 015dbc78 00000000 00000000 c065a058 2**3
> CONTENTS, READONLY, DEBUGGING
> ...
> 34 .debug_loc 08b66519 00000000 00000000 c1c35cfd 2**0
> CONTENTS, READONLY, DEBUGGING
> 35 .debug_str 10b85beb 00000000 00000000 ca79c216 2**0
> CONTENTS, READONLY, DEBUGGING
> 36 .debug_frame 00d2f1b4 00000000 00000000 db321e04 2**2
> CONTENTS, READONLY, DEBUGGING
> ...
The file size is like below.
before)
3.5G libchromium-ewk.so
36M libchromium-ewk.so.debug
after)
36M libchromium-ewk.so
3.5G libchromium-ewk.so.debug
Bug: http://suprem.sec.samsung.net/jira/browse/RWASP-807
Change-Id: I11e80373fa9973663ee2c7b2092ae9a5f678cbc8
Signed-off-by: Youngsoo Choi <kenshin.choi@samsung.com>
|
|
Change-Id: I1214981ceb82d53c96becbe9d59e87e6272897bd
|
|
This allows moving rpm configs in x86_64 environment to prevent clashing in multilib
environments.
Change-Id: I8aa94d47f6b6fc6cb1ece88417363bb57ac8c14c
Signed-off-by: Slava Barinov <v.barinov@samsung.com>
|
|
This reverts commit c31c49f42b54dcf6edb8804e633e6b6985acbb41.
Change-Id: I94a88f43ba2db764c7c3a9435683ca26fe97c565
|
|
This reverts commit 822fe26c20549c1e891d874316cf91a7b244c23d.
Change-Id: Ic866ff716b4d547b4499f701b7577d025b89e8db
|
|
This commit is to solve a stripping issue of chromium-efl (m53).
Note that up-to-date elfutils package(e.g., the elfutils version
0.168 (3a45dbbe7) have fixed this issue. However, GPLv3 is a problem.
Let's support an alternative way to choose between strip (binutils)
and eu-strip (elfutils) to handle in case of a large shared object
such as chromium project. The default strip of rpmbuild is eu-strip.
* Case study: chromium-efl(m53)
Here is how to replace eu-strip (elfutils) with strip (binutils):
$ vi ./packaging/<git-package-name>.spec
# Let's replace eu-strip (elf-utils) with strip (binutils) in %install.
export STRIP_DEFAULT_PACKAGE="binutils"
Change-Id: Idca08e2f65ea084c6b5eb3c5cd218477f6da1a5f
Signed-off-by: Geunsik Lim <geunsik.lim@samsung.com>
|
|
build time
eu-strip can not normally remove debugging symbols in case of a large so file
such as libchromium-efl.so (2.8GiB) at build time. The up-to-date version of
eu-strip handles this issue by merging the commit that was submitted by
Mark Wielaard as following:
http://www.mail-archive.com/elfutils-devel@lists.fedorahosted.org/msg04444.html
In order to avoid eu-strip modification such as backporting, use strip(binutils)
instead of eu-strip(elfutils) because the existing strip has already fixed this issue.
before) eu-strip --remove-comment $g $strip_option -f "$1" "$2" || exit
after) strip --remove-section=.comment $g $strip_option -o "$1" "$2" || exit
* build error:
eu-strip: /home/abuild/rpmbuild/BUILDROOT/chromium-efl-53.2785.0.36-1.arm/usr/
lib/libchromium-ewk.so: INTERNAL ERROR 936 (0.153-Jan 6 2017): cannot read data from file
* unit test:
$ sudo chroot ~/GBS-ROOT/local/BUILD-ROOTS/scratch.armv7l.0/ /bin/bash
$ strip --remove-section=.comment -g ./libchromium-efl.so
$ ls -al
* evaluation:
$ sudo chroot ~/GBS-ROOT/local/BUILD-ROOTS/scratch.armv7l.0/ /bin/bash
$ rpm -ivh rpm-build-4.11.0.1-0.armv7l.rpm --force --nodeps
$ git checkout tizen_m53_beta
$ gbs build --define "nodebug 0" ......
(or ./tizen_src/build/build_mobile.sh -P tzmb_v3.0_target-TM1_mirror -A armv7l)
Change-Id: I7ae755b1f4570a28c0fc3088801b12f2ffd21808
Reported-by: Youngsoo Choi <kenshin.choi@samsung.com>
Signed-off-by: Geunsik Lim <geunsik.lim@samsung.com>
Reviewed-by: Dongkyun Son <dongkyun.s@samsung.com>
|
|
Additional modifications to support weak dependencies
(resolving errors from the cherry-pick)
rebased.
Change-Id: I34e9a5b11853dd4c0862dfbb119a3a5b7dd4f2bd
Signed-off-by: MyungJoo Ham <myungjoo.ham@samsung.com>
|
|
Change-Id: I24f0b1c0e98003a75b097c8afe7be19e21506695
Signed-off-by: MyungJoo Ham <myungjoo.ham@samsung.com>
|
|
Change-Id: Icac0310111aa3b59197af934659f7b94ca403059
|
|
As 32 bit build suffers under the limitation of 32 bit address space,
regardless of it's environment would be ie. 64 bit and not have this
constration, rpm must make sure not to exceed this memory limitation.
When using multithreaded xz compression, the number of threads used will
increase the memory usage, making it necessary to check the memory
required with the number of threads to be used.
Number of compression threads will therefore be kept reduced untill
amount of memory required won't exceed this limitation.
For 32 bit binaries running under 64 bit host environment, where less
available memory will be reserved for kernel, easing memory constraints,
determination of this will be done by a combination of checking host
arch as well as whether 32 bit personality flag is set, thereby still
allow a sligthly greater memory usage for such cases to avoid
imposing unnecessatry limitations under such environments.
Change-Id: Ie72827d3067a353a8a48faff9b65595c99f60a4c
|
|
Change-Id: I77af75943420c65868672f05cbde73563370c351
|
|
Change-Id: If7513a85c77692983bc2cb948f5b92eea3b304d8
|
|
Change-Id: I25c017827b38e2141dcff4d6bfd398f9e1a008c2
|
|
Change-Id: I3b95d39e0385ad50a6e8ed244757dd1fa8797f6e
|
|
Change-Id: Ie430058a1ecd3c03627060c1b32080d0d47a3877
|
|
which BTW fix the default compression level which is 6 instead of 7
Change-Id: I8b9b50a2cd1f64169477a72cc4d36a374d7a9867
|
|
Remove msm related macros inside macros.in file
Change-Id: I3ae680b13739f92624f757934fe884737c9181bf
|
|
package upgrade
Change-Id: I4cecbdb5034cef6ca42b8a8ed95792e73bf81c04
|
|
libdir macro which is re-defined in each platform macro : is not defined by ARCH but by _host_cpu
Change-Id: I2b5a10c817a1b8703bc3e51e8970ea73e49c5815
|
|
Change-Id: Ie5ccab262eed0494676bddfeba7ee16c25698a79
|
|
Change-Id: I24e489e0a965a85310d045435100f5ad2e95a592
|
|
Change-Id: Id4a2f8473d111284afbdb7760736b2a84a5954e4
|
|
Change-Id: I37f9794b4d009c6c7241b91d1c15b4c60633f62b
|
|
Change-Id: Ice05610d1c23eaf2dc1fb0cdf610feb20ad1cfab
|
|
using addPackageProvides_for_debuginfo_pkg
Change-Id: Iee094726b58250b7e86ebd3b508e30eb7c5389c9
|
|
option add '_rpm_strip_disable' option and '_rpm_strip_option' to project config.
Change-Id: I3718510670465957e7048db6ed285bd8ed09a5dd
|
|
Change-Id: I157f6a027820e0448e1ee95e10d1b42e8c95fcea
|
|
package & add option add '_rpm_strip_disable' option and '_rpm_strip_option' to project config."
This reverts commit dc338f74bbe69185d09a419ecda8e5fa35bb4acb.
Change-Id: I3c15db4307ea877b660ca6ea1056aa0e26b0e182
|
|
option add '_rpm_strip_disable' option and '_rpm_strip_option' to project config.
Change-Id: I939ca673d8dd06ebd0cb414d5471bdf962d8f5e1
|
|
|
|
New variable global_LDFLAGS can be defined in project config
to set default LDFLAGS during build.
Change-Id: I4da460c26b3f693833c74cb19d7234e78dbd4fc7
Signed-off-by: Yury Usishchev <y.usishchev@samsung.com>
|
|
The conflicts within the packages of equally ranked keys
must be treated usually by rpm.
Without this change, installation of conflicting packages
is not possible when msm plugin is active.
Change-Id: I909540524c7e2b43229b8aac90f66430041cbd55
Signed-off-by: José Bollo <jose.bollo@open.eurogiciel.org>
|
|
After 31699 optflags can contain ',' which breaks macros generation.
Change-Id: I86016ae4f5f97eadeb17c8ad79089539069b7f38
Signed-off-by: Yury Usishchev <y.usishchev@samsung.com>
|
|
Without it will fail if optflags are not overridden
and raise an error like :
configure: CFLAGS error: CFLAGS may only be used to specify C compiler flags, not macro definitions. Use CPPFLAGS for: -D_FORTIFY_SOURCE=2
configure: error: Can not continue. Fix errors mentioned immediately above this line.
error: Bad exit status from /var/tmp/rpm-tmp.AoOYbS (%build)
More details at :
https://gcc.gnu.org/onlinedocs/gcc-4.9.2/gcc/Preprocessor-Options.html#index-Wp-986
Change-Id: I49c8545a0526a1922905ef55de3a59edf9036068
Signed-off-by: Philippe Coval <philippe.coval@open.eurogiciel.org>
|
|
tizen
|
|
|
|
Change-Id: I5d0d86ca8788837c78ee078c5dfa6d4396168f95
Signed-off-by: Ronan Le Martret <ronan@fridu.net>
|
|
This patch is required when we use findutils-4.5.14 version. When we
tried to upgrade the findutils to 4.5.14 version, I've got below error
because the version of findutils obsoleted "find -perm +NNN".
[ 146s] find: invalid mode '+111'
[ 146s] error: Bad exit status from /var/tmp/rpm-tmp.5tcK7o (%install)
I picked up this patch from openSUSE[1] to solve this problem.
Origin: mail@bernhard-voelker.de
- replace obsoleted "find -perm +NNN" syntax [bnc#842004]
to "-perm /NNN" in debugsource-package.diff and
finddebuginfo.diff.
[1]: https://build.opensuse.org/request/show/200349
Change-Id: I38394427e4a806111550ad8ee560a448dd7a7307
Signed-off-by: Chanho Park <chanho61.park@samsung.com>
|
|
Apparently Yocto and BitBake do not use bash(1) as /bin/sh and break
when fed with bashisms like pushd/popd.
Bug-Tizen: BTY-21
Change-Id: I1a2781f97968b7290954297820b083759f11f0ed
Signed-off-by: Łukasz Stelmach <l.stelmach@samsung.com>
|
|
Localisation packages should be in the same group as the main package[1].
[1] https://wiki.tizen.org/wiki/Packaging/Guidelines#Group_Tag
Change-Id: Idd50d5a96f03ca316deaec61361016eb59db4065
Signed-off-by: Łukasz Stelmach <l.stelmach@samsung.com>
|
|
Change-Id: I107f04237037daffbc0d972ad9fed84a42836392
Signed-off-by: Nataliia Koval <nataliia.koval@globallogic.com>
|
|
With the Group tag explicitly set to "Documentation" trigger rpmlint
errors. With the tag removed from the macro the packages inherit their
parents' groups which makes rpmlint happy.
Change-Id: I3bbb02e58be284ebf36f3cfb0b2fa66b912332d3
Signed-off-by: Łukasz Stelmach <l.stelmach@samsung.com>
|
|
Yocto users can use different shells so the code inside recipes should
not be "bash only compliant".
Bug-Tizen: BTY-21
Change-Id: I5e91b4a284e195ff823f25f9eeed12544344c4b0
Signed-off-by: Kévin THIERRY <kevin.thierry@open.eurogiciel.org>
|
|
The msm plugin creates one access rule file
in SMACK_RULES_PATH=/etc/smack/accesses.d for
each RPM installed.
Since Tizen 3, the guideline for packages is
simplified and the new guideline states that
manifest files have to be as simple as:
<manifest>
<request>
<domain name="_"/>
</request>
</manifest>
It means that most access rule files are empty.
Thus, this patch removes the file if it is empty
because without any penality, it improves:
- the start time of the system
- the administration of the system
The start time is improved because at start, all
the files in /etc/smack/accesses.d are read and
loaded to the kernel. As empty files are just removed,
no time is spend to seek it, open it, read it, close it,
apply empty rule.
The administration is also improved because only meaning
access rule files are retains, avoid to have to sort what
is meaning and what is not.
Change-Id: I7b40f2b291f0c1dbcb2f033f62191c651430e3c8
Signed-off-by: José Bollo <jose.bollo@open.eurogiciel.org>
|
|
Change-Id: I5e84c913d1756320bf31442d87b797ff8b5f4633
|
|
Names of the software repositories were used as subject of
the generated smack rules. There is no mention of such
behaviour on the help pages in the wiki of tizen.
Bug-Tizen: PTREL-638
Change-Id: Iefef89492ab5c9839cb01d3b62dae4c3637f00f4
Signed-off-by: José Bollo <jose.bollo@open.eurogiciel.org>
|
|
|
