Not sure why is so confusing and frustracting , build such system take so
many efforts. It has taken half a week.
Now toolchain_base missing shadow-utils file. but Base 2.28 has it. The
moment the only problem I found with Base 2.28 is the "su" missing in
util-linux package which stop buildroot from working, as I don't know how
to put a "su" directly into it. stackoverflow and google suggest a rebuild
the src rpm. so I am building it. Now all compilation passed, but stop me
at
+ cp -pr COPYING
/root/rpmbuild/BUILDROOT/util-linux-2.28-1.1.x86_64/usr/share/licenses/util-linux-2.28
+ exit 0
RPM build errors:
File must begin with "/": %manifest
File must begin with "/": util-linux.manifes
What's the "File must begin with "/": %manifest"
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
>>>>>
>>>>>
>>
>
_______________________________________________
General mailing list
General@lists.tizen.org
https://lists.tizen.org/listinfo/general
