Skip to content

Conversation

@Ericson2314
Copy link
Contributor

Fixes #269

The "don't move the variables independently if you want to make install" part is a gross, but as neither wasi-sdk or Nixpkgs actually
needs make install (we both can just build right into the directories
we want) I figured it wasn't actually so heinous in practice.

@sbc100
Copy link
Member

sbc100 commented Mar 16, 2022

Seems reasonable.

I wonder if we should just remove the install target if its not being used anywhere (and therefore untested).

@sbc100
Copy link
Member

sbc100 commented Mar 16, 2022

I don't the github actions running here... any idea whats up with that?

@sbc100
Copy link
Member

sbc100 commented Mar 16, 2022

Looks like github actions might be down/struggling: https://www.githubstatus.com/


# Set the target.
CFLAGS = $(WASM_CFLAGS) --target=$(TARGET_TRIPLE)
CFLAGS += --target=$(TARGET_TRIPLE)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If someone overwrites CFLAGS on the make command line, does it override the --target=$(TARGET_TRIPLE) part too, or just the -O2 -DNDEBUG part?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think just the O2 -DNDEBUG part, but will check.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@sunfishcode I tested it, and it indeed the CLI was overriding everything. I added a bunch of override so that this is no longer the case, and just the -O2 -DNDEBUG part gets overridden.

@sunfishcode
Copy link
Member

The CI failure has errors like "cc: error: unrecognized command line option ‘--target=wasm32-wasi’"; it looks like it's using the host cc.

@Ericson2314
Copy link
Contributor Author

Oops forgot about CI and the README too. I did a grep and there should be no more pesky WASM_ at all, now.

@sunfishcode
Copy link
Member

The CI is now getting "fatal error: 'wasi/api.h' file not found" errors, and it's not immediately obvious what the problem is.

@Ericson2314
Copy link
Contributor Author

@sunfishcode I think I am using -isystem, but we in Nixpkgs were getting that error before too, and hacked around it. I tried various things, but nothing is making sense, so I messaged for help in the Zulip.

@Ericson2314 Ericson2314 force-pushed the standardize-build branch 4 times, most recently from 96808c1 to c28fd53 Compare March 21, 2022 22:23
Ericson2314 added a commit to Ericson2314/wasi-libc that referenced this pull request Mar 21, 2022
This is less of a sledgehammer, and prepares the way for WebAssembly#270.
sunfishcode pushed a commit that referenced this pull request Mar 21, 2022
This is less of a sledgehammer, and prepares the way for #270.
Ericson2314 added a commit to Ericson2314/wasi-libc that referenced this pull request Mar 21, 2022
Ericson2314 added a commit to Ericson2314/wasi-libc that referenced this pull request Mar 21, 2022
Ericson2314 added a commit to Ericson2314/wasi-libc that referenced this pull request Mar 22, 2022
Ericson2314 added a commit to Ericson2314/wasi-libc that referenced this pull request Mar 22, 2022
Ericson2314 added a commit to Ericson2314/wasi-libc that referenced this pull request Mar 22, 2022
Fixes WebAssembly#269

The "don't move the variables independently if you want to `make
install`" part is a gross, but as neither `wasi-sdk` or Nixpkgs actually
needs `make install` (we both can just build right into the directories
we want) I figured it wasn't actually so heinous in practice.

Also reorganize the the github actions CI slightly.
@Ericson2314
Copy link
Contributor Author

Closing since I broke up into bits.

@Ericson2314 Ericson2314 deleted the standardize-build branch March 23, 2022 02:48
Ericson2314 added a commit to Ericson2314/wasi-libc that referenced this pull request Apr 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

A few packaging nits, coming from Nixpkgs/NixOS

3 participants