From: Ashwin Kumar <ashwinkumar3098@gmail.com>
To: gentoo-soc@lists.gentoo.org
Cc: Brian Dolbec <dolsen@gentoo.org>, Benda Xu <heroxbd@gentoo.org>
Subject: [gentoo-soc] Weekly Report: Project - Standalone Gentoo Chromebook
Date: Mon, 29 Jun 2020 14:10:44 +0530 [thread overview]
Message-ID: <CAP0gjOWmdLWWWoK5x07nZu4s7hMwzTQeWc2Es+=p48yNb9hB0Q@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 824 bytes --]
Hi everyone,
After expanding the root partition, I moved the toolchain built using
crossdev to crOS and configured it. But crOS core packages are compiled
with older version of gcc and glibc which is holding back to compile new
packages using portage. So, I thought to upgrade it to using the
Upgrading_Gentoo guide. But again, It broke the core packages. I also tried
to install to /usr/local but the problem persisted.
So, next week, I will be trying to setup a prefix for crOS. I have brief
understanding of it, so i would be following the manual bootstrap
<https://wiki.gentoo.org/wiki/Project:Prefix/Manual_Bootstrap> process and
also setting it up stage wise would make debugging easy. As a prerequisite,
I should have a toolchain packages which i already have built using
crosstool-ng
--
- Regards
Ashwin A Kumar
[-- Attachment #2: Type: text/html, Size: 1023 bytes --]
next reply other threads:[~2020-06-29 8:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 8:40 Ashwin Kumar [this message]
2020-07-01 9:19 ` [gentoo-soc] Re: Weekly Report: Project - Standalone Gentoo Chromebook Benda Xu
2020-07-01 10:41 ` Ashwin Kumar
-- strict thread matches above, loose matches on Subject: below --
2020-06-22 10:11 [gentoo-soc] " Ashwin Kumar
2020-06-16 1:11 Ashwin Kumar
2020-06-08 7:40 Ashwin Kumar
2020-06-28 14:24 ` Benda Xu
2020-06-29 1:39 ` Ashwin Kumar
2020-07-01 7:02 ` Benda Xu
2020-07-01 7:22 ` Ashwin Kumar
2020-07-01 8:23 ` Benda Xu
2020-07-01 8:46 ` Ashwin Kumar
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='CAP0gjOWmdLWWWoK5x07nZu4s7hMwzTQeWc2Es+=p48yNb9hB0Q@mail.gmail.com' \
--to=ashwinkumar3098@gmail.com \
--cc=dolsen@gentoo.org \
--cc=gentoo-soc@lists.gentoo.org \
--cc=heroxbd@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