Bug 8281 - pyrexc fails to run when path is too long
Summary: pyrexc fails to run when path is too long
Status: RESOLVED FIXED
Alias: None
Product: buildroot
Classification: Unclassified
Component: Other (show other bugs)
Version: 2015.05
Hardware: PC Linux
: P5 normal
Target Milestone: ---
Assignee: unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-11 13:04 UTC by kevin.alden2
Modified: 2018-10-26 22:14 UTC (History)
3 users (show)

See Also:
Host:
Target:
Build:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description kevin.alden2 2015-08-11 13:04:35 UTC 
If your build environment starts with a path longer than 100 characters, pyrexc will fail to run due to a shebang longer than 128 characters
Comment 1 Thomas Petazzoni 2015-08-24 20:17:14 UTC 
Isn't this a pyrexc bug rather than a Buildroot bug?
Comment 2 kevin.alden2 2015-08-27 16:29:04 UTC 
(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.
Comment 3 Thomas Petazzoni 2015-10-14 14:55:15 UTC 
Fixed by http://git.buildroot.net/buildroot/commit/?id=fd43cadc6bf0c814d30ac0112ddf31ee5e72af5b. Thanks for the report!