PDF bundle for Mac fails to load

[dunbarx]

All of a sudden I get a warning after an otherwise successful build of a standalone, the this bundle (the pdf printing inclusion) has failed to install for Mac. And it is true. I cannot make a pdf from the command "open printing to pdf". Interestingly, the Windows version has no issue; it works fine.

I changed nothing. Just tried to make a standalone from a long standing splash stack/working stack that worked fine last Friday, without modification. Tried several times. Restarted computer.

Still in v 6.7.9, of course, but this question is not about that. Rough weekend for LC? Would reinstalling the program make sense? Anyone ever see such a thing?

thanks...

Craig

[LiveCode_Panos]

Hi Craig,

What is the exact warning you get when building a standalone? Can you attach a screenshot?

Best,
Panos
--

[dunbarx]

Panos.

Thanks for looking. Attached.

Craig

[LiveCode_Panos]

Hmm, do you get that only with this external (revpdfprinter?), or with *any* external? Try for example to include revZip and revDB.

I am wondering if it is a permissions issue, like bug http://quality.livecode.com/show_bug.cgi?id=17992.

Best,
Panos
--

[dunbarx]

Panos.

The two new externals (revZip and revDB) also failed to load.

But this simply reared its head one day, at least for PDF. Cosmic ray? Fortunately, the users I am making the standalone for all use Windows, and only I use the (Mac) IDE stack for testing, which prints just fine. But it is worrisome. Again, is there any point in reloading LC?

Craig

[LiveCode_Panos]

Hi Craig,

It is indeed strange that it started happening all of a sudden.

Maybe you could try changing the permissions. Open a terminal and type:

sudo chmod -R 755 /Applications/LiveCode\ Commercial\ 6.7.9.app/Contents/Tools/Runtime

(or sudo chmod -R 755 /path/to/LC6.7.9.app/Contents/Tools/Runtime if you have not put it in the Applications folder)

and then try again to create a standalone.

Keep us posted

Best,
Panos
--

[dunbarx]

Panos.

That did it.

If it is not to much to ask, what exactly did the Terminal command do? What permissions did it change?

Thanks ever so much.

Craig

[LiveCode_Panos]

Hi Craig,

Before this command, probably the directory were the externals are stored (i.e. the /path/to/LC6.7.9.app/Contents/Tools/Runtime) had become read-only.

This command gives everyone read and execute permissions, and the file owner is allowed to write to the files as well.

Best,
Panos
--