| View previous topic :: View next topic |
| Author |
Message |
TPC
Tux's lil' helper
Joined: 16 Sep 2003
Posts: 135
Location: Sweden
|
 Posted: Wed Dec 10, 2003 11:10 am Post subject: I get a sandbox error in the ebuild I'm creating |
 |
|
I'm creating an ebuild for snesamp-xmms, that haven't released anything yet, but they do have a cvs, so I'm making the ebuild for that. I took irssi-cvs as a template. I got it to download and compile the thing, but during the install part I get a sandbox error:
| Code: |
>>> Install snesamp-xmms-cvs-0.1 into /var/tmp/portage/snesamp-xmms-cvs-0.1/image/ category media-plugins
cp -f libsnesamp.so `xmms-config --plugin-dir`/Input/libsnesamp.so
ACCESS DENIED open_wr: /usr/lib/xmms/Input/libsnesamp.so
cp: cannot create normal file "/usr/lib/xmms/Input/libsnesamp.so": Access Denied
make: *** [install] Fel 1
!!! ERROR: media-plugins/snesamp-xmms-cvs-0.1 failed.
!!! Function src_install, Line 31, Exitcode 2
!!! (no error message)
--------------------------- ACCESS VIOLATION SUMMARY ---------------------------
LOG FILE = "/tmp/sandbox-snesamp-xmms-cvs-0.1-12012.log"
open_wr: /usr/lib/xmms/Input/libsnesamp.so
--------------------------------------------------------------------------------
|
The logfile mentioned contains this:
| Code: |
open_wr: /usr/lib/xmms/Input/libsnesamp.so
|
This is the install part of the ebuild:
| Code: |
src_install() {
make iinstall || die
}
|
someone told me to do this, but the exact same thing happened:
| Code: |
src_install() {
make DESTDIR=${D} install || die
}
|
suggestions? |
|
| Back to top |
|
 |
phosphan
n00b
Joined: 02 Dec 2003
Posts: 46
|
| Posted: Wed Dec 10, 2003 2:21 pm Post subject: Re: I get a sandbox error in the ebuild I'm creating |
|
|
| TPC wrote: |
cp: cannot create normal file "/usr/lib/xmms/Input/libsnesamp.so": Access Denied
This is the install part of the ebuild:
| Code: |
src_install() {
make iinstall || die
}
|
someone told me to do this, but the exact same thing happened:
| Code: |
src_install() {
make DESTDIR=${D} install || die
}
|
suggestions? |
Seems that package does not honor DESTDIR - an ugly tweak that could maybe work would be using einstall instead of install. If that doesn't work either, you will have to manually copy the files to the right directory which is below ${D} - not below /
All in all, I'd say: Check the Makefile if there's some chance to tell the program where the install directory really is. |
|
| Back to top |
|
|
akauppi
n00b
Joined: 23 Feb 2003
Posts: 23
Location: Finland
|
| Posted: Sun Dec 14, 2003 6:26 pm Post subject: I'm also having this problem.. |
|
|
emerge accuses me of "open_wr" on '/usr/include/smpeg/smpeg.h' which i _definately_ don't do.. That is, the builder reads the file but doesn't write it.
Am i missing something (do i really try to write?) or is there a logical help / explanation?
thanks.. -ak |
|
| Back to top |
|
|
phosphan
n00b
Joined: 02 Dec 2003
Posts: 46
|
| Posted: Sun Dec 14, 2003 7:22 pm Post subject: |
|
|
| I'm not a very good guesser. Having a look at the ebuild could maybe help. |
|
| Back to top |
|
|
akauppi
n00b
Joined: 23 Feb 2003
Posts: 23
Location: Finland
|
| Posted: Sun Dec 14, 2003 8:20 pm Post subject: bug 35821 |
|
|
I traced & reported this in the mean time:
https://bugs.gentoo.org/show_bug.cgi?id=35821
It was caused by using fopen("rt") in the build process, which portage mistakes for trying to write to that file. fopen("r") works, but i think a fix in portage would be appropriate.
If you'd like to help with the ebuild file overall, i would be honered. But it's your call..
-ak |
|
| Back to top |
|
|
Genone
Retired Dev
Joined: 14 Mar 2003
Posts: 9532
Location: beyond the rim
|
| Posted: Sun Dec 14, 2003 11:09 pm Post subject: |
|
|
| what's the "t" supposed to do ? It's not mentioned in the info- or manpage for fopen. The only supported characters in the OPENTYPE parameter after the mode are x and b (and the ,ccs= parameter). |
|
| Back to top |
|
|
akauppi
n00b
Joined: 23 Feb 2003
Posts: 23
Location: Finland
|
| Posted: Mon Dec 15, 2003 12:42 am Post subject: |
|
|
You're right - its not mentioned! *surprised*
It's the opposite of 'b', meaning a file should be opened in 't'ext mode (and not binary). Used in DOS/Win32, and i've always taken for granted that it's part of the ANSI C.
Anyways, since binary and text are the same on *nix, it can be simply ignored.
-ak |
|
| Back to top |
|
|
phosphan
n00b
Joined: 02 Dec 2003
Posts: 46
|
| Posted: Mon Dec 15, 2003 9:58 am Post subject: |
|
|
| I think the standard says that it's always a text stream as long as you don't open it for binary I/O. |
|
| Back to top |
|
|
|
Portage & Programming
