05-15-2015 04:17 PM
Not sure how to set VIs to separate source code...
So I did the forced recompile. Labview now consistently fails compile when SSE2 Optimization is checked, and consistently succeeds the compile when it is unchecked again...tried it both ways six times. Even tried shutting down and restarting LV and then recompiling both ways again. Same thing. Seems to be directly related to SSE2 somehow...?
I'm on a brand new Dell Lattitude laptop running high-end hardware, on Windows 7 with all recent updates. Had this same issue a few months ago on a relatively high-end Dell desktop as well...so it doesn't seem to be computer specific...perhaps manufacturer specific. I have no way to try another manufacturers' computer since the company I work for only buys Dell...
05-15-2015 05:08 PM
05-15-2015 05:56 PM
Mike,
Thanks for your help. I'll have to continue troubleshooting as you suggested after I get a few of my other tasks (that got pushed out due to this bug) completed. I'll post back here if / when I find a solution.
-Ryan
03-24-2022 05:46 AM
I realize it has been over 14 years since the original post and almost 7 years since the most recent one, but as there is no "solution" posted I thought I would mention what I found.
I had this problem building my applications in a VirtualBox Centos 7 VM, so after researching the right way to do this I decided to try brute force and that worked for me. The problem had to do with file permissions, so I decided to start LabVIEW 2020 in administrative mode (sudo ./labview - see image below). The problem was solved!