From: Philipp Riegger <lists@anderedomain.de>
To: gentoo-soc@lists.gentoo.org, gnap-dev@lists.gentoo.org,
Christel Dahlskjaer <christel@gentoo.org>,
g2boojum@gentoo.org
Subject: [gnap-dev] GNAP Cross Compile Support: Status Report
Date: Tue, 10 Jul 2007 01:04:11 +0300 [thread overview]
Message-ID: <1184018652.32228.58.camel@b136a> (raw)
Hi.
I want to tell you about the status of my project.
My plan was like this:
Part 1: 2 weeks: Getting to know all the things.
Part 2: 4 weeks: Integrate cross compile support into gnap/catalyst.
Part 3: 2 weeks: Make gnap working on arches other than x86/amd64.
Part 4: 3 weeks: Proof of concept, support one board.
1 week of buffer.
If you want more details... well, its in the project description. Is
that pblicly available? I'm not sure. If not and you want to read it,
write a mail.
At the moment i'm slightle behind schedule and things also have changed
a little.
6 weeks are gone, i almost finished part 1. From my point of view, the
gnap_* scripts were in quite a bad state. I cleaned them up a bit, did
some refacturing and some improvements. Some small things still have to
be done, and i have to create the patchset, but i'm almost finished. The
plan is also to provide more than just one example configurations. Bass
was working on a new portage snapshot, a new seedstage and also a new
kernel. I tested this intensively, built several images and extensions
and looked into the kernel patches used (src.rpm from redhat/fedora).
For part 2 i'm still waiting for vapiers patches. I emailed him when the
project started, theese mails seem to have been lost. I pinged him on
IRC several times and finally reached him one week ago, he said he would
fiel a bug with the patches and inform me. Some people told me i should
start from scratch because vapier is quite busy and does not have time
to send the patches. But since he's much more into this and i really
want to see what he did, i have been waiting until now. It's not that i
have done nothing, i built some cross toolchains, looked into cross
building stage1 image building and played around a bit. I understood
most of how this stuff works (i hope) and i know how i would do this.
I'll remind vapier and if i don't hear anything positive i'll start from
scratch tomorrow. Time is running out.
I started on part 3 and it works better than i thought. The hardest part
was getting access to non-x64, non-amd64 machines and to get the rights
i need (root, at least in a chroot). Since half a week i have what i
need on ppc(64), i'm very happy with what i reached so far. Building
with glibc works great, i just have some problems getting started with
uclibc.
Part 4 is a little difficult. I could choose a ppc board and build
images on the ppc64 machines not using cross compilers, or i focuse more
on the other tasks and maybe leave that aside. I'll have to look into
that as soon as get further with the other stuff.
Ok, that's what i have. A little behind, but i'm working. There are some
problems i faced so far which surely made things harder for me:
- The last semester used more time than was planed. I did not have the
time to look into the things i am working with until summer of code
started, and this started for me about 1 1/2 week late because i still
had to finnish university stuff.
- My Laptop decided to not cooperate anymore with me and i had to get
an old PC from a friend and get it running/configure it so that i can
work with. Not that easy, since i'm abroad, just finished my exchange
studies, and i have nothing here.
- Well, i had to get used to a proper version control (the cmmands are
easy, it's harder to get as much out of it as possible).
But all of the above mentioned things are working now, i'm very happy
with all of them and i finally have my focus where it should be, on
GSoC.
Something on what i plan for the future:
Today/tomorrow i will sort all the things out i did as improvement for
the gnap_* scripts, finnish the work and clean things up. I'll rerun the
test builds over night to make (at least to some point) sure, that i did
not break anything.
I'll ping vapier again and again and like mentioned above, tomorrow i'll
look into that stuff myself. I should also make the decision about part
4, i'll discuss that in the next meeting with my mentors next monday and
make a decision next week.
Some things that need to be sorted out:
I read that kingtaco wanted to ask christel about misinforming me about
the soc box gentoo bought. Nobody ever told me what the misinformation
was. I also heard that it is not ready. Quite good, i'm not the only one
behind schedule. I heard that it is quite powerful (which might prove
very usefull for me) but it seems not to be possible to get the level of
access i need, which would be sudo for a special chroot script. The
usual hardened setup gentoo servers have and the script would make this
safe (at leat me and the admin of a box i got that level of access
thought that). Ok, 4 chroot restrictions from grsec need to be disabled
for catalyst, but it should still be quite safe. I never got a reply to
the mail i sent.
So much from me, if you want to know more, i read my mail.
Philipp
--
gnap-dev@gentoo.org mailing list
reply other threads:[~2007-07-09 22:10 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=1184018652.32228.58.camel@b136a \
--to=lists@anderedomain.de \
--cc=christel@gentoo.org \
--cc=g2boojum@gentoo.org \
--cc=gentoo-soc@lists.gentoo.org \
--cc=gnap-dev@lists.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