| View previous topic :: View next topic |
| Author |
Message |
tscolari l33t


Joined: 02 May 2004 Posts: 602 Location: curitiba - pr - Brazil
|
Posted: Mon Jun 06, 2005 11:06 am Post subject: trying to emerge foomatic |
|
|
Im trying to emerge foomatic here, but its giving this error:
while in ./config:
| Code: | GS /usr/bin/gs
checking how to redirect GhostScript output to fd 3... ACCESS DENIED open_wr: /dev/fd/3
./configure: line 1763: /dev/fd/3: Permission denied
using |/usr/bin/cat >&3
|
at the emerge:
| Code: | ...
chmod a+rx Makefile makeDefaults makeMan foomatic-configure foomatic-printjob foomatic-kitload foomatic-ppdfile foomatic-preferred-driver foomatic-cleanupdrivers foomatic-getpjloptions foomatic-addpjloptions foomatic-compiledb foomatic-fix-xml foomatic-nonumericalids foomatic-replaceoldprinterids foomatic-ppd-options foomatic-printermap-to-gimp-print-xml mkinstalldirs
--------------------------- ACCESS VIOLATION SUMMARY ---------------------------
LOG FILE = "/tmp/sandbox-net-print_-_foomatic-db-engine-3.0.2-9063.log"
open_wr: /dev/fd/3 (symlink to /proc/12692/fd/3)
--------------------------------------------------------------------------------
|
tjos /dev/fd/3 doesnt even exist...
how could i fix this? _________________ ------------------------------------
Tiago Scolari |
|
| Back to top |
|
 |
kernelsensei Bodhisattva


Joined: 22 Feb 2004 Posts: 5619 Location: Woustviller/Moselle/FRANCE (49.07°N;7.02°E)
|
Posted: Mon Jun 06, 2005 11:08 am Post subject: |
|
|
try that :
| Code: | | SANDBOX_DISABLED=1 emerge foomatic |
that's not always safe, you've to trust the ebuild ..
these ACCESS VIOLATION bugs have to be reported _________________ $ ruby -e'puts " .:@BFegiklnorst".unpack("x4ax7aaX6ax5aX15ax4aax6aaX7ax2aX5aX8 \
axaX3ax8aX4ax6aX3aX6ax3ax3aX9ax4ax2aX9axaX6ax3aX2ax4ax3aX4aXaX12ax10aaX7a").join' |
|
| Back to top |
|
 |
tuxian l33t

Joined: 26 Jan 2004 Posts: 766 Location: Austria
|
Posted: Mon Jun 06, 2005 7:22 pm Post subject: |
|
|
| kernel_sensei wrote: | try that :
| Code: | | SANDBOX_DISABLED=1 emerge foomatic |
that's not always safe, you've to trust the ebuild ..
these ACCESS VIOLATION bugs have to be reported |
Many thanks, now I was able to compile evolution  |
|
| Back to top |
|
 |
amne Bodhisattva


Joined: 17 Nov 2002 Posts: 6378 Location: Graz / EU
|
|
| Back to top |
|
 |
tuxian l33t

Joined: 26 Jan 2004 Posts: 766 Location: Austria
|
Posted: Mon Jun 06, 2005 7:56 pm Post subject: |
|
|
I know, but in my case it worked fine and didn't damage my system.
I also have a backup when I try such dangerous thinks  |
|
| Back to top |
|
 |
Tequilasour n00b

Joined: 12 May 2005 Posts: 5
|
Posted: Mon Jun 13, 2005 10:18 am Post subject: Same problem, bug not yet fixed? |
|
|
Hi!
I just encoutered the same problem like tscolari:
| Code: |
emerge -av foomatic
|
gives the following output in ./config:
| Code: |
...
checking for a2ps... A2PS_NOT_FOUND
checking for wget... /usr/bin/wget
checking for curl... /usr/bin/curl
checking for printf... /usr/bin/printf
checking GhostScript check... no
GS /usr/bin/gs
checking how to redirect GhostScript output to fd 3... ACCESS DENIED open_wr: /dev/fd/3
./configure: line 1763: /dev/fd/3: Permission denied
using |/usr/bin/cat >&3
checking for perl... /usr/bin/perl
Checking whether Perl will find libraries installed under /usr... yes
checking for bash... /bin/bash
checking for lpd/... no
checking for lp-errs... no
...
|
and later portage terminates complaining about an access violation
| Code: |
...
for m in foomatic-printjob foomatic-configure foomatic-combo-xml foomatic-perl-data foomatic-ppdfile foomatic-compiledb foomatic-ppd-options foomatic-kitload foomatic-getpjloptions foomatic-addpjloptions foomatic-preferred-driver foomatic-fix-xml foomatic-nonumericalids foomatic-replaceoldprinterids foomatic-printermap-to-gimp-print-xml; do \
/usr/bin/perl -p -i -e "s=use lib '.*lib/';\n==s" $m; \
done
chmod a+rx Makefile makeDefaults makeMan foomatic-configure foomatic-printjob foomatic-kitload foomatic-ppdfile foomatic-preferred-driver foomatic-cleanupdrivers foomatic-getpjloptions foomatic-addpjloptions foomatic-compiledb foomatic-fix-xml foomatic-nonumericalids foomatic-replaceoldprinterids foomatic-ppd-options foomatic-printermap-to-gimp-print-xml mkinstalldirs
--------------------------- ACCESS VIOLATION SUMMARY ---------------------------
LOG FILE = "/tmp/sandbox-net-print_-_foomatic-db-engine-3.0.2-26726.log"
open_wr: /dev/fd/3 (symlink to /proc/27106/fd/3)
--------------------------------------------------------------------------------
|
For me, this seems to be the same bug, albeit a different log-file that is accessed. Now, do I have to report this bug or would somebody be annoyed by some fool like me reporting the same bug for the umpteenth time? And how does this reporting business work anyway? Is there some kind of tutorial or howto? Can I also have a look at the progress, I mean whether somebody is already trying to fix this bug or something?
I'll better not try to emerge foomatic without sandbox-feature turned on, because I really don't want to screw up my system. |
|
| Back to top |
|
 |
amne Bodhisattva


Joined: 17 Nov 2002 Posts: 6378 Location: Graz / EU
|
Posted: Mon Jun 13, 2005 12:32 pm Post subject: |
|
|
Yes, this seems to be the same bug, and it should already be fixed. Afaik the number of the logfile is more or less randomish. Does the problem still appear after an emerge sync?
According to the bug it should either work with portage-2.0.51.19 or portage-2.0.51.22-r1 with sandbox-1.2.9. _________________ Dinosaur week! (Ok, this thread is so last week) |
|
| Back to top |
|
 |
Tequilasour n00b

Joined: 12 May 2005 Posts: 5
|
Posted: Mon Jun 13, 2005 1:11 pm Post subject: |
|
|
Telling me the version numbers of portage and sandbox was really a good idea. I should have thought of this myself but when I checked them, I found out that I had sandbox-1.2.8 installed.
After an upgrade to 1.2.9 it works fine now. Kind of embarrassing , but I'm still a noob, I guess. Thanks for the quick support! |
|
| Back to top |
|
 |
Stefan de Groot Tux's lil' helper

Joined: 19 Jul 2003 Posts: 82 Location: /home/ Netherlands/ Rotterdam
|
Posted: Sun Jun 26, 2005 11:35 am Post subject: |
|
|
| Tequilasour wrote: | Telling me the version numbers of portage and sandbox was really a good idea. I should have thought of this myself but when I checked them, I found out that I had sandbox-1.2.8 installed.
After an upgrade to 1.2.9 it works fine now. Kind of embarrassing , but I'm still a noob, I guess. Thanks for the quick support! |
This did help me to install it.
The bug look then anly be appear in sandbox 1.2.8 (and less?). I am happy that it worked now.   |
|
| Back to top |
|
 |
atom2103 n00b

Joined: 15 Mar 2004 Posts: 20
|
Posted: Fri Sep 30, 2005 1:16 am Post subject: Just 4 Info |
|
|
Hi!
Had the same problem while emerging foomatic.
It had not the permission to write to /dev/fd/3.
/dev/fd is symlinked to /proc/self/fd which means this should be all filedescriptors held by the current process.
/dev/fd/1 and 2 are stdout and stderr, but i was not able to check out which file the number 3 should be...
Disabling the sandbox worked fine. Thanks for the help anyway!
Using:
Linux atwork 2.6.12-gentoo-r3 #1 SMP Wed Jul 13 21:41:47 CEST 2005 i686 Intel(R) Pentium(R) 4 CPU 2.80GHz GenuineIntel GNU/Linux |
|
| Back to top |
|
 |
amne Bodhisattva


Joined: 17 Nov 2002 Posts: 6378 Location: Graz / EU
|
Posted: Fri Sep 30, 2005 11:58 am Post subject: |
|
|
_________________ Dinosaur week! (Ok, this thread is so last week) |
|
| Back to top |
|
 |
|