Factorio Forums

All,

Took me a couple weeks to track this one down. Headless Factorio won't run without some possible necessary filesystem maintenance. See
viewtopic.php?f=49&t=34445&p=299832#p299832

I have no idea what is going on with linux, so I'm assigning it to oxyd to take a look on it.

I'm no linux expert, but you're welcome to pass any questions my way, I can get around in it just fine.


--iNick

Yes, Factorio requires /lib64/ld-linux-x86-64.so.2, that is not a bug. Changing it to /lib/ld-linux-x86-64.so.2 would break the game for everyone except you, so we obviously won't do that.

Oxyd,

Nor am I asking for that. But I'm not the only one with the problem. Search results tells me that. the problem does seem to be purely the so-called "filesystem hierarchy standard" that isn't standard. I'm no expert but if you only code 'ld-linux-x86-64.so.2' file as a requirement, and let the system find said file, you should be able to get both scenarios fixed? o.O

Because Factorio codes the /lib64 absolute path directory, problems surface, such as the one I wrote on, and others have also reported.


Does this make sense?
--iNick

inick wrote:Nor am I asking for that. But I'm not the only one with the problem. Search results tells me that. the problem does seem to be purely the so-called "filesystem hierarchy standard" that isn't standard. I'm no expert but if you only code 'ld-linux-x86-64.so.2' file as a requirement, and let the system find said file, you should be able to get both scenarios fixed? o.O

So far as I can tell, it has to be absolute path.

You can try it yourself: Run `patchelf --set-interpreter ld-linux-x86-64.so.2 factorio`, verify that the path is now relative in ldd output, and that factorio won't start.

Oxyd wrote:
So far as I can tell, it has to be absolute path.

You can try it yourself: Run `patchelf --set-interpreter ld-linux-x86-64.so.2 factorio`, verify that the path is now relative in ldd output, and that factorio won't start.

Well, thank you for this tip, thank you for the information! (beyond helpful!)

Here's what happened here. Downloaded patchelf and compiled it. ran it on a copy of Factorio binary to remove absolute pathnames. The modified Factorio binary now doesn't launch by itself or symlinking /lib64 (old fix). It still runs when forcibly specifying the interpreter on the command line.


As a result of this, I am more baffled. I see the results of my request has not helped the issue and learned something. You're right to move it to NaB, and I should probably let this thread go.
Thank you a lot! --iNick