Gary Johnson Posted July 20, 2023 Report Share Posted July 20, 2023 Yet another MacOS file problem. New M2, Ventura 13.4.1, LV community 2023 Q1 64 bit, VIPM Free 2020. Attempts to install any pkg fails with error 7 (see below). Both LV and VIPM have full disk access. Used the finder Info on each target LV folder to set Everyone to RW. That mostly helped, but in some cases I would also have to manually create the sub-folder, such as OpenG. That finally worked. Of course I have to do this for every required directory...... So I tried a Unix command that I found related to this problem: sudo chmod -R u=rwx,g=rwx,o=rwx /Applications/National\ Instruments/LabVIEW\ 2023\ 64-bit/LabVIEWCommunity.app That didn't help, but seems like it should. It failed to set Everyone to rwx, which seems to be required. I'm not much of a Unix hack so maybe someone can enlighten me. Is there anything else I am missing here? Main Package Name: OpenG Boolean Library v4.0.0.7 Package Name with Error: OpenG Boolean Library v4.0.0.7 Error Message: VIPM could not install the package oglib_boolean-4.0.0.7 . Error Code: 7 Error Source: Write to Text File in Command-Line Zip.lvlib:ABDDB5E9F4D44AE0E70A4E4F8D4F491A->90BBE5FF7A35F3CE3E236F5A778C7C48->AD4791BDA0231EB30EBF129C1A98AB7B->OGPM Class.lvlib:1D42A1CCBC79EB157F4B29421C6C7648->OGPM Class.lvlib:68DD1F408D6154AB6D8715845077EEA9->FB296AD1654D68D63B7041E1F06FA55C->VIPM Main Window.vi<APPEND> /Applications/National Instruments/LabVIEW 2023 64-bit/user.lib/_OpenG.lib/boolean/boolean.llb/Boolean Trigger__ogtk.vi =============== -Gary Johnson 1 Quote Link to comment Share on other sites More sharing options...
Jim Kring Posted July 20, 2023 Report Share Posted July 20, 2023 Hi Gary! 🙇♂️ It may take a few tries, but we should be able to get this all sorted soon. Question, if you look in this folder, what do you see? /Applications/National Instruments/LabVIEW 2023 64-bit/user.lib/_OpenG.lib/boolean/ Does that folder exist? Is there an LLB named `boolean.llb` in there? Or, is there a folder named "boolean.llb"? Anything in it? Thanks for letting us know and for your patience with this, as it takes a bit of work to support Mac (and Arm) but we're trying Quote Link to comment Share on other sites More sharing options...
Gary Johnson Posted July 20, 2023 Author Report Share Posted July 20, 2023 Hi Jim, I'm retired but still at it 🙂 The file is there now, and the pkg install works, after I made user.lib RW for Everyone, manually. Also had to do that for menus/Categories. -Gary 1 Quote Link to comment Share on other sites More sharing options...
Jim Kring Posted July 20, 2023 Report Share Posted July 20, 2023 2 minutes ago, Gary Johnson said: Hi Jim, I'm retired but still at it 🙂 The file is there now, and the pkg install works, after I made user.lib RW for Everyone, manually. Also had to do that for menus/Categories. -Gary Oh, good! You'll probably want to do that for various other sub-folders of LabVIEW, too (vi.lib, resource, project, help, etc.) Quote Link to comment Share on other sites More sharing options...
Gary Johnson Posted July 20, 2023 Author Report Share Posted July 20, 2023 At least we have a (manual) solution. Not sure why the recursive chmod didn't do the job. Quote Link to comment Share on other sites More sharing options...
Jim Kring Posted July 21, 2023 Report Share Posted July 21, 2023 In your initial post, I just now noticed that the `LabVIEWCommunity.app` bundle was the target/argument of the `chmod` command. I would have probably targeted the whole LabVIEW folder: sudo chmod -R ugo+rw /Applications/National\ Instruments/LabVIEW\ 2023\ 64-bit/ Quote Link to comment Share on other sites More sharing options...
Gary Johnson Posted July 21, 2023 Author Report Share Posted July 21, 2023 For whatever reason, that doesn't seem to make a difference. Folders that I haven't manually changed to Everyone = RW are still read-only. Quote Link to comment Share on other sites More sharing options...
Jim Kring Posted July 21, 2023 Report Share Posted July 21, 2023 Security feature 🤷♂️ Quote Link to comment Share on other sites More sharing options...
ClinTrialist Posted December 27, 2023 Report Share Posted December 27, 2023 Similar problem: M1, Ventura 13.4, LV Pro 2023 & VIPM Free 2020, with LV and VIPM having full disk access. Followed https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000001DoXACA0&%3Bl=en-US&l=en-US which solved an Error 7 and allowed install of JDP Science Common Utilities. Now showing an Error 8, VIPM would only install JDP Science's SQLite Library post--as Gary points out--manually changing Everyone to RW in the folder to which to file will not write. Fortunately, the error 8 points to the destination folder (in this case, LabVIEW 2023 64-bit > menus > Categories > Computer). A Kludge, but it worked. As a plug, please keep VIPM updating for Mac OS versions of LV. Thank you. 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.