Comments by "Anony Mousse" (@anon_y_mousse) on "Is Odin "Programming done right"? (with Bill Hall)" video.

I don't know if it's just me, but Odin fails to build straight from the repository. I tried checking out prior tags to no avail. I suspect my clang/LLVM installation is out of date, but I'm not updating since it works now and updating always breaks things for me. This is the eternal problem I keep having with new languages, they refuse to build out of the box unless you have the exact same system they expect or the latest and greatest library versions or stand on one leg and cluck like a chicken. Zig at least provides a pre-built binary that runs, even if the language is half-baked and not completed, and Rust as ginormous as it is actually built from source, which is a first for me, but none of the nightly builds for Odin will even run because even my libffi is out of date. Is it too much to ask that compiler authors try to remember that all they're doing is converting source into a binary format and it doesn't require the latest and greatest of everything to do that. Hell, I'm not even finished with my own language, but every version compiled for every system I tested it on without the need to update anything and still generated code which ran. Except for the Pi version, which generated a binary that ran, but not on the Pi itself, because I haven't written the ARM code generator yet.
3
Update if anyone even bothers to read this, but I edited the source and deleted the bad option it was sending to clang and it built without errors. I'm assuming some configure script did it, but I'm not going to bother investigating further because no one cares.
1
What system are you on, do you update regularly and did you do more than just `make`? It flat out refused to build for me, and I wouldn't think a compiler should require the latest and greatest anything to work out of the box, but the nightly build even refused to run because I have an out of date libffi. I refuse to update for anything because it always breaks something, but it shouldn't be necessary given the nature of compilation.
1
@GroverAU Ah, you're on Windows. I guess I'll have to actually look into what the build system is doing wrong then, but it makes me wonder if Ginger Bill is on Windows and doing something improper that breaks it for me and no one else. But it's probably going to be a version mismatch kind of thing like it usually is, and I'll probably have to manually correct it like I usually do. Weird thing is, it gives me an error about a flag passed to clang, <dash>die and it asks if <dash><dash>dce was meant. I only have clang installed to compile others' projects. I've never used it myself and can't find any switch that matches either all three as separate characters or together as an accidental <dash><dash> turned into <dash>. As a side note, it's a good thing I was checking old posts because YouTube didn't notify me of your reply. Par for the course really. *Edited to change dashes into a textual format because YouTube wants to use MarkDown.
1
@GroverAU I thought I'd give that a try since some programs can be sensitive about where they're run from, but it still gives me the same error. If it makes any sense to you, it does generate a *.ll file that matches the *.odin file I feed it, but nothing further.
1
@GroverAU Don't know if you care, but I eventually got it to build correctly and generate binaries that work by editing the source code. I'm not sure if it was some configure script or what was responsible, but I just deleted the bad option it passed to clang and called it a day.
1