[Buildroot] [GSoC19] Motivation

[Buildroot] [GSoC19] Motivation

[Mohamed Dawod]

Greetings,
I hope this email finds you well.

My name is Mohamed.
I am a 4th year Computer Engineering student at Faculty of Engineering -
Cairo University.
*LinkedIn Profile* : https://www.linkedin.com/in/mohameddawod96/
*Github Profile* : https://github.com/Dawody
I would like to work in Project *"Support for distributed builds with
IceCC"*

I have 2 years of experience in this failed.
1. I studied Operating systems and Distributed systems in the faculty.

2. I learnt How to build Linux From Scratch  (LFS8.3).

3. I learnt Embedded Linux. I worked as Embedded Linux Engineer Inter in
the last summer.
- I built a complete linux based operating system for specific kit to
execute qt5 apps.
- I changed the default windowing system to wayland, and I customized
wayland to fit the project needs.
- I used yoctoproject, bitbake and openembedded and other open source
layers.


I am interested in operating systems and building embedded linux systems.
From my experiment with bitbake and openembedded, I found that It really
takes so much time to build complete embedded linux system.
so I think that distributing this process can be a great achievement.
Although I didn't use Buildroot or IceCC before, but  I could learn yocto,
bitbake and openembedded and building projects with them during my summer
internship without a direct supervision. It's well-known that Yocto Project
has a steep learning curve.
so I hope that I can learn buildroot and IceCC in short free time to start
the project.

I am looking forward to be accepted in this project because I would like to
dig deeper in this field as I adore it,
and because it may be my last chance to participate in GSoC, I wouldn't
like to lose this chance.

Thank You,
Regards,

-- 

Mohamed Dawod
Computer Engineering Department
Faculty of Engineering
Cairo University
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20190401/106088c7/attachment.html>

[Buildroot] [GSoC19] Motivation

[Thomas Petazzoni]

Hello Mohamed,

On Mon, 1 Apr 2019 21:07:15 +0200
Mohamed Dawod <mhm.dawod@gmail.com> wrote:

> I am looking forward to be accepted in this project because I would like to
> dig deeper in this field as I adore it,
> and because it may be my last chance to participate in GSoC, I wouldn't
> like to lose this chance.

Thanks a lot for introducing yourself, and for your interest in our
topic related to IceCC.

In order to show your interest and skills, could you try to submit one
patch doing some useful contribution to Buildroot ?

You could for example look at http://autobuild.buildroot.net/stats/ for
some package that is not up-to-date, update it to a newer version, test
it on some target (real HW or Qemu) and provide a patch doing the
update. Of course, make sure to read a bit the mailing list to see the
best practices. Check out also the Buildroot manual which has some
indications on how to contribute.

Alternatively, you could have a look at http://autobuild.buildroot.net/
and try to solve some of the build failures, but this is more difficult
for a newcomer.

Thanks!

Thomas Petazzoni
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

[Buildroot] [GSoC19] Motivation

[Mohamed Dawod]

>
> In order to show your interest and skills, could you try to submit one
> patch doing some useful contribution to Buildroot ?
>
> You could for example look at http://autobuild.buildroot.net/stats/ for
> some package that is not up-to-date, update it to a newer version, test
> it on some target (real HW or Qemu) and provide a patch doing the
> update. Of course, make sure to read a bit the mailing list to see the
> best practices. Check out also the Buildroot manual which has some
> indications on how to contribute.
>

Ok, I will try to do this task. I will start NOW.

Unfortunately, My midterm exams will start next week. I need to finish the
project proposal this week because it will be very hard to work during
exams.
so I suggest to give higher priority to the project proposal more than the
task of contribution.
I promise I will finish the contribution task after the exams if I couldn't
finish it before the exams.
Are you agree for that ?

thank you in advance,

On Mon, Apr 1, 2019 at 9:44 PM Thomas Petazzoni <
thomas.petazzoni@bootlin.com> wrote:

> Hello Mohamed,
>
> On Mon, 1 Apr 2019 21:07:15 +0200
> Mohamed Dawod <mhm.dawod@gmail.com> wrote:
>
> > I am looking forward to be accepted in this project because I would like
> to
> > dig deeper in this field as I adore it,
> > and because it may be my last chance to participate in GSoC, I wouldn't
> > like to lose this chance.
>
> Thanks a lot for introducing yourself, and for your interest in our
> topic related to IceCC.
>
> In order to show your interest and skills, could you try to submit one
> patch doing some useful contribution to Buildroot ?
>
> You could for example look at http://autobuild.buildroot.net/stats/ for
> some package that is not up-to-date, update it to a newer version, test
> it on some target (real HW or Qemu) and provide a patch doing the
> update. Of course, make sure to read a bit the mailing list to see the
> best practices. Check out also the Buildroot manual which has some
> indications on how to contribute.
>
> Alternatively, you could have a look at http://autobuild.buildroot.net/
> and try to solve some of the build failures, but this is more difficult
> for a newcomer.
>
> Thanks!
>
> Thomas Petazzoni
> --
> Thomas Petazzoni, CTO, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
>


-- 

Mohamed Dawod
Computer Engineering Department
Faculty of Engineering
Cairo University
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20190402/ccacddcd/attachment.html>

[Buildroot] [GSoC19] Motivation

[Mohamed Dawod]

Hi all,
I submitted my Draft Proposal document with buildroot organization to
review my proposal document.
I am looking forward to read your comments and feedback.

About the contribution task,
I read about buildroot and how to patch new packages.
Buildroot is powerful and really more easier than Yocto project. I loved
buildroot very much :-D
I checked the list of packages and I chose wget package to update it.
I successfully prepared the patch file but still not tested.
I hope to test it before the end of this week_before the starting of
midterm exams_ to submit it to the the main list.

Thank you for the useful help on the IRC channel ,
And thank you for the great Buildroot user manual.

Regards.



On Tue, Apr 2, 2019 at 5:14 AM Mohamed Dawod <mhm.dawod@gmail.com> wrote:

> In order to show your interest and skills, could you try to submit one
>> patch doing some useful contribution to Buildroot ?
>>
>> You could for example look at http://autobuild.buildroot.net/stats/ for
>> some package that is not up-to-date, update it to a newer version, test
>> it on some target (real HW or Qemu) and provide a patch doing the
>> update. Of course, make sure to read a bit the mailing list to see the
>> best practices. Check out also the Buildroot manual which has some
>> indications on how to contribute.
>>
>
> Ok, I will try to do this task. I will start NOW.
>
> Unfortunately, My midterm exams will start next week. I need to finish the
> project proposal this week because it will be very hard to work during
> exams.
> so I suggest to give higher priority to the project proposal more than the
> task of contribution.
> I promise I will finish the contribution task after the exams if I
> couldn't finish it before the exams.
> Are you agree for that ?
>
> thank you in advance,
>
> On Mon, Apr 1, 2019 at 9:44 PM Thomas Petazzoni <
> thomas.petazzoni at bootlin.com> wrote:
>
>> Hello Mohamed,
>>
>> On Mon, 1 Apr 2019 21:07:15 +0200
>> Mohamed Dawod <mhm.dawod@gmail.com> wrote:
>>
>> > I am looking forward to be accepted in this project because I would
>> like to
>> > dig deeper in this field as I adore it,
>> > and because it may be my last chance to participate in GSoC, I wouldn't
>> > like to lose this chance.
>>
>> Thanks a lot for introducing yourself, and for your interest in our
>> topic related to IceCC.
>>
>> In order to show your interest and skills, could you try to submit one
>> patch doing some useful contribution to Buildroot ?
>>
>> You could for example look at http://autobuild.buildroot.net/stats/ for
>> some package that is not up-to-date, update it to a newer version, test
>> it on some target (real HW or Qemu) and provide a patch doing the
>> update. Of course, make sure to read a bit the mailing list to see the
>> best practices. Check out also the Buildroot manual which has some
>> indications on how to contribute.
>>
>> Alternatively, you could have a look at http://autobuild.buildroot.net/
>> and try to solve some of the build failures, but this is more difficult
>> for a newcomer.
>>
>> Thanks!
>>
>> Thomas Petazzoni
>> --
>> Thomas Petazzoni, CTO, Bootlin
>> Embedded Linux and Kernel engineering
>> https://bootlin.com
>>
>
>
> --
>
> Mohamed Dawod
> Computer Engineering Department
> Faculty of Engineering
> Cairo University
>


-- 

Mohamed Dawod
Computer Engineering Department
Faculty of Engineering
Cairo University
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20190404/43b120fb/attachment.html>

[Buildroot] [GSoC19] Motivation

[Peter Korsgaard]

>>>>> "Mohamed" == Mohamed Dawod <mhm.dawod@gmail.com> writes:

 > Hi all,
 > I submitted my Draft Proposal document with buildroot organization to
 > review my proposal document.
 > I am looking forward to read your comments and feedback.

 > About the contribution task,
 > I read about buildroot and how to patch new packages.
 > Buildroot is powerful and really more easier than Yocto project. I loved
 > buildroot very much :-D
 > I checked the list of packages and I chose wget package to update it.
 > I successfully prepared the patch file but still not tested.
 > I hope to test it before the end of this week_before the starting of
 > midterm exams_ to submit it to the the main list.

Sorry, I bumped wget yesterday:

https://git.buildroot.net/buildroot/commit/?id=c21d440c8a79a6af284ec5793481d1b8a0b298ca

-- 
Bye, Peter Korsgaard

[Buildroot] [GSoC19] Motivation

[Mohamed Dawod]

>
> >>>>> Peter Korsgaard <peter at korsgaard.com <mhm.dawod@gmail.com>> writes:
> > Sorry, I bumped wget yesterday:
>

No problem, I will find some other package to update.
But I noticed that my patch is slightly different of yours

This id my patch :

Signed-off-by: Mohamed Dawod <mhm.dawod@gmail.com>
> ---
> diff -Naur wget/wget.hash wget2/wget.hash
> --- a/package/wget.hash    2019-04-03 14:38:50.133423838 +0200
> +++ b/package/wget.hash    2019-04-03 15:09:44.834238846 +0200
> @@ -1,6 +1,6 @@
>  # Locally calculated after checking pgp signature
> -# https://ftp.gnu.org/gnu/wget/wget-1.20.1.tar.lz.sig
> +# https://ftp.gnu.org/gnu/wget/wget-1.20.2.tar.lz.sig
>  # with key 1CB27DBC98614B2D5841646D08302DB6A2670428
> -sha256 0f63e84dd23dc53ab3ab6f483c3afff8301e54c165783f772101cdd9b1c64928
> wget-1.20.1.tar.lz
> +sha256 e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
> wget-1.20.2.tar.lz
>  # Locally calculated
>  sha256 e79e9c8a0c85d735ff98185918ec94ed7d175efc377012787aebcf3b80f0d90b
> COPYING
> diff -Naur wget/wget.mk wget2/wget.mk
> --- a/package/wget.mk    2019-04-03 14:38:50.133423838 +0200
> +++ b/package/wget.mk    2019-04-03 14:40:12.080507178 +0200
> @@ -4,7 +4,7 @@
>  #
>
>  ################################################################################
>
> -WGET_VERSION = 1.20.1
> +WGET_VERSION = 1.20.2
>  WGET_SOURCE = wget-$(WGET_VERSION).tar.lz
>  WGET_SITE = $(BR2_GNU_MIRROR)/wget
>  WGET_DEPENDENCIES = host-pkgconf
>


The difference is new sha256sum of the new package.
I downloaded the new package from the link "
https://ftp.gnu.org/gnu/wget/wget-1.20.2.tar.lz"
then I run the command $sha256sum wget-1.20.2.tar.lz
how can the checksum be different ?




On Thu, Apr 4, 2019 at 7:56 AM Peter Korsgaard <peter@korsgaard.com> wrote:

> >>>>> "Mohamed" == Mohamed Dawod <mhm.dawod@gmail.com> writes:
>
>  > Hi all,
>  > I submitted my Draft Proposal document with buildroot organization to
>  > review my proposal document.
>  > I am looking forward to read your comments and feedback.
>
>  > About the contribution task,
>  > I read about buildroot and how to patch new packages.
>  > Buildroot is powerful and really more easier than Yocto project. I loved
>  > buildroot very much :-D
>  > I checked the list of packages and I chose wget package to update it.
>  > I successfully prepared the patch file but still not tested.
>  > I hope to test it before the end of this week_before the starting of
>  > midterm exams_ to submit it to the the main list.
>
> Sorry, I bumped wget yesterday:
>
>
> https://git.buildroot.net/buildroot/commit/?id=c21d440c8a79a6af284ec5793481d1b8a0b298ca
>
> --
> Bye, Peter Korsgaard
>


-- 

Mohamed Dawod
Computer Engineering Department
Faculty of Engineering
Cairo University
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20190404/aad30d74/attachment.html>

[Buildroot] [GSoC19] Motivation

[Peter Korsgaard]

>>>>> "Mohamed" == Mohamed Dawod <mhm.dawod@gmail.com> writes:

 >> 
 >> >>>>> Peter Korsgaard <peter at korsgaard.com <mhm.dawod@gmail.com>> writes:
 >> > Sorry, I bumped wget yesterday:
 >> 

 > No problem, I will find some other package to update.
 > But I noticed that my patch is slightly different of yours

 > This id my patch :

 > Signed-off-by: Mohamed Dawod <mhm.dawod@gmail.com>
 >> ---
 >> diff -Naur wget/wget.hash wget2/wget.hash
 >> --- a/package/wget.hash    2019-04-03 14:38:50.133423838 +0200
 >> +++ b/package/wget.hash    2019-04-03 15:09:44.834238846 +0200
 >> @@ -1,6 +1,6 @@
 >> # Locally calculated after checking pgp signature
 >> -# https://ftp.gnu.org/gnu/wget/wget-1.20.1.tar.lz.sig
 >> +# https://ftp.gnu.org/gnu/wget/wget-1.20.2.tar.lz.sig
 >> # with key 1CB27DBC98614B2D5841646D08302DB6A2670428
 >> -sha256 0f63e84dd23dc53ab3ab6f483c3afff8301e54c165783f772101cdd9b1c64928
 >> wget-1.20.1.tar.lz
 >> +sha256 e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
 >> wget-1.20.2.tar.lz
 >> # Locally calculated
 >> sha256 e79e9c8a0c85d735ff98185918ec94ed7d175efc377012787aebcf3b80f0d90b
 >> COPYING
 >> diff -Naur wget/wget.mk wget2/wget.mk
 >> --- a/package/wget.mk    2019-04-03 14:38:50.133423838 +0200
 >> +++ b/package/wget.mk    2019-04-03 14:40:12.080507178 +0200
 >> @@ -4,7 +4,7 @@
 >> #
 >> 
 >> ################################################################################
 >> 
 >> -WGET_VERSION = 1.20.1
 >> +WGET_VERSION = 1.20.2
 >> WGET_SOURCE = wget-$(WGET_VERSION).tar.lz
 >> WGET_SITE = $(BR2_GNU_MIRROR)/wget
 >> WGET_DEPENDENCIES = host-pkgconf
 >> 


 > The difference is new sha256sum of the new package.
 > I downloaded the new package from the link "
 > https://ftp.gnu.org/gnu/wget/wget-1.20.2.tar.lz"
 > then I run the command $sha256sum wget-1.20.2.tar.lz
 > how can the checksum be different ?

Ehh, I don't know. I just tried it again here:

wget https://ftp.gnu.org/gnu/wget/wget-1.20.2.tar.lz
--2019-04-04 12:09:23--  https://ftp.gnu.org/gnu/wget/wget-1.20.2.tar.lz
Resolving ftp.gnu.org (ftp.gnu.org)... 209.51.188.20, 2001:470:142:3::b
Connecting to ftp.gnu.org (ftp.gnu.org)|209.51.188.20|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2134961 (2.0M) [application/x-tar]
Saving to: ?wget-1.20.2.tar.lz?

wget-1.20.2.tar.lz                               100%
[===================================================================>]   2.04M  2.12MB/s    in 1.0s

2019-04-04 12:09:24 (2.12 MB/s) - ?wget-1.20.2.tar.lz? saved [2134961/2134961]

sha256sum wget-1.20.2.tar.lz
84d3cbece8c08e130a8da0a72cf6e543a2adf58ca8ecf28726560b06243d4ce6  wget-1.20.2.tar.lz

Which matches current git.

-- 
Bye, Peter Korsgaard