weird portage errors
 

After emerging the latest portage and emerging packages, I'm seeing this
after a successful completed install....

>>> Completed installing cvs-1.12.12-r9 into
/j/var/tmp/portage/dev-vcs/cvs-1.12.12-r9/image/

/usr/lib/portage/bin/helper-functions.sh: line 75: mj_control_fd: File
exists
/usr/lib/portage/bin/ebuild-helpers/prepstrip: line 205: scanelf:
command not found
/usr/lib/portage/bin/helper-functions.sh: line 40: read: pid: invalid
file descriptor specification
/usr/lib/portage/bin/ebuild-helpers/prepstrip: exit trap: line 1: syntax
error near unexpected token `newline'
/usr/lib/portage/bin/ebuild-helpers/prepstrip: exit trap: line 1: `echo
${BASHPID} $? >&'
/usr/lib/portage/bin/ebuild-helpers/prepstrip: line 294: scanelf:
command not found
/usr/lib/portage/bin/helper-functions.sh: line 75: mj_control_fd: File
exists
/usr/lib/portage/bin/helper-functions.sh: line 40: read: pid: invalid
file descriptor specification
/usr/lib/portage/bin/helper-functions.sh: line 40: read: pid: invalid
file descriptor specification
/usr/lib/portage/bin/helper-functions.sh: line 40: read: pid: invalid
file descriptor specification
/usr/lib/portage/bin/helper-functions.sh: line 40: read: pid: invalid
file descriptor specification
/usr/lib/portage/bin/ebuild-helpers/ecompressdir: exit trap: line 1:
syntax error near unexpected token `newline'
/usr/lib/portage/bin/ebuild-helpers/ecompressdir: exit trap: line 1:
`echo ${BASHPID} $? >&'
/usr/lib/portage/bin/helper-functions.sh: line 40: read: pid: invalid
file descriptor specification
/usr/lib/portage/bin/ebuild-helpers/ecompressdir: exit trap: line 1:
syntax error near unexpected token `newline'
/usr/lib/portage/bin/ebuild-helpers/ecompressdir: exit trap: line 1:
`echo ${BASHPID} $? >&'
/usr/lib/portage/bin/ebuild-helpers/ecompressdir: exit trap: line 1:
syntax error near unexpected token `newline'
/usr/lib/portage/bin/ebuild-helpers/ecompressdir: exit trap: line 1:
`echo ${BASHPID} $? >&'
/usr/lib/portage/bin/ebuild-helpers/ecompressdir: exit trap: line 1:
syntax error near unexpected token `newline'
/usr/lib/portage/bin/ebuild-helpers/ecompressdir: exit trap: line 1:
`echo ${BASHPID} $? >&'
/usr/lib/portage/bin/ebuild-helpers/ecompressdir: exit trap: line 1:
syntax error near unexpected token `newline'
/usr/lib/portage/bin/ebuild-helpers/ecompressdir: exit trap: line 1:
`echo ${BASHPID} $? >&'
ecompressdir: bzip2 -9 /usr/share/man
/usr/lib/portage/bin/helper-functions.sh: line 40: read: pid: invalid
file descriptor specification
/usr/lib/portage/bin/helper-functions.sh: line 40: read: pid: invalid
file descriptor specification
/usr/lib/portage/bin/helper-functions.sh: line 40: read: pid: invalid
file descriptor specification
/usr/lib/portage/bin/helper-functions.sh: line 40: read: pid: invalid
file descriptor specification
/usr/lib/portage/bin/ebuild-helpers/ecompressdir: exit trap: line 1:
syntax error near unexpected token `newline'
/usr/lib/portage/bin/ebuild-helpers/ecompressdir: exit trap: line 1:
`echo ${BASHPID} $? >&'
/usr/lib/portage/bin/helper-functions.sh: line 40: read: pid: invalid
file descriptor specification
/usr/lib/portage/bin/ebuild-helpers/ecompressdir: exit trap: line 1:
syntax error near unexpected token `newline'
/usr/lib/portage/bin/ebuild-helpers/ecompressdir: exit trap: line 1:
`echo ${BASHPID} $? >&'
/usr/lib/portage/bin/ebuild-helpers/ecompressdir: exit trap: line 1:
syntax error near unexpected token `newline'
/usr/lib/portage/bin/ebuild-helpers/ecompressdir: exit trap: line 1:
`echo ${BASHPID} $? >&'
/usr/lib/portage/bin/ebuild-helpers/ecompressdir: exit trap: line 1:
syntax error near unexpected token `newline'
/usr/lib/portage/bin/ebuild-helpers/ecompressdir: exit trap: line 1:
`echo ${BASHPID} $? >&'
/usr/lib/portage/bin/ebuild-helpers/ecompressdir: exit trap: line 1:
syntax error near unexpected token `newline'
/usr/lib/portage/bin/ebuild-helpers/ecompressdir: exit trap: line 1:
`echo ${BASHPID} $? >&'

Anyone else ?

Alan.

weird portage errors
 

Alan,

On 10-08-2012 10:58:52 +0100, Alan Hourihane wrote:
> After emerging the latest portage and emerging packages, I'm seeing this
> after a successful completed install....
>
> >>> Completed installing cvs-1.12.12-r9 into
> /j/var/tmp/portage/dev-vcs/cvs-1.12.12-r9/image/
>
> /usr/lib/portage/bin/helper-functions.sh: line 75: mj_control_fd: File
> exists

I haven't see this happening myself. It seems your linenumbers are
different, but it's the multijob stuff (multijob_init). It probably
helps if you can figure out which call is bombing out here.

--
Fabian Groffen
Gentoo on a different level

weird portage errors
 

On 10-08-2012 10:58:52 +0100, Alan Hourihane wrote:
> After emerging the latest portage and emerging packages, I'm seeing this
> after a successful completed install....
>
> >>> Completed installing cvs-1.12.12-r9 into
> /j/var/tmp/portage/dev-vcs/cvs-1.12.12-r9/image/
>
> /usr/lib/portage/bin/helper-functions.sh: line 75: mj_control_fd: File

I get on OpenIndiana now:

* redirect_alloc_fd failed

which looks similar to your error, but investigations pending...


--
Fabian Groffen
Gentoo on a different level

weird portage errors
 

On 20-08-2012 17:09:07 +0200, Fabian Groffen wrote:
> On 10-08-2012 10:58:52 +0100, Alan Hourihane wrote:
> > After emerging the latest portage and emerging packages, I'm seeing this
> > after a successful completed install....
> >
> > >>> Completed installing cvs-1.12.12-r9 into
> > /j/var/tmp/portage/dev-vcs/cvs-1.12.12-r9/image/
> >
> > /usr/lib/portage/bin/helper-functions.sh: line 75: mj_control_fd: File
>
> I get on OpenIndiana now:
>
> * redirect_alloc_fd failed
>
> which looks similar to your error, but investigations pending...

Ok, this turns out to be redirect_alloc_fd doing something that only
works on Linux to find a free file descriptor, it seems. At least it
fails hard on Solaris, so it needs bash 4.1 at least, because there this
is a bash built-in, which /does/ seem to work correctly.


--
Fabian Groffen
Gentoo on a different level

weird portage errors
 

On 08/20/12 16:09, Fabian Groffen wrote:
> On 10-08-2012 10:58:52 +0100, Alan Hourihane wrote:
>> After emerging the latest portage and emerging packages, I'm seeing this
>> after a successful completed install....
>>
>>>>> Completed installing cvs-1.12.12-r9 into
>> /j/var/tmp/portage/dev-vcs/cvs-1.12.12-r9/image/
>>
>> /usr/lib/portage/bin/helper-functions.sh: line 75: mj_control_fd: File
> I get on OpenIndiana now:
>
> * redirect_alloc_fd failed
>
> which looks similar to your error, but investigations pending...
>
>
Managed to fix my error, it was a local problem with my libc.

Alan.