Hi,

Attached here with please find my gbs.conf file for your reference.
Can you please tell me what is wrong over here? I have successfully
build sed and zlib package from source. i.e. Downloaded using 'git
clone' and build it, They build well, util-linux is creating a
problem.

I wanted to build tizen image that I can run using qemu, It will be
great if some one please explain me the procedure for the same. AFAIK,
First I have to build the tizen image (.img file) that I will be able
to run using qemu/emulator.

For the same I am giving a single package a try and try to understand
the procedure, environment etc.

uptil now I have compiled package from source code, didn't use yum or apt-get,

-Suresh

On 3/19/14, Maciej Wereski <[email protected]> wrote:
> 18.03.2014 at 18:20 Suresh Kanzariya <[email protected]> wrote:
>
>> Hi All,
>>
>> I was bit busy, so didn't came up with the latest updates. I have
>> checked the spec file, I think I have to build the required dependency
>> files first inorder to build util-linux.
>
> Well, you might, but you should just set up your GBS repositories
> correctly and GBS will automatically install all dependences. For more
> information about GBS please read following documentation:
> <https://source.tizen.org/documentation/reference/git-build-system/>
>
>>
>> Here are the list present in spec file.
>> BuildRequires:  binutils-devel
>> BuildRequires:  fdupes
>> BuildRequires:  gettext-devel
>> BuildRequires:  libtool
>> BuildRequires:  ncurses-devel
>> BuildRequires:  pam-devel
>> BuildRequires:  pkg-config
>> BuildRequires:  readline-devel
>> BuildRequires:  zlib-devel
>>
>> I am now learning spec file format, It is bit new to me as I have
>> build code from scratch and used it.
>>
>> Attached here with spec file for the reference.
>>
>> Thanks & Regards,
>> Suresh
>>
>
>
> regards,
> --
> Maciej Wereski
> Samsung R&D Institute Poland
> Samsung Electronics
> [email protected]
>
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev

Reply via email to