Linking for armv6 failure

Getting into LiveCode for iOS? Ask your questions here.

Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller

Post Reply
grovecat
Livecode Opensource Backer
Livecode Opensource Backer
Posts: 99
Joined: Thu Aug 04, 2011 10:32 am

Linking for armv6 failure

Post by grovecat » Sun Jan 27, 2013 9:46 am

Suddenly I am unable to build any standalones and I get an error message:

There was an error while saving the standalone application.
linking for armv6 failed with arm-apple-darwin10-llvm-g++-4.2:
/private/var/folders/m2/rzzx1s7m8xj7k600r6brlj0h0000gq/T/TemporaryItems/tmp.629.oppikHxu:
No such file or directory.

I have tried restarting the Mac (10.8.2) but it makes no difference. An hour ago all was well and I have no idea what brought this on.

Does anyone have a clue what it all means and what I can do about it?

TIA
Don

grovecat
Livecode Opensource Backer
Livecode Opensource Backer
Posts: 99
Joined: Thu Aug 04, 2011 10:32 am

Re: Linking for armv6 failure

Post by grovecat » Sun Jan 27, 2013 9:52 am

Forgot to mention that I am using LC 6.5.3 and I also tried 6.5.2 with the same result.

grovecat
Livecode Opensource Backer
Livecode Opensource Backer
Posts: 99
Joined: Thu Aug 04, 2011 10:32 am

Re: Linking for armv6 failure

Post by grovecat » Sun Jan 27, 2013 9:59 am

Update:

I made a simple one-control stack and when saving that as a standalone I got a different message:

Could not open standalone engine file.

Is that more of a clue?

grovecat
Livecode Opensource Backer
Livecode Opensource Backer
Posts: 99
Joined: Thu Aug 04, 2011 10:32 am

Re: Linking for armv6 failure

Post by grovecat » Sun Jan 27, 2013 10:10 am

Further update

I re-installed LC 6.5.3 but no luck.

sturgis
Livecode Opensource Backer
Livecode Opensource Backer
Posts: 1685
Joined: Sat Feb 28, 2009 11:49 pm

Re: Linking for armv6 failure

Post by sturgis » Sun Jan 27, 2013 4:15 pm

You might try wiping out the preferences file for LC, but I can't remember off the top of my head exactly where that file is. You might do a forum search for that. I have 10.8.2 also, basically all updates done on my machine here, but I can't test on IOS. (no dev membership) all other aspects of lc work for me including android builds.

It might also be something on the xcode side of things. (the linking message kinda indicates that) Is your xcode updated all the way? If so and it doesn't work, I wonder if you can downgrade to the most recent previous version. If it is NOT updated all the way you might try updating to the most recent.


Just did a google search and found some info. Like this: http://blog.manbolo.com/2011/12/04/xcod ... est-friend
You most likely have a more recent version of xcode than 4.2, but it's worth a check.

EDIT: Er.. just looked again. You are using 4.2. :) Upgrade might help.

grovecat
Livecode Opensource Backer
Livecode Opensource Backer
Posts: 99
Joined: Thu Aug 04, 2011 10:32 am

Re: Linking for armv6 failure

Post by grovecat » Mon Jan 28, 2013 2:45 pm

Thanks sturgis

I have found the problem and it was rather weird. It was associated with the rreMicrophone external version and LC 5.5.3. However, what I was doing was purging memory and then opening another stack that had no externals and it gave the same error so I discounted the external as the cause. Then I belatedly discovered that if I quit LC and opened one of the other apps it built a standalone with no problem -- so the error caused by my app was in effect stored somewhere and persisted even through a memory purge, thus leading me well astray and wasting several hours of head scratching.

Anyway all is now well with LC 5.5.2 and the original external so I'll stick with those for now. The lesson is not to to trust the memory purge and always restart with a different stack.

Cheers
Don

sturgis
Livecode Opensource Backer
Livecode Opensource Backer
Posts: 1685
Joined: Sat Feb 28, 2009 11:49 pm

Re: Linking for armv6 failure

Post by sturgis » Mon Jan 28, 2013 4:54 pm

Hmm. Does the external contain a command to remove itself from memory? Not sure enough about externals to have a clue on that, but my gut feeling is that it would take up residence in its own unpurgable (by lc) memory location. I know revspeak has a command to unload itself, so if you are building the rremicrophone external yourself, perhaps you can adjust it so that you can de-initialize it on close stack.

Maybe monte will chime in on this since I don't know enough, but am curious now!

Post Reply