Dear all:
No clue how is happen " conflict for providers of
libnetfilter_queue.so.1()(64bit) needed by nether (provider
libnetfilter_queue conflicts with installed libjpeg-devel)"
I don't see any connection between libnetfilter_queue and
libjpeg-devel.
[ 0s] Memory limit set to 98743912KB
[ 0s] Using
BUILD_ROOT=/home/marship/GBS-ROOT/local/BUILD-ROOTS/scratch.x86_64.11
[ 0s] Using BUILD_ARCH=x86_64:i686:i586:i486:i386:noarch
[ 0s]
[ 0s] unknown keyword in config: _project
[ 0s]
[ 0s] localhost.localdomain started "build chromium-efl.spec" at Sun Oct
30 17:44:17 UTC 2016.
[ 0s]
[ 0s]
[ 0s] processing recipe
/home/marship/GBS-ROOT/local/sources/tizen3.0_common/chromium-efl-47.2526.69.49-1/chromium-efl.spec
...
[ 0s] init_buildsystem --configdir /usr/lib/build/configs --cachedir
/home/marship/GBS-ROOT/local/cache --repository
/home/marship/GBS-ROOT/local/repos/tizen3.0_common/x86_64/RPMS --repository
/home/marship/tizen_repo/common/ --repository
/home/marship/tizen_repo/base/
/home/marship/GBS-ROOT/local/sources/tizen3.0_common/chromium-efl-47.2526.69.49-1/chromium-efl.spec
...
[ 0s] expanding package dependencies...
[ 0s] unknown keyword in config: _project
[ 1s] Use of uninitialized value in concatenation (.) or string at
/usr/lib/build/expanddeps line 276.
[ 1s] expansion error
[ 1s] conflict for providers of libnetfilter_queue.so.1()(64bit)
needed by nether (provider libnetfilter_queue conflicts with installed
libjpeg-devel)
On Sun, Oct 30, 2016 at 12:31 AM, Scott Zhang <macromars...@gmail.com>
wrote:
> After fix the build.conf for setup buildroot to include "cpp" and
> "util-linux-su" in , looks now it compiles 350/735 without any error. So
> looks finally I have my build environment right.
> Conclusion for build :
> 1. edit .gbs.conf,
> remove default "prebuilt/toolchains-x86_64" repo.
> It has far old package comparing to latest Base and ONLY have binary
> package without -devel packages, by compiling ourselves, everything need
> -devel packages so this is totally useless.
>
> 1.1 find the correct Base repository
> 1.2 find the correct Common repository
> For the moment, I am pretty sure "Base" it the toolchain repo. which
> should be replaced prevoius prebuilt/toolchain repo.
>
> there are many Base repostory, like "tizen","snapshots","live"."devel".
> In the confusing download.tizen.com, I was thinking the devel should be
> the lastest and most unstable build, but not ,snapshot is.
> So ONLY use Base and Common repo from snapshot.
>
> by edit .gbs.conf, in [profile.tizen3.0_common], only need Base and
> Common, don't use exisitng prebuilt.:
> And for build.conf, use the one below, comment out the default one.
> buildconf=${work_dir}/scm/meta/build-config/build-x86_64-wayland.conf
>
> [repo.tizen3.0_x86_64.base]
> url=/home/marship/tizen_repo/base/
>
> [repo.tizen3.0_x86_64.common]
> url=/home/marship/tizen_repo/common/
>
> [profile.tizen3.0_common]
> repos=repo.tizen3.0_x86_64.common,repo.tizen3.0_x86_64.base
> exclude_packages=libtool,gettext,texinfo
>
> # For wayland x86_64
> buildconf=${work_dir}/scm/meta/build-config/build-x86_64-wayland.conf
>
>
> 2. Now as we have upgrade the Base-toolchain to latest, the buildroot
> required packages need changed too. we need to edit
> ${work_dir}/scm/meta/build-config/build-x86_64-wayland.conf to reflect
> the changes.
> If you don't, you will find, like "gcc" can run "cc1". no "su" in
> buildroot. can't find "#include <stream>" complains error.
> My changes were to fix the error I get.
> So
> 0. I comment out "ligcc_s1" because last base doesn't have this package
> anymore.
> L374
> #Preinstall: libgcc_s1
>
>
> 1. I added util-linux-su becuase now util-linux doesn't install 'su'
> comand.
> L385
> Preinstall: util-linux util-linux-su
>
>
> 2. I appended "cpp" which provides "cc1"
> L391
> Required: binutils gcc glibc rpm-build libtool cpp
>
> 3. I added " libstdc++-devel" which provides "stream" headers
> L406
> # FIXME: TO REMOVE (? comes from IVI)
> Support: gcc-c++ libstdc++-devel
>
> After finish all these, I do
> gbs build -A x86_64 --threads 36 --clean --clean-repo
>
> The build goes smoothly.
>
> And one big note about speed up compile, the document is very correct by
> mount BUILD-ROOT as tmpfs, which greatly speed up the build. So absolutely
> should do that before compile.
>
> Next I can start learning the platform.
>
> Special Thanks to Pawel. Without your help I can't go this further.
> Thanks again.
>
>
> On Sat, Oct 29, 2016 at 11:24 PM, Scott Zhang <macromars...@gmail.com>
> wrote:
>
>> OK. I find in latest Base, the "su" command is in "
>> util-linux-su-2.28-1.1.x86_64.rpm
>> <http://download.tizen.org/snapshots/tizen/3.0-base/latest/repos/x86_64/packages/x86_64/util-linux-su-2.28-1.1.x86_64.rpm>
>> ".
>>
>> On Sat, Oct 29, 2016 at 5:08 PM, Scott Zhang <macromars...@gmail.com>
>> wrote:
>>
>>> I think this is a bug report.
>>> I have looked into the build.conf file.
>>> The prebuilt's rpm is too old. The latest tizen-base actually is the
>>> "Base". But the problem is the util-linux file being included in the
>>> lastest base, which DOESN't have the "su" do command. I have to check with
>>> the prebuilt version 2.24. devel repo version 2.25 and latest 2.28. Only
>>> latest doesn't have "su" command. I think I have to revert back to old base
>>> repo.
>>> [marship@localhost t]$ rpm -qlp ../util-linux-2.24.2-7.5.x86_64.rpm
>>> |grep su
>>> /etc/default/su
>>> /etc/pam.d/su
>>> /etc/pam.d/su-l
>>> /usr/bin/su
>>> /usr/sbin/sulogin
>>> [marship@localhost t]$ rpm -qlp util-linux-2.25.2-2.4.x86_64.rpm |grep
>>> su
>>> /etc/default/su
>>> /etc/pam.d/su
>>> /etc/pam.d/su-l
>>> /usr/bin/su
>>> /usr/sbin/sulogin
>>> [marship@localhost t]$ rpm -qlp util-linux-2.28-8.1.x86_64.rpm |grep su
>>> /etc/pam.d/su
>>> /etc/pam.d/su-l
>>> /usr/sbin/sulogin
>>>
>>>
>>> On Sat, Oct 29, 2016 at 4:43 PM, Scott Zhang <macromars...@gmail.com>
>>> wrote:
>>>
>>>> Dear pawel.
>>>> I have added the base+common into the local repo. Now more packages
>>>> built, but the same problem with there are OLD packages in
>>>> prebuilt/toolchains-x86_64 which existing within base repo too. Looks base
>>>> contains higher version and -devel files. Then for some package, the lower
>>>> version of package were installed and conflicts reported. Usually I will
>>>> remove the conflicts packages from prebuilt/ and createrepo . to rebuild
>>>> the repbuilt directory. But now, some package reports gcc/libdw conflicts
>>>> so I have to remove gcc from prebuilt.
>>>> My question is what exactlly "prebuilt/toolchains-x86_64" are? An
>>>> older version of Base repo without -devel packages? How can I make it to
>>>> newer version?
>>>> Thanks.
>>>>
>>>> On Sat, Oct 29, 2016 at 1:51 AM, Paweł Wieczorek <
>>>> p.wieczor...@samsung.com> wrote:
>>>>
>>>>> I am glad I could help.
>>>>>
>>>>> Best regards,
>>>>>
>>>>> Paweł Wieczorek
>>>>> Samsung R&D Institute Poland
>>>>> Samsung electronicsp.wieczor...@samsung.com
>>>>>
>>>>> On 28/10/16 18:02, Scott Zhang wrote:
>>>>>
>>>>> You win Pawel.
>>>>> The base repo still have packages devel repo doesn't have so I am
>>>>> including the repo in now.
>>>>>
>>>>> Regards
>>>>>
>>>>> On Fri, Oct 28, 2016 at 1:48 AM, Scott Zhang <macromars...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Thank. Pawel.
>>>>>> Yes. I guess missing "Base" is a main cause.
>>>>>> During the daytime dig of all urls, I found
>>>>>> http://download.tizen.org/snapshots/devel/common/latest/rep
>>>>>> os/x86_64-wayland/packages/ , Looks the "Devel" contains all the rpm
>>>>>> build need, so I am making a little more progress today, few more
>>>>>> packages
>>>>>> build success. Due to the slow network speed of China, I am getting slow
>>>>>> with remote repository. I will revert back to Base+Common if devel fails.
>>>>>>
>>>>>> Thank again.
>>>>>>
>>>>>> On Fri, Oct 28, 2016 at 12:37 AM, Paweł Wieczorek <
>>>>>> p.wieczor...@samsung.com> wrote:
>>>>>>
>>>>>>> Hi Scott,
>>>>>>>
>>>>>>> The issues you reported here and in "About Repo Sync get..." thread
>>>>>>> seem to be caused by the Tizen:Base repository (or rather by the lack of
>>>>>>> it).
>>>>>>>
>>>>>>> In order to get all the necessary source code, please refer to the
>>>>>>> following thread:
>>>>>>>
>>>>>>> https://lists.tizen.org/pipermail/dev/2016-June/007100.html
>>>>>>>
>>>>>>> Description of setting up proper GBS configuration can be found in
>>>>>>> following threads:
>>>>>>>
>>>>>>> https://lists.tizen.org/pipermail/dev/2016-May/007045.html
>>>>>>> https://lists.tizen.org/pipermail/dev/2016-June/007101.html
>>>>>>> https://lists.tizen.org/pipermail/dev/2016-September/007159.html
>>>>>>>
>>>>>>> Best regards,
>>>>>>>
>>>>>>> Paweł Wieczorek
>>>>>>> Samsung R&D Institute Poland
>>>>>>> Samsung electronicsp.wieczor...@samsung.com
>>>>>>>
>>>>>>> On 27/10/16 08:03, Scott Zhang wrote:
>>>>>>>
>>>>>>> I have read the link over 10 times and tried to understand and
>>>>>>> following each command. but still can't get project build without
>>>>>>> problem.
>>>>>>> Now I hangs on
>>>>>>> tpk-backend:
>>>>>>> nothing provides libgdbm.so.3()(64bit) needed by capi-system-info
>>>>>>>
>>>>>>> So many missings.
>>>>>>>
>>>>>>> I am using Centos7 to build tizen_common x86_64-wayland. Any
>>>>>>> suggestions?
>>>>>>> Thanks.
>>>>>>>
>>>>>>> https://source.tizen.org/documentation/developer-guide/getti
>>>>>>> ng-started-guide/building-packages-locally-gbs
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> General mailing
>>>>>>> listGeneral@lists.tizen.orghttps://lists.tizen.org/listinfo/general
>>>>>>>
>>>>>>>
>>>>
>>>
>>
>
_______________________________________________
Dev mailing list
Dev@lists.tizen.org
https://lists.tizen.org/listinfo/dev
