serasbails / mupen64plus

Automatically exported from code.google.com/p/mupen64plus
0 stars 0 forks source link

Mupen64 binary unusable #342

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Describe your system:
 - Operating System (be specific): Ubuntu 10.04 "Lucid Lynx" alpha 3
 - Machine type (32-bit or 64-bit): 64-bit
 - Mupen64Plus version: 1.99.3 
 - Plugins used: mupen64plus-video-rice.so, mupen64plus-rsp-hle.so,
mupen64plus-input-sdl.so, mupen64plus-audio-sdl.so

Mupen64Plus fails with the following:

rjarrrpcgp@rjarrrpcgp-klc:~/mupen64plus-bundle-linux64-1.99.3$
./mupen64plus /home/rjarrrpcgp/Nintendo 64 Games/Snowboard Kids 2 (U) [!].z64
bash: syntax error near unexpected token `('
rjarrrpcgp@rjarrrpcgp-klc:~/mupen64plus-bundle-linux64-1.99.3$

Original issue reported on code.google.com by rjarrrp...@yahoo.com on 1 Mar 2010 at 8:58

GoogleCodeExporter commented 8 years ago
This bug is invalid. Please use either correct escaping or ' around parameters 
to
tell your shell what is a single string parameter and what must be interpreted
extra.

Example would be:

./mupen64plus '/home/rjarrrpcgp/Nintendo 64 Games/Snowboard Kids 2 (U) [!].z64'

Original comment by sven@narfation.org on 1 Mar 2010 at 11:32

GoogleCodeExporter commented 8 years ago
Yep, confirmed, but is that error a bad coding? 

Original comment by rjarrrp...@yahoo.com on 2 Mar 2010 at 9:23

GoogleCodeExporter commented 8 years ago
Sry, but in this case it is a bad user :)

The parser of your shell (probably bash) gives the parameter as a single option 
only
if it is a single string without special characters and without spaces. The 
error you
get is before mupen64plus started at all - it is part of your shell. You can 
say that
a string with spaces doesn't meant to be "splitted at the space position" by 
using
either \ before each space (and different other special characters) or adding '
around the parameter. You can also use " around the string, but some other 
special
characters are still interpreted by your shell in that case.

It is complete normal to do so (because your shell does it and not the program 
which
is to be run). Try for example

$EDITOR test file

vs.

$EDITOR 'test file'

vs. 

$EDITOR test\ file

The first version opens two files - test and file. The second and third version 
opens
a file called "test file".

Original comment by sven@narfation.org on 2 Mar 2010 at 9:39

GoogleCodeExporter commented 8 years ago

Original comment by richard...@gmail.com on 4 Mar 2010 at 3:41