chocolate-doom wget error...

Hello again.

Per the chocolate-doom wiki's instructions, I entered this command in at the shell:

wget http://www.chocolate-doom.org/build-chocolate-doom -O - | sh

This was the output:

--2010-12-15 11:06:47--  http://www.chocolate-doom.org/build-chocolate-doom
Resolving chocolate-doom.org... 216.34.181.97
Connecting to chocolate-doom.org|216.34.181.97|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/plain]
Saving to: “STDOUT”

    [<=>                                    ] 0           --.-K/s              sh: line 1: syntax error near unexpected token `('
sh: line 1: `�Y���οbL�S�T���r�NbT~ V��B�+�g�KpI��흙].�Sߵ%������Ã��j�:����1��H�JaU�X&Q����ӵ�d�&Rn��Q�M����E*2���Of1L���?����":��m�A���Z�w"C~E"�,�f������(       |�d,��
     �4\��8>Ȫ`���''
    [ <=>                                   ] 1,145       --.-K/s   in 0.02s   


Cannot write to “-” (Broken pipe).

I have no idea what a 'broken pipe' is...

What shell are you using?

Bash.

I ran it from the default (non-gui) command line.

$ wget http://www.chocolate-doom.org/build-chocolate-doom
Saving to: `build-chocolate-doom'

$ file build-chocolate-doom
build-chocolate-doom: gzip compressed data, from Unix

Virii said:

Hello again.

Per the chocolate-doom wiki's instructions, I entered this command in at the shell:

wget http://www.chocolate-doom.org/build-chocolate-doom -O - | sh

This was the output:

--2010-12-15 11:06:47--  http://www.chocolate-doom.org/build-chocolate-doom
Resolving chocolate-doom.org... 216.34.181.97
Connecting to chocolate-doom.org|216.34.181.97|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/plain]
Saving to: “STDOUT”

    [<=>                                    ] 0           --.-K/s              sh: line 1: syntax error near unexpected token `('
sh: line 1: `�Y���οbL�S�T���r�NbT~ V��B�+�g�KpI��흙].�Sߵ%������Ã��j�:����1��H�JaU�X&Q����ӵ�d�&Rn��Q�M����E*2���Of1L���?����":��m�A���Z�w"C~E"�,�f������(       |�d,��
     �4\��8>Ȫ`���''
    [ <=>                                   ] 1,145       --.-K/s   in 0.02s   


Cannot write to “-” (Broken pipe).

I have no idea what a 'broken pipe' is...

Broken pipe means that one of the pipe ends closed, hence it's broke.

Try maybe

wget http://www.chocolate-doom.org/build-chocolate-doom -O - | gunzip -C - | sh

Try maybe

wget http://www.chocolate-doom.org/build-chocolate-doom -O - | gunzip -C - | sh

Same.

Is there any way I can download the sources, and compile manually, instead of using the script?

Virii said:

Same.

Is there any way I can download the sources, and compile manually, instead of using the script?

If you use Debian (or Ubuntu)

apt-get install libsdl1.2-dev libsdl-mixer1.2-dev libsdl-net1.2-dev build-essential

If not then be sure you have subversion and essential building tools if you want the latest code.

svn co http://chocolate-doom.svn.sourceforge.net/svnroot/chocolate-doom/trunk/chocolate-doom chocolate-doom
cd chocolate-doom
./autogen.sh
make

Otherwise download the archive, extract it (tar -xvvf file.tar.alg) then navigate the the directory, then just do

./autogen.sh && make

Virii said:

Per the chocolate-doom wiki's instructions, I entered this command in at the shell:

wget http://www.chocolate-doom.org/build-chocolate-doom -O - | sh

This wouldn't happen to be an Ubuntu machine would it?

Unless you've gone in and changed it [1], /bin/sh on Ubuntu is dash, not bash, and dash can break things horribly, unfortunately.

Try this:

wget http://www.chocolate-doom.org/build-chocolate-doom -O - | bash

and see if it works then.

[1] https://wiki.ubuntu.com/DashAsBinSh

spicyjack said:

Unless you've gone in and changed it [1], /bin/sh on Ubuntu is dash, not bash, and dash can break things horribly, unfortunately.

In reality, bash broke thing horribly by extending the standard shell along with everyone using /bin/sh in shell scripts instead of /bin/bash.

The dash/bash thing shouldn't be an issue; I already know about it and the build script should work with dash.

It looks like there is something odd going on with the version of wget that you guys are using. When I wget the file, I get the script, but your version seems to be outputting a gzipped version. You could try installing curl instead, the script should prefer curl over wget.

If you're using Debian/Ubuntu you could just install the chocolate-doom package that the distro provides (though it might not be the latest version).

fraggle said:

It looks like there is something odd going on with the version of wget that you guys are using. When I wget the file, I get the script, but your version seems to be outputting a gzipped version.

I believe an older version of wget ignores content encoding. Your site is probably sending him a file encoded as gzip (server compresses file and sends as gzip) and his wget recieves the compressed data but thinks it's gzip data and doesn't actually decompress it when it downloads it. I've encountered this before.

It appears either one of these starts the compiling correctly.

GhostlyDeath said:

svn co http://chocolate-doom.svn.sourceforge.net/svnroot/chocolate-doom/trunk/chocolate-doom chocolate-doom
cd chocolate-doom
./autogen.sh
make

spicyjack said:

wget http://www.chocolate-doom.org/build-chocolate-doom -O - | bash

But... they both end on the same/similar error:

SyntaxError: invalid syntax
make[2]: *** [chocolate-doom.6] Error 1
make[2]: Leaving directory `/root/chocolate-doom/build/chocolate-doom-1.4.0/man\\\\\\\'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/root/chocolate-doom/build/chocolate-doom-1.4.0\\\\\\\'
make: *** [all] Error 2

Virii said:

It appears either one of these starts the compiling correctly.





But... they both end on the same/similar error:

A more complete log would be more descriptive rather than the last few lines.

GhostlyDeath said:

A more complete log would be more descriptive rather than the last few lines.

I'm sorry, but how would I do that?

Virii said:

I'm sorry, but how would I do that?

To write make output to a file, substitute

make

with

make 2>&1 | tee make.log

Post the make.log file to a pastebin (or some other publicly accessable website), then post the URL to your pastebin back into this thread so we can view the logs. Google pastebin if you don't know what one is.

GhostlyDeath said:

I believe an older version of wget ignores content encoding. Your site is probably sending him a file encoded as gzip (server compresses file and sends as gzip) and his wget recieves the compressed data but thinks it's gzip data and doesn't actually decompress it when it downloads it. I've encountered this before.

That was my assumption, yes. The Chocolate Doom website is hosted on Sourceforge so there isn't a lot I can do about it.

Here's the paste.

http://pastebin.com/D63YHPCK

I completely removed the chocolate-doom directory, and downloaded a fresh SVN.

So is it working okay now, then?

Let me guess ... This needs to be compiled as an normal user?

Anyways, The original topic has been solved. Thanks.