| Summary: | pyrexc fails to run when path is too long | ||
|---|---|---|---|
| Product: | buildroot | Reporter: | kevin.alden2 |
| Component: | Other | Assignee: | unassigned |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | buildroot, kevin.alden2, steffen |
| Priority: | P5 | ||
| Version: | 2015.05 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Host: | Target: | ||
| Build: | |||
|
Description
kevin.alden2
2015-08-11 13:04:35 UTC
Isn't this a pyrexc bug rather than a Buildroot bug? (In reply to comment #1) > Isn't this a pyrexc bug rather than a Buildroot bug? I suppose you could look at it that way. I don't know enough about pyrexc to propose a solution, but Buildroot must be populating that invalid shebang. I guess I would look at it as a Buildroot bug for that reason. I would consider it a pyrexc bug as well if it happens to be completely reliant on the shebang to work. It seems like you could just explicitly pass pyrexc to python and avoid the shebang issue though. Fixed by http://git.buildroot.net/buildroot/commit/?id=fd43cadc6bf0c814d30ac0112ddf31ee5e72af5b. Thanks for the report! |