rofl0r

@afterdelight thanks for the ytdl-patched linked, it took me a while to scrutinize the repo in order to figure out whether it can be trusted. this is also the main...

> Provided that a binary is available for your machine architecture ... not only that, even a libc difference makes a precompiled binary unusable (unless everything is statically linked). in...

well, i thought i'd first hear what the maintainer has to say, if anything at all, because making the patch fit for primetime would require to check for availability of...

linking to my commit also serves another purpose: to make the author realize what other patches distros currently use to make his package compile. for example we can find the...

your unprofessional, minimalistic issue description leaves it unclear whether you refer to compilation of lacc itself, or the output of it, but either way it's the choice of the user...

_start is in your libc's startup files crt0.o etc. if the compiler was properly `configure`d it should automatically add them when compiling things.

your issue is not whether it exists or not, but whether it is added to the `ld` command that's used when linking your executable together. run your compiler command via...

the only lines relevant are the ones containing `execve`. as you can see lacc, doesn't add any startfiles (crt*.o) to the linker command, that's why _start isnt found. output from...

> When I add the parameter --dynamic-linker, the same warning is still happening. not what i was talking about. look at what crt* is added by your gcc. > I...

you need `-s 256 -v` args to strace to see the crt stuff, as its cutting them off.