on 2008-10-11 at 15:17 Daniel Pielmeier wrote:
>Have you updated python recently and did not run python-updater? You
>can also try to re-emerge scons.
did both, but i get the same results.
>Sandbox errors are mostly caused when the ebuild tries to access the
>filesystem directly instead of using
luis jure schrieb am 11.10.2008 14:37:
> thanks for your answer, that doesn't seem to be the problem, though.
> i can install everything using install.py directly (not emerging with
> portage). also, using FEATURES="-sandbox" i can emerge without
> problems. so this problem seems to be related to
luis jure schrieb am 11.10.2008 14:37:
>> Can you emerge attr, then run lsattr on the files that cannot be
>> unlinked? I suspect that they might have extended attributes
>> preventing those file from being deleted.
>
> thanks for your answer, that doesn't seem to be the problem, though.
> i can
on 2008-10-10 at 18:36 Andrey Falko wrote:
>Can you emerge attr, then run lsattr on the files that cannot be
>unlinked? I suspect that they might have extended attributes
>preventing those file from being deleted.
thanks for your answer, that doesn't seem to be the problem, though.
i can insta
On Fri, Oct 10, 2008 at 6:19 PM, luis jure <[EMAIL PROTECTED]> wrote:
>
>
> hello list,
>
> i need some help to come up with an ebuild for csound (a language for
> sound synthesis).
>
> csound uses scons and then installs files using a script called
> install.py. compilation goes fine.
>
> executab
hello list,
i need some help to come up with an ebuild for csound (a language for
sound synthesis).
csound uses scons and then installs files using a script called
install.py. compilation goes fine.
executables, libraries, plugins and header files are correctly
installed (under /usr/bin, /us
6 matches
Mail list logo