Databases
StackOverflow2013
Postsdbo
POCompiling LuaJit 2 for Android on mac. Assembler errrors : lj_vm.s:5: Error: unknown pseudo-op: `.private_extern'
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCompiling LuaJit 2 for Android on mac. Assembler errrors : lj_vm.s:5: Error: unknown pseudo-op: `.private_extern'
    text
    copied!<p>Please advise about building android LuaJit on mac or tips on resolving <code>pseudo-op: '.private_extern'</code> assembler errors in general.</p> <p>I am on Mac and following instruction to complie LuaJit2 in doc/install or <a href="http://luajit.org/install.html#android" rel="nofollow">http://luajit.org/install.html#android</a> :</p> <p>The only change I made is to change <code>linux-x86</code> to <code>darwin-x86</code> to get <code>NDK</code> cross-compiler. I also added <code>TARGET_SYS=Linux</code> (I tried with and without) per installation notes: “Whenever the host OS and the target OS differ, you need to specify <code>TARGET_SYS</code> or you'll get assembler or linker errors…”</p> <p>So my build script looks like this:</p> <pre><code>NDK=$ANDROID_NDK NDKABI=8 NDKVER=$NDK/toolchains/arm-linux-androideabi-4.4.3 NDKP=$NDKVER/prebuilt/darwin-x86/bin/arm-linux-androideabi- NDKF="--sysroot $NDK/platforms/android-$NDKABI/arch-arm" make HOST_CC="gcc -m32" CROSS=$NDKP TARGET_SYS=Linux TARGET_FLAGS="$NDKF" </code></pre> <p>My <code>$ANDROID_NDK</code> points to <code>r8b NDK</code>. But I also tried <code>r8</code> and <code>r7</code>, and I tried <code>gcc 4.6</code> with <code>r8b</code>. In all cases I get similar errors. </p> <pre> ==== Building LuaJIT 2.0.0-beta9 ==== make -C src ASM lj_vm.o lj_vm.s: Assembler messages: lj_vm.s:5: Error: unknown pseudo-op: `.private_extern' lj_vm.s:8: Error: unknown pseudo-op: `.private_extern' lj_vm.s:25: Error: unknown pseudo-op: `.private_extern' … </pre>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload