You are not logged in.
From my memory on previous Unix systems, the environment variables for the compiler such as CC, CPATH, etc. were set at the system level.
While reading the fine wiki, it appears that a (the?) proper location to set them might be as a separate .sh file in /etc/profile.d/
I know they can be set most anywhere and work, be I would like to know where is recommended on Arch Linux.
Thanks,
Bob Collins
Sunnyvale CA USA
Offline
were set at the system level.
a separate .sh file in /etc/profile.d/
These are the same thing.
Offline
BobCollins wrote:were set at the system level.
BobCollins wrote:a separate .sh file in /etc/profile.d/
These are the same thing.
Allen, on my computer, I don't currently see (printenv) these environment variables being set. I listed the /etc/profile.d/ directory as a POSSIBLE place I could set them. There is no file in my /etc/profile.d/ directory which sets the compiler environment variables.
Offline
Then none are set. What's the question here?
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
QUESTION: Where should I set the compiler environment variables? It there a standard location? Is there a package I missed that should have done it for me?
Then none are set. What's the question here?
I guess I violated forum rule #1—ask the question first and clear. All caps?
Offline
I listed the /etc/profile.d/ directory as a POSSIBLE place I could set them. There is no file in my /etc/profile.d/ directory which sets the compiler environment variables.
So put one there...
Offline
You might want to clarify your exact intention, what do you want to set, and why and for what purpose. As mentioned globally setting variables happens at the location mentioned.
But if your actual question is where these flags come from when using makepkg, you will want to read https://wiki.archlinux.org/index.php/Ma … d_binaries
Offline
QUESTION: Where should I set the compiler environment variables?
But this was answered in the first response by Allan. Then you noted that there were no environment variables set. Certainly this is a true statement, but it suggests that your question wasn't completely answered or that you are still unclear about something. What remaining uncertainty do you have?
Create a .sh file in /etc/profile.d if you'd like to set those variables system-wide. You have not yet done so, so as you note, those environment variables do not yet exist. This is normal. If you want them set, set them.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline