From: lin pro <linforpros@gmail.com>
To: gentoo-catalyst@lists.gentoo.org
Subject: [gentoo-catalyst] bootstrap.sh ewarn and command not found?
Date: Sat, 11 Jan 2014 17:03:04 -0600 [thread overview]
Message-ID: <CACU8XWkuMQ5M_tfPkODG=byS-MB8f0v=AxDXd6ROFtp=xH6Nrw@mail.gmail.com> (raw)
Hi,
I just wanted to ask whether this message is normal:
Gentoo Linux; http://www.gentoo.org/
Copyright 1999-2013 Gentoo Foundation; Distributed under the GPLv2
-------------------------------------------------------------------------------
[[ (0/3) Locating packages ]]
/usr/portage/scripts/bootstrap.sh: line 208: ewarn: command not found
/usr/portage/scripts/bootstrap.sh: line 209: ewarn: command not found
/usr/portage/scripts/bootstrap.sh: line 210: ewarn: command not found
/usr/portage/scripts/bootstrap.sh: line 211: ewarn: command not found
/usr/portage/scripts/bootstrap.sh: line 212: ewarn: command not found
/usr/portage/scripts/bootstrap.sh: line 213: ewarn: command not found
* Using baselayout : >=sys-apps/baselayout-2
* Using portage : portage
* Using os-headers : >=sys-kernel/linux-headers-3.9
* Using binutils : sys-devel/binutils
* Using gcc : sys-devel/gcc
* Using gettext : gettext
* Using libc : virtual/libc
* Using texinfo : sys-apps/texinfo
* Using zlib : zlib
* Using ncurses : ncurses
-------------------------------------------------------------------------------
[[ (1/3) Configuring environment ]]
-------------------------------------------------------------------------------
[[ (2/3) Updating portage ]]
Below is a more complete log:
http://bpaste.net/show/167138/
Stage2 spec file continues to build.
thank you
Ben
--
best regards
linforpros
next reply other threads:[~2014-01-11 23:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-11 23:03 lin pro [this message]
2014-01-12 2:48 ` [gentoo-catalyst] bootstrap.sh ewarn and command not found? Rick "Zero_Chaos" Farina
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='CACU8XWkuMQ5M_tfPkODG=byS-MB8f0v=AxDXd6ROFtp=xH6Nrw@mail.gmail.com' \
--to=linforpros@gmail.com \
--cc=gentoo-catalyst@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