Re: [proaudio] amsynth permission denied

["Mark Knecht" <markknecht@xxxxxxxxx>]

On 10/22/06, Mark Knecht <markknecht@xxxxxxxxx> wrote:
> On 10/22/06, Paul Winkler <pw_lists@xxxxxxxxxx> wrote:
> > On Sun, Oct 22, 2006 at 11:59:50AM +0200, Frieder B?rzele wrote:
> > > Paul Winkler wrote:
> > > >On Sat, Oct 21, 2006 at 11:47:29PM -0400, Paul Winkler wrote:
> > > >
> > > >> * [ ok ]/usr/lib/portage/bin/ebuild.sh: line 1454:
> > > >> *
> > > >> /home/pw/Downloads/Apps/Audio/proaudio_overlay/proaudio/media-sound/amsynth/amsynth-1.1.0-r1.ebuild:
> > > >> * Permission denied
> > > >>
> > > >
> > > >OK, I'm now getting this for horgand too.
> > > >Looks like my overlay is set up wrong or something.
> > > >Hints?
> > > >
> > > >
> > > what are the permissions for
> > > ls -la
> > > /home/pw/Downloads/Apps/Audio/proaudio_overlay/proaudio/media-sound/amsynth/amsynth-1.1.0-r1.ebuild:
> >
> > -rw-r-r-
> >
> > ... exactly the same as every ebuild under /usr/portage.
> >
> > and, as already noted, I'm emerging as root, which leads me
> > to suspect that something is lacking executable permissions,
> > but it's normal for ebuilds to not be executabe.
> > (If you look at the line 1454 mentioned in ebuild.sh, the ebuild
> > file is sourced, not executed.)
> >
>
> Hi Paul,
>    Where is your overlay? Is it on a separate partiton? If so were the
> permissions for the mounting directory changed approapriately? I've
> had similar problems with my music drives that were fixed by checking
> permissions both before and after the drives were mounted.
>
>    I'm emerging amsynth as a test now. If I have problems, which I
> doubt, I'll post back.
>
> - Mark

Paul,
  I didn't have your problem. Apparently there are other problems
here WRT AMD64 installations.

  Does this suggest there there needs to be some improvement to the
ebuild AMD64 systems?

Cheers,
Mark

<SNIP>
make[3]: Entering directory
`/var/tmp/portage/libsigc++-1.0.4-r2/work/libsigc++-
1.0.4/sigc++/config'
make[3]: Nothing to be done for `install-exec-am'.
/bin/sh ../../scripts/mkinstalldirs
/var/tmp/portage/libsigc++-1.0.4-r2/image//u
sr/lib64/sigc++-1.0/include
mkdir /var/tmp/portage/libsigc++-1.0.4-r2/image/usr
mkdir /var/tmp/portage/libsigc++-1.0.4-r2/image/usr/lib64
mkdir /var/tmp/portage/libsigc++-1.0.4-r2/image/usr/lib64/sigc++-1.0
mkdir /var/tmp/portage/libsigc++-1.0.4-r2/image/usr/lib64/sigc++-1.0/include
/bin/install -c -m 644 sigc++config.h
/var/tmp/portage/libsigc++-1.0.4-r2/image
//usr/lib64/sigc++-1.0/include/sigc++config.h
make  install-data-hook
make[4]: Entering directory
`/var/tmp/portage/libsigc++-1.0.4-r2/work/libsigc++-
1.0.4/sigc++/config'
#@if test -d "/usr/lib64/sigc++" ; then \
         echo ;\
         echo "*** WARNING ***:" ;\
         echo "You seem to have old libsigc++ config header files
installed in: " ;\
         echo ;\
         echo "  \"/usr/lib64/sigc++\"" ;\
         echo ;\
         echo "The entire directory will be removed now." ;\
         echo "To allow parallel installation of sigc++-1.0 and sigc++-1.2," ;\
         echo "the header files are now installed in a version
specific subdire ctory." ;\
         echo ; \
         rm -rf "/usr/lib64/sigc++" ;\
       fi
/bin/sh: -c: line 12: syntax error near unexpected token `fi'
/bin/sh: -c: line 12: `fi'
make[4]: *** [install-data-hook] Error 2
make[4]: Leaving directory
`/var/tmp/portage/libsigc++-1.0.4-r2/work/libsigc++-1
.0.4/sigc++/config'
make[3]: *** [install-data-am] Error 2
make[3]: Leaving directory
`/var/tmp/portage/libsigc++-1.0.4-r2/work/libsigc++-1
.0.4/sigc++/config'
make[2]: *** [install-am] Error 2
make[2]: Leaving directory
`/var/tmp/portage/libsigc++-1.0.4-r2/work/libsigc++-1
.0.4/sigc++/config'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory
`/var/tmp/portage/libsigc++-1.0.4-r2/work/libsigc++-1 .0.4/sigc++'
make: *** [install-recursive] Error 1

!!! ERROR: dev-libs/libsigc++-1.0.4-r2 failed.
Call stack:
 ebuild.sh, line 1546:   Called dyn_install
 ebuild.sh, line 1020:   Called src_install
 libsigc++-1.0.4-r2.ebuild, line 40:   Called die

!!! (no error message)
!!! If you need support, post the topmost build error, and the call
stack if rel evant.

lightning ~ #
<SNIP>