From: listout <brahmajit.xyz@gmail.com>
To: gentoo-soc <gentoo-soc@lists.gentoo.org>
Cc: sam <sam@gentoo.org>, juippis <juippis@gentoo.org>,
arsen <arsen@gentoo.org>
Subject: [gentoo-soc] Week 2 report on porting Gentoo packages to modern C
Date: Sun, 11 Jun 2023 21:24:03 +0530 [thread overview]
Message-ID: <yttuaetxmllv2sqz453dyhne7aifii2kzk6divq2vhekigasxq@fxejgel7kzjr> (raw)
Hello all,
This is my week 2 report for my SoC 2023 project "Modern C porting of
Gentoo packages" at Gentoo Linux.
Current:
- I've stuck to my proposal and mainly worked on the
"Wincompatible-function-pointer-types" bugs. Honestly, nothing much
interesting did happen.
- I was not able to work for 2 days, due to some personal health issues,
I plan on making up for them in the following weeks/days.
- MUSL testing environment (chroot) is set up and bugs are being tested
against it. There are some bugs that still need improvements/fixes on
musl
- Got more of my bugs reviewed by my mentor/s, while I do need to work
on those updates.
Next:
- While the "Wincompatible-function-pointer-types" bugs are not
completely removed from the bug list, I do plan on working on
different kinds of bugs in the coming weeks, while also trying to keep
up with the aforementioned bug types.
- For the first half of the coming two weeks the plan is to work on
"Wimplicit-function-declaration" type of bugs, and "Wimplicit-int" on
the later half. To be honest, I didn't see many bugs in the later type
in the bug list, hence if there are fewer I can dedicate some of the
time to the "Wincompatible-function-pointer-types" bugs.
- Since I have the musl testing environment up and running, I plan of
testing/patching most of the bugs on musl environment, especially the
ones that were found in the musl-clang environment.
That is it, hopefully, I'll come across something interesting for people
reading here.
reply other threads:[~2023-06-11 15:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yttuaetxmllv2sqz453dyhne7aifii2kzk6divq2vhekigasxq@fxejgel7kzjr \
--to=brahmajit.xyz@gmail.com \
--cc=arsen@gentoo.org \
--cc=gentoo-soc@lists.gentoo.org \
--cc=juippis@gentoo.org \
--cc=sam@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox