[SOLVED] r2183 at x264.nl

[Midzuki]

If you download any "flavor" of x264.exe, all you get is a 1.7KB file which is a copy of the current placeholder for JEEB's homepage :confused:

sudden server failure

Mikoto has taken over the stage. And no, I have no idea if I will get at least some data saved from the previous hoster, who seems to have gone missing like a boss. I do hope that nothing bad has happened to him.

etc etc etc

[JEEB]

This is a fail on both sides. I have no access to x264.nl unfortunately, so I can't fix it. jarod needs to reset and re-run the script of his.

You can get the builds here (http://x264.fushizen.eu/files/revision2183/) until then.

In short, nginx's default configuration has an active example line in it that basically leads to the fact that 404s don't happen. You get /index.html for non-found files. Which I forgot to deal with after moving to the new server. And then jarod's script finds a new revision, and goes to look for it. Since 404s don't happen, it "finds" what it's looking for and downloads it. Now, while I was told to make md5 hash files as well, this seemingly never gets checked during mirroring. And thus now both files are the index.html of my current setup.

herp a la derp

[Midzuki]

Thanx 4 the attention and for the up-to-date build

:thanks: :thanks: :thanks:

...
In short, nginx's default configuration has an active example line in it that basically leads to the fact that 404s don't happen. You get /index.html for non-found files. Which I forgot to deal with after moving to the new server. And then jarod's script finds a new revision, and goes to look for it. Since 404s don't happen, it "finds" what it's looking for and downloads it. Now, while I was told to make md5 hash files as well, this seemingly never gets checked during mirroring. And thus now both files are the index.html of my current setup.

¿ nginx ?

Argh :(

[JEEB]

¿ nginx ?
A web server (http://nginx.org/en/), specifically good at serving static content, or acting as a proxy for another web server handling the non-static content. Which has a funny feature in the default configuration file that led to this mishap happening (although the fact that the md5 hashes were never checked is amusing as well) :) .

[Midzuki]

The first time I read about "nginx" was I-don't-remember-when :) Thanks to Netcraft, I found out it was a great success among the p0rn sites :rolleyes: So it received all the prejudices from this old-fashioned man, who never managed to go beyond Apache 1.3 :o and Xitami :D

[Lorax2161]

Thank you for the builds, JEEB.

I started looking into how to compile when I couldn't find a binary, and with your uploads I have a chance to read more about it before I jump into the deep end of the pool.

[JEEB]

And just noting that x264.nl has been fixed now.

[Midzuki]

Thanks for the good-news :) ,
now let's give an olde and goode alarm clock to komisar :rolleyes:

[kypec]

Thanks for the good-news :) ,
now let's give an olde and goode alarm clock to komisar :rolleyes:
Exactly, I was about posting in this thread asking what's going on with that blessed man - he hasn't updated his builds since Jan 19 this year... wishing him all the best anyway!:p

[Midzuki]

For the curious:
commit 5c85e0a2b7992fcaab09418e3fcefc613cffc743 r2184
Author: Anton Mitrofanov
Date: Sun Mar 11 23:08:18 2012 -0700

Fix clobbering of mutex/cvs
Regression in r2183.
Bizarrely seemed to work on many platforms, but crashed on win64 and may have been slower.
Only affected sliced threads during encoding, but could cause crashes on x264 encoder close even without sliced threads.
O_o

[filler56789]

r2216 is available at Komisar's site since 2012-09-06, but x264.nl doesn't have it yet. :confused:

[JEEB]

r2216 is available at Komisar's site since 2012-09-06, but x264.nl doesn't have it yet. :confused:
Been busy with a new devbox and other stuff, built it just now on a university linux machine and uploaded to be mirrored. Should get propagated within some time.

The builds are without GPAC because it decided to be a complete failure with both the 0.5.0 release (configure fails straight away) and the svn trunk (fails when trying to link the gpac library with the unknown parameter '-z', which seemingly comes from the fact that if you are building on linux, you are only building for linux that the configure script has decided).