shell-usage on stage

Reinhard bookreader at gmx.com
Mon Apr 5 15:10:12 PDT 2004


On Sunday 04 April 2004 20:06, Kevin P. Fleming wrote:
> Reinhard wrote:
> >   18690 I: Creating directory ../binutils-build (parents)
> >   18691 E: Changing current directory to /tools/build/../binutils-build
> > failed:
> >   18692 E:     No such file or directory
> >   18693 I: Exiting stage: Installing Binutils-2.14 - Pass 1
> >   18694 W: Unable to remove /var/log/ALFS/stamps/Binutils.
> >
> > I don't understand the error from line 18691. Where comes that path from?
> > Is it a bug or my misunderstanding?
>
> That error is not coming from the profile fragment you posted; it's
> coming from something _after_ the mkdir element.

Thanks for that hint.  - I think, it was the breakthrough in profile-building.
I found a bug in namespace-handling.

Now I successfully build binutils and nearly complete of gcc-pass1.
At building the libbackend.a gcc trappes the same way, as the cvs of glibc.

29331 I: /var/log/ALFS/packages/GCC-testsuite-3.3.2.xml
29332 E: <stage> child (2142) killed by signal 11.
29333 I: Exiting stage: Installing GCC-3.3.2 - Pass 1
29334 W: Unable to remove /var/log/ALFS/stamps/GCC-testsuite.

> > - nALFS traps when you fetch glibc with cvs (chapter materials / packages)
> >       the tar after cvs-fetch works well.
>
> I'm not sure I follow this; what does "fetch glibc with cvs" mean? Are 
> you running a cvs command from your profile?

Yes. In newxml as well as belfs there are commands on how to build a tarball 
of glibc from cvs-archive. 
Yes I executed the cvs from profile - and it failed nearly to the end with: 
	killed by signal 11.

How about your test-system? Could you fix it?

Kind regards

Reinhard




More information about the alfs-discuss mailing list