Bryant Mairs

@CryZe I noticed that you aren't testing on `x86_64-android`. It doesn't work for me in my testing, but I wanted to see if you even tried it before I start...

As `cross` says it's supportes.

Well I'm getting the following error. I'd be curious if you're getting the same (I'd expect you would). ``` cross build --target x86_64-linux-android Updating git repository `https://github.com/rust-lang/libc` Updating registry `https://github.com/rust-lang/crates.io-index`...

@japaric Just wanted to ping you on this? Shouldn't require too much review to get this merged.

@japaric This was merged into cross in japaric/cross#89. I don't have an iOS system to test on, so I guess this is stalled until someone steps up for that?

I think this is what you were asking for. I should note that I was expecting japaric/cross#91 to block this as then we can add a default whitelist for RUSTFLAGS...

Interesting, it actually looks like `RUSTFLAGS` is being passed through on mac. On Travis only the `DISABLE_TEST` targets should have passed, but mac also passed and shows the test as...

Getting back to this now that japaric/cross#91 is merged, I'm actually uncertain how to set up `Cross.toml` for these tests in order to pass through `RUSTFLAGS`. Additionally, should this whitelist...

I think I understand. So this would require another change to `cross` such that it can pull config values from environment variables as you described above. And then in addition...

I fixed everything I think, but this relies on changes in Cross such that it will read from environment variables, IIUC. So this will block until I get that functionality...