Skip to content

exename does not work on Mac OS X #3812

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
apinski-cavium opened this issue Dec 28, 2022 · 1 comment · Fixed by #5185
Closed

exename does not work on Mac OS X #3812

apinski-cavium opened this issue Dec 28, 2022 · 1 comment · Fixed by #5185
Assignees
@fruffy
Labels
core Topics concerning the core segments of the compiler (frontend, midend, parser)

Comments

@apinski-cavium
Copy link

When I was reading the code for exename, I see it does not have a fallback for searching the PATH env if the argv0 was not a path.
csh shell does not set _ env variable either.
There might be other shells which don't set _ env variable either either.
@apinski-cavium
Copy link
Author

Even worse is if you invoke csh from bash and then try to invoke p4test (or p4c) with a moved binary install. _ will put to /bin/csh so it more even be confused.

@mihaibudiu mihaibudiu added the bug label Jan 6, 2023
@fruffy fruffy added the core Topics concerning the core segments of the compiler (frontend, midend, parser) label Mar 2, 2023
@fruffy fruffy removed the bug label Mar 18, 2025
@fruffy fruffy self-assigned this Mar 19, 2025
@fruffy fruffy mentioned this issue Mar 19, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@fruffy fruffy

Labels
core Topics concerning the core segments of the compiler (frontend, midend, parser)
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Try to make exename portable. Refactor searchForIncludePath. p4lang/p4c
3 participants
@fruffy @apinski-cavium @mihaibudiu