Add mojo-libc package

[msaelices]

Checklist

• License file is packaged (see here for an example).
• Set the build number to 0 (for new packages, or if the version changed)
• Bumped the build number (if the version is unchanged)

[carolinefrasca]

Thanks for submitting, @msaelices! It looks like the recipe.yaml file lists https://github.com:msaelices/mojo-libc.git as the source rather than https://github.com/msaelices/mojo-libc.git - do you mind fixing?

[crisadamo]

LGTM

[yetalit]

I think you're using a wrong command: magic run mojo package libc -o ${PREFIX}/lib/mojo/libc.mojopkg
You're not also giving the correct path to the source code.
Use this instead: mojo package src/libc -o ${PREFIX}/lib/mojo/libc.mojopkg

[carolinefrasca]

@msaelices do you mind trying @yetalit's suggestion of mojo package src/libc -o ${PREFIX}/lib/mojo/libc.mojopkg for the build script? And then I can rerun the worfklows

[msaelices]

mojo package src/libc -o ${PREFIX}/lib/mojo/libc.mojopkg

Sorry for being so late. Fixed!

[carolinefrasca]

Thank you @msaelices! I assume this package isn't yet compatible with 24.6 yet, right? If so, do you mind specifying that in line 19 of your recipe.yaml file via - max ==24.6?

[msaelices]

Thank you @msaelices! I assume this package isn't yet compatible with 24.6 yet, right? If so, do you mind specifying that in line 19 of your recipe.yaml file via - max ==24.6?

Done: 70522a7

[carolinefrasca]

Thank you @msaelices! We're getting an error now from the test file:

 │ │ │ Testing commands:
 │ │ │ + mojo run test.mojo
 │ │ │ mojo: error: module does not define a `main` function
 │ │ │ × error Script failed with status 1
 │ │ │ × error Work directory: '/home/runner/work/modular-community/modular-community/output/bld/rattler-build_libc_1736882039/work/test/run/etc/conda/test-files/libc/0'
 │ │ │ × error To debug the build, run it manually in the work directory (execute the `./conda_build.sh` or `conda_build.bat` script)
 │ │ │
 │ │ ╰─────────────────── (took 4 seconds)
 │ │
 │ ╰─────────────────── (took 5 seconds)
 │
 ╰─────────────────── (took 17 seconds)
Error:   × failed to run test: Script failed

[carolinefrasca]

A quick update for everyone with open PRs that will hopefully make this process a bit easier: it's actually not necessary to include your test file(s) in the PR if you'd like to keep them in your source repo instead, as long as you include the test invocation and SHA/ID for your GitHub in the recipe file (here's an example with @TilliFe's Endia). Please let me know if you have any questions!