Ask HN: Help with LLVM
I'm developing a new language, and everything is pretty nice so far. I need to know if there's a way to prevent LLVM from linking in CRT symbols entirely. The goal is to make a new runtime. I have a stub library written in my language, when I go to compile the library in .lib form, I keep running into a wall where LLVM forcefully brings in _fltused , causing my definition to get flagged with an error saying _fltused already exists. There is nothing in the .ll IR file other than the _fltused definition, the one that I want to have end up in the final .lib. I have Googled and asked AI for days now what compiler/linker flags I can use to get LLVM to bypass the CRT entirely so I can develop my own runtime, and Clang, MinGW, and LLVM are all aggressively linking in the CRT no matter what flags I add. I'm pulling my hair out over here. I can't convert my .ll file directly to .as because the LLVM compiler is getting in the way, otherwise I'd have my library by now. 3 comments on Hacker News.
I'm developing a new language, and everything is pretty nice so far. I need to know if there's a way to prevent LLVM from linking in CRT symbols entirely. The goal is to make a new runtime. I have a stub library written in my language, when I go to compile the library in .lib form, I keep running into a wall where LLVM forcefully brings in _fltused , causing my definition to get flagged with an error saying _fltused already exists. There is nothing in the .ll IR file other than the _fltused definition, the one that I want to have end up in the final .lib. I have Googled and asked AI for days now what compiler/linker flags I can use to get LLVM to bypass the CRT entirely so I can develop my own runtime, and Clang, MinGW, and LLVM are all aggressively linking in the CRT no matter what flags I add. I'm pulling my hair out over here. I can't convert my .ll file directly to .as because the LLVM compiler is getting in the way, otherwise I'd have my library by now.
I'm developing a new language, and everything is pretty nice so far. I need to know if there's a way to prevent LLVM from linking in CRT symbols entirely. The goal is to make a new runtime. I have a stub library written in my language, when I go to compile the library in .lib form, I keep running into a wall where LLVM forcefully brings in _fltused , causing my definition to get flagged with an error saying _fltused already exists. There is nothing in the .ll IR file other than the _fltused definition, the one that I want to have end up in the final .lib. I have Googled and asked AI for days now what compiler/linker flags I can use to get LLVM to bypass the CRT entirely so I can develop my own runtime, and Clang, MinGW, and LLVM are all aggressively linking in the CRT no matter what flags I add. I'm pulling my hair out over here. I can't convert my .ll file directly to .as because the LLVM compiler is getting in the way, otherwise I'd have my library by now. 3 comments on Hacker News.
I'm developing a new language, and everything is pretty nice so far. I need to know if there's a way to prevent LLVM from linking in CRT symbols entirely. The goal is to make a new runtime. I have a stub library written in my language, when I go to compile the library in .lib form, I keep running into a wall where LLVM forcefully brings in _fltused , causing my definition to get flagged with an error saying _fltused already exists. There is nothing in the .ll IR file other than the _fltused definition, the one that I want to have end up in the final .lib. I have Googled and asked AI for days now what compiler/linker flags I can use to get LLVM to bypass the CRT entirely so I can develop my own runtime, and Clang, MinGW, and LLVM are all aggressively linking in the CRT no matter what flags I add. I'm pulling my hair out over here. I can't convert my .ll file directly to .as because the LLVM compiler is getting in the way, otherwise I'd have my library by now.
Hacker News story: Ask HN: Help with LLVM
![Hacker News story: Ask HN: Help with LLVM]()
Reviewed by Tha Kur
on
January 05, 2026
Rating:
No comments: