Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[solved] emerge chocolate doom failed
View unanswered posts
View posts from last 24 hours
View posts from last 7 days

 
Reply to topic    Gentoo Forums Forum Index Deutsches Forum (German)
View previous topic :: View next topic  
Author Message
teddydeluxe
Tux's lil' helper
Tux's lil' helper


Joined: 08 Oct 2011
Posts: 114

PostPosted: Tue Apr 09, 2013 10:57 am    Post subject: [solved] emerge chocolate doom failed Reply with quote

hallo,

ich wollte mal chocolate doom drauf machen, aber es failed aufgrund eines syntax errors. liegt es an der unstable version oder kann man es irgendwie beheben ?

Code:

./docgen -m manpage.template ../src > chocolate-doom.6
./docgen -m default.cfg.template -c default.cfg ../src > default.cfg.5
./docgen -m extra.cfg.template -c chocolate-doom.cfg ../src > chocolate-doom.cfg.5
  File "./docgen", line 392
    print line.rstrip()
             ^
SyntaxError: invalid syntax
make[2]: *** [chocolate-doom.cfg.5] Error 1
make[2]: *** Waiting for unfinished jobs....
  File "./docgen", line 392
    print line.rstrip()
             ^
SyntaxError: invalid syntax
make[2]: *** [chocolate-doom.6] Error 1
  File "./docgen", line 392
    print line.rstrip()
             ^
SyntaxError: invalid syntax
make[2]: *** [default.cfg.5] Error 1
make[2]: Leaving directory `/var/tmp/portage/games-fps/chocolate-doom-1.2.1/work/chocolate-doom-1.2.1/man'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/games-fps/chocolate-doom-1.2.1/work/chocolate-doom-1.2.1'
make: *** [all] Error 2
emake failed
 * ERROR: games-fps/chocolate-doom-1.2.1 failed (compile phase):
 *   emake failed
 *
 * Call stack:
 *     ebuild.sh, line  93:  Called src_compile
 *   environment, line 3184:  Called die
 * The specific snippet of code:
 *       emake || die "emake failed"
 *
 * If you need support, post the output of `emerge --info '=games-fps/chocolate-doom-1.2.1'`,
 * the complete build log and the output of `emerge -pqv '=games-fps/chocolate-doom-1.2.1'`.
 * This ebuild is from an overlay named 'sunrise': '/var/lib/layman/sunrise/'
 * The complete build log is located at '/var/tmp/portage/games-fps/chocolate-doom-1.2.1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/games-fps/chocolate-doom-1.2.1/temp/environment'.
 * Working directory: '/var/tmp/portage/games-fps/chocolate-doom-1.2.1/work/chocolate-doom-1.2.1'
 * S: '/var/tmp/portage/games-fps/chocolate-doom-1.2.1/work/chocolate-doom-1.2.1'

>>> Failed to emerge games-fps/chocolate-doom-1.2.1, Log file:

>>>  '/var/tmp/portage/games-fps/chocolate-doom-1.2.1/temp/build.log'


Last edited by teddydeluxe on Wed Apr 10, 2013 3:43 pm; edited 1 time in total
Back to top
View user's profile Send private message
franzf
Advocate
Advocate


Joined: 29 Mar 2005
Posts: 3839
Location: Irgendwo im Nirgendwo

PostPosted: Tue Apr 09, 2013 11:27 am    Post subject: Reply with quote

Schaut so als hättest du python3.2 als system default, jedenfalls legt das der Fehler nahe.
WORKAROUND: eselect python set python2.7 -> emerge chocolate doom -> alten python3.x wieder setzen
LÖSUNG: Dem Script (./docgen) ein #!/usr/bin/python2 vorne anstellen/ändern. In jedem Fall nen bugreport aufmachen (build.log und emerge --info nicht vergessen!).
_________________
"der mac dennoch wesen geil"
Wolfram von Eschenbach, Parzival (Buch 1, Z. 7).
Ein frühes Statement gegen Windows.

My overlay
Back to top
View user's profile Send private message
teddydeluxe
Tux's lil' helper
Tux's lil' helper


Joined: 08 Oct 2011
Posts: 114

PostPosted: Tue Apr 09, 2013 3:06 pm    Post subject: Reply with quote

danke, der workaround hat geholfen. und im docgen file ist schon python2.7 im shebang angegeben.

ich soll den bug hier reporten ? ist das legitim, obwohl es aus einem overlay stammt und unstable ist ?
Back to top
View user's profile Send private message
AmonAmarth
l33t
l33t


Joined: 03 Mar 2005
Posts: 707

PostPosted: Wed Apr 10, 2013 11:42 am    Post subject: Reply with quote

teddydeluxe wrote:
danke, der workaround hat geholfen. und im docgen file ist schon python2.7 im shebang angegeben.

ich soll den bug hier reporten ? ist das legitim, obwohl es aus einem overlay stammt und unstable ist ?


wenn du den bug reportest dann hier: https://bugs.gentoo.org/
afair kann man dort auch auswählen das es zu einem overlay gehört.
Back to top
View user's profile Send private message
teddydeluxe
Tux's lil' helper
Tux's lil' helper


Joined: 08 Oct 2011
Posts: 114

PostPosted: Wed Apr 10, 2013 11:45 am    Post subject: Reply with quote

ich hab ihn schon reported, aber keine option für overlays gesehen

https://bugs.gentoo.org/show_bug.cgi?id=465374
Back to top
View user's profile Send private message
Josef.95
Advocate
Advocate


Joined: 03 Sep 2007
Posts: 2186
Location: Germany

PostPosted: Wed Apr 10, 2013 1:29 pm    Post subject: Reply with quote

Normal solten Bugs aus Overlays nicht im bugs.gentoo.org gepostet werden.
Wenn es sich aber, wie in diesem Fall, um ein Ebuild aus einen von gentoo Devs betreuten Overlay handelt, dann stelle dem Bug-Titel am besten ein Overlay Präfix voran - also zb
[sunrise overlay] Bug-Titel....
Back to top
View user's profile Send private message
teddydeluxe
Tux's lil' helper
Tux's lil' helper


Joined: 08 Oct 2011
Posts: 114

PostPosted: Wed Apr 10, 2013 3:43 pm    Post subject: Reply with quote

alles klar, danke
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Deutsches Forum (German) All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum