| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Still emitting a bunch of warnings on OpenBSD, though.
|
| |
|
|
|
|
| |
I can't select C99 in luasocket, because I don't know how to include
the definition of struct timespec. All this fucking complexity. But
hopefully things will build on OpenBSD now.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Since everything is in my control there's no need to parameterize
include paths.
It's a struggle to get make to run when it should. Lying that something
is phony stops working when it's a dependency. Commands get
unnecessarily run. Just fucking run recursive makes directly in the
target that depends on them.
|
| |
|
|
|
| |
Now we have 2 probably-valid warnings caused by my edits, and 1
false-positive.
|
| |
|
|
|
|
|
|
|
|
| |
I'd like to enable -Wextra as well, but that creates some false
positives.
I've at least made my changes clean w.r.t. -Wextra.
Now we have 4 remaining warnings with gcc 9.3 that seem genuine. Need to
fix those.
|
| |
|
|
|
|
| |
What in the world is up with the $MYCFLAGS convention in these Lua
makefiles? I don't know, but I'm going to leave it undisturbed as far as
possible.
|
| |
|
|
| |
cc and gcc are identical on my system. But why rely on that.
|
| | |
|
| |
|
|
| |
Hilariously, I wasn't linking against it in the first place.
|
| | |
|
|
|
Still extremely ugly:
- I've inlined all the namespaces under ssl, so you need to know that
context and config are related to ssl.
- luasec comes with its own copy of luasocket. I haven't deduped that
yet.
|