Is it safe to ignore errors while bootstrapping? Are they just a sign
of instability that is temporary and will become more stable during
the following steps?
emerge --oneshot --nodeps bash
make: *** [bash] Error 1
* ERROR: app-shells/bash-4.1_p5 failed:
* make failed
*
* Call stack:
* ebuild.sh, line 53: Called src_compile
* environment, line 2722: Called die
* The specific snippet of code:
* emake || die "make failed";
*
* If you need support, post the output of 'emerge --info
=app-shells/bash-4.1_p5',
* the complete build log and the output of 'emerge -pqv
=app-shells/bash-4.1_p5'.
* The complete build log is located at
'/home/elmar/gentoo/var/tmp/portage/app-shells/bash-4.1_p5/temp/build.log'.
* The ebuild environment file is located at
'/home/elmar/gentoo/var/tmp/portage/app-shells/bash-4.1_p5/temp/environment'.
* S: '/home/elmar/gentoo/var/tmp/portage/app-shells/bash-4.1_p5/work/bash-4.1'
Al
08-20-2010, 10:30 AM
Fabian Groffen
Bash failed. Are errors normal?
On 20-08-2010 12:24:45 +0200, Elmar Hinz wrote:
> Is it safe to ignore errors while bootstrapping? Are they just a sign
> of instability that is temporary and will become more stable during
> the following steps?
no.
> emerge --oneshot --nodeps bash
>
> make: *** [bash] Error 1
> * ERROR: app-shells/bash-4.1_p5 failed:
> * make failed
> *
> * Call stack:
> * ebuild.sh, line 53: Called src_compile
> * environment, line 2722: Called die
> * The specific snippet of code:
> * emake || die "make failed";
> *
> * If you need support, post the output of 'emerge --info
> =app-shells/bash-4.1_p5',
> * the complete build log and the output of 'emerge -pqv
> =app-shells/bash-4.1_p5'.
> * The complete build log is located at
> '/home/elmar/gentoo/var/tmp/portage/app-shells/bash-4.1_p5/temp/build.log'.
> * The ebuild environment file is located at
> '/home/elmar/gentoo/var/tmp/portage/app-shells/bash-4.1_p5/temp/environment'.
> * S: '/home/elmar/gentoo/var/tmp/portage/app-shells/bash-4.1_p5/work/bash-4.1'
the error right above your paste would clear up things
--
Fabian Groffen
Gentoo on a different level
08-20-2010, 10:46 AM
Elmar Hinz
Bash failed. Are errors normal?
>
> the error right above your paste would clear up things
>
I installed libncurses5-dev. Now it works.
The question was about the general approach, if such libs would come
on their own during the next roundtrips.
All
08-20-2010, 10:58 AM
Fabian Groffen
Bash failed. Are errors normal?
On 20-08-2010 12:46:14 +0200, Elmar Hinz wrote:
> >
> > the error right above your paste would clear up things
> >
>
> I installed libncurses5-dev. Now it works.
>
> The question was about the general approach, if such libs would come
> on their own during the next roundtrips.
IIRC, you have to emerge ncurses before bash (either explicitly, or
implicitly)
--
Fabian Groffen
Gentoo on a different level
08-20-2010, 11:10 AM
Elmar Hinz
Bash failed. Are errors normal?
>
> IIRC, you have to emerge ncurses before bash (either explicitly, or
> implicitly)
>
Which maybe means, that the solaris documentation requires an update.
Does emerge return an error value so that I can check for it in my
scripts? Well sure it does.
Al
08-20-2010, 11:17 AM
Fabian Groffen
Bash failed. Are errors normal?
On 20-08-2010 13:10:17 +0200, Elmar Hinz wrote:
> >
> > IIRC, you have to emerge ncurses before bash (either explicitly, or
> > implicitly)
> >
>
> Which maybe means, that the solaris documentation requires an update.
In this case, not really, since Solaris has curses available. Your
system apparently doesn't. Maybe a --nodeps ncurses will work in your
case. Otherwise the approach you chose was the best workaround for your
system.
> Does emerge return an error value so that I can check for it in my
> scripts? Well sure it does.
Indeed, yes it does.
--
Fabian Groffen
Gentoo on a different level
08-20-2010, 11:34 AM
Elmar Hinz
Bash failed. Are errors normal?
> system apparently doesn't. *Maybe a --nodeps ncurses will work in your
> case.
I try this to reach a general linux installer as the next step of my researches.
Al
08-20-2010, 08:17 PM
Elmar Hinz
Bash failed. Are errors normal?
2010/8/20 Elmar Hinz <oss.elmar@googlemail.com>:
>> system apparently doesn't. *Maybe a --nodeps ncurses will work in your
>> case.
>
> I try this to reach a general linux installer as the next step of my researches.
>
I tried it with tree and latest_tree. In both cases I run into this error.
<-------------------------------------------->
cd ../obj_s; -I../c++ -I../include
-I/home/elmar/gentoo/var/tmp/portage/sys-libs/ncurses-5.7-r4/work/ncurses-5.7/c++
-DHAVE_CONFIG_H
-I/home/elmar/gentoo/var/tmp/portage/sys-libs/ncurses-5.7-r4/work/ncurses-5.7/c++/../include
-I. -I../include -I/home/elmar/gentoo/usr/include -D_GNU_SOURCE
-D_FILE_OFFSET_BITS=64 -DXTSTRINGDEFINES -DNDEBUG
-I/home/elmar/gentoo/usr/include -O2 -march=i686 -pipe -m32 -fPIC -c
/home/elmar/gentoo/var/tmp/portage/sys-libs/ncurses-5.7-r4/work/ncurses-5.7/c++/cursesw.cc
/bin/bash: -I../c++: No such file or directory
<-------------------------------------------->
Remember is the step just before emerging the gentoo bash, in my case ubuntu.
GNU bash, Version 4.1.5(1)-release (i486-pc-linux-gnu)
Al
08-20-2010, 08:22 PM
Fabian Groffen
Bash failed. Are errors normal?
On 20-08-2010 22:17:16 +0200, Elmar Hinz wrote:
> 2010/8/20 Elmar Hinz <oss.elmar@googlemail.com>:
> >> system apparently doesn't. *Maybe a --nodeps ncurses will work in your
> >> case.
> >
> > I try this to reach a general linux installer as the next step of my researches.
> >
>
> I tried it with tree and latest_tree. In both cases I run into this error.
ncurses needs another tool, that's why we don't emerge the deps of bash,
it goes too deep. Getting ncurses-dev was the right thing you did.
> <-------------------------------------------->
> cd ../obj_s; -I../c++ -I../include
> -I/home/elmar/gentoo/var/tmp/portage/sys-libs/ncurses-5.7-r4/work/ncurses-5.7/c++
> -DHAVE_CONFIG_H
> -I/home/elmar/gentoo/var/tmp/portage/sys-libs/ncurses-5.7-r4/work/ncurses-5.7/c++/../include
> -I. -I../include -I/home/elmar/gentoo/usr/include -D_GNU_SOURCE
> -D_FILE_OFFSET_BITS=64 -DXTSTRINGDEFINES -DNDEBUG
> -I/home/elmar/gentoo/usr/include -O2 -march=i686 -pipe -m32 -fPIC -c
> /home/elmar/gentoo/var/tmp/portage/sys-libs/ncurses-5.7-r4/work/ncurses-5.7/c++/cursesw.cc
> /bin/bash: -I../c++: No such file or directory
> <-------------------------------------------->
>
>
> I find this pathes in the tree:
>
> gentoo/var/tmp/portage/sys-libs/ncurses-5.7-r4/work/narrowc/obj_s/
> gentoo/var/tmp/portage/sys-libs/ncurses-5.7-r4/work/narrowc/c++/
>
> gentoo/var/tmp/portage/sys-libs/ncurses-5.7-r4/work/ncurses-5.7/c++/
>
> Where is that directory missing?
>
> Remember is the step just before emerging the gentoo bash, in my case ubuntu.
> GNU bash, Version 4.1.5(1)-release (i486-pc-linux-gnu)
>
>
>
> Al
>
--
Fabian Groffen
Gentoo on a different level
08-20-2010, 08:34 PM
Elmar Hinz
Bash failed. Are errors normal?
2010/8/20 Fabian Groffen <grobian@gentoo.org>:
> On 20-08-2010 22:17:16 +0200, Elmar Hinz wrote:
>> 2010/8/20 Elmar Hinz <oss.elmar@googlemail.com>:
>> >> system apparently doesn't. *Maybe a --nodeps ncurses will work in your
>> >> case.
>> >
>> > I try this to reach a general linux installer as the next step of my researches.
>> >
>>
>> I tried it with tree and latest_tree. In both cases I run into this error.
>
> ncurses needs another tool, that's why we don't emerge the deps of bash,
> it goes too deep. *Getting ncurses-dev was the right thing you did.
>
OK, than a skip this requirement for now.
I have my installer script ready so far, but it still does not go to
the end. The next problem I run into is this thingy with pax-utils
complaining about shebangs.
Oh, no! This time it is in binutils. Each run something new. Very strange!
Bash failed. Are errors normal?
