-
Notifications
You must be signed in to change notification settings - Fork 0
Compilation Errors
HuyHAP edited this page Mar 19, 2026
·
3 revisions
This page is the compile-focused companion to Troubleshooting.
The detailed error workflow has been merged into the main troubleshooting guide so there is one canonical place for build failures, runtime failures, and debugging steps.
On Windows, start with:
lp file.lp --gcc
lp build file.lp --release --gccIf you are checking the native default path, remember that lp file.lp uses the ASM backend and expects a working assembler/linker toolchain.
lp file.lp -o output.cThen inspect the generated file around the failing line.
gcc -Wall -Wextra -std=c11 output.c -o outputThis is often the fastest way to surface missing symbols, invalid lowering, or host-toolchain warnings.
For the full troubleshooting flow, go to Troubleshooting, especially:
- compile and backend checks
- generated-C debugging
- runtime debugging
- common LP coding mistakes
| Category | Typical symptom |
|---|---|
| LP syntax error | parser or codegen error before C compilation |
| lowering/codegen issue | generated C fails under GCC |
| missing toolchain |
gcc, as, or ld not found |
| stale assumptions from docs | example parses, but current build path is not reliable end-to-end |
Back to Home | GitHub Repo | Issues
- Home
- Installation and Setup
- First Programs
- Language Basics
- Quick Reference
- Troubleshooting
- Known Limitations
- Language Reference
- Expressions and Collections
- Object-Oriented Programming
- Error Handling
- Feature Overview
- Feature Status
- Runtime Modules
- Concurrency and Parallelism
- Parallel and GPU Computing
- Security Overview
- Security Reference
- Security Calling Patterns
- Native ASM is the default backend.
- On Windows, prefer
--gccfor verification. - Docs are written against verified current behavior.