Merge pull request #431 from rustcoreutils/merge-c99

merge cc

Author: jgarzik

.github/workflows/TestingCI.yml

@@ -6,12 +6,24 @@ on:
 
 env:
   CARGO_TERM_COLOR: always
+  RUST_BACKTRACE: 1
 
 jobs:
   linux-ubuntu:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
+      - name: System info
+        run: |
+          echo "=== Architecture ==="
+          uname -a
+          echo "=== CPU ==="
+          lscpu | head -20
+          echo "=== Toolchain ==="
+          rustc --version
+          cargo --version
+          cc --version || true
+          as --version || true
       - name: Fetch
         run: cargo fetch
       - name: Build
@@ -39,9 +51,26 @@ jobs:
         with:
           path: ~/.cargo/registry/cache
           key: registry-${{ runner.os }}-${{ steps.rust-version.outputs.version }}-${{ hashFiles('Cargo.lock') }}
+      - name: System info
+        run: |
+          echo "=== Architecture ==="
+          uname -a
+          arch
+          echo "=== Toolchain ==="
+          rustc --version
+          cargo --version
+          cc --version || true
+          as -version || true
+          echo "=== Xcode ==="
+          xcodebuild -version || true
       - name: Fetch
         run: cargo fetch
       - name: Build
         run: cargo build --release --verbose
       - name: Run tests
         run: cargo test --release --verbose
+      - name: Run cc tests (detailed)
+        if: failure()
+        run: |
+          echo "=== Re-running cc tests with more detail ==="
+          cargo test --release -p posixutils-cc --verbose -- --nocapture --test-threads=1 2>&1 | head -500

CONTRIBUTING.md

@@ -71,6 +71,9 @@ There are several ways to contribute to posixutils-rs:
 	   static input data, and compares output with
 	   static output data (OS reference data).
 * Use plib's TestPlan framework for integration tests.
+* Integration test harness should ONLY contain `mod` statements.
+  Test logic is in $module/tests/$category/mod.rs files.
 * Only "quick" tests should be run automatically in `cargo test`
 * Longer tests, or tests requiring root access, should be triggered
   via special environment variables.
+

Cargo.lock

@@ -4,6 +4,7 @@ resolver = "2"
 members = [
 	"awk",
 	"calc",
+	"cc",
 	"datetime",
 	"dev",
 	"display",