Como eu faço cross-compile node.js para arquitetura ARM? O GCC não reporta o FP ABI compilado para

Question

Como eu faço cross-compile node.js para arquitetura ARM? O GCC não reporta o FP ABI compilado para

Navegue suas respostas

#1 resposta do (2 votos)
#2 resposta do (1 votos)

3

Ambiente

TARGET Computador de mesa único: FriendlyARM mini210s
TARGET Linux: 3.0.8 armv7l
Cross compiling na caixa vagrant Ubuntu Precise64

Cross-compiling com o GCC 4.5.1

arm-none-linux-gnueabi-gcc (ctng-1.8.1-FA) 4.5.1

`arm-none-linux-gnueabi-gcc --verbose`

Using built-in specs.
COLLECT_GCC=arm-none-linux-gnueabi-gcc
COLLECT_LTO_WRAPPER=/opt/FriendlyARM/toolschain/4.5.1/libexec/gcc/arm-none-linux-gnueabi/4.5.1/lto-wrapper
Target: arm-none-linux-gnueabi
Configured with: /work/toolchain/build/src/gcc-4.5.1/configure --build=i686-build_pc-linux-gnu --host=i686-build_pc-linux-gnu --target=arm-none-linux-gnueabi --prefix=/opt/FriendlyARM/toolschain/4.5.1 --with-sysroot=/opt/FriendlyARM/toolschain/4.5.1/arm-none-linux-gnueabi/sys-root --enable-languages=c,c++ --disable-multilib --with-cpu=arm1176jzf-s --with-tune=arm1176jzf-s --with-fpu=vfp --with-float=softfp --with-pkgversion=ctng-1.8.1-FA --with-bugurl=http://www.arm9.net/ --disable-sjlj-exceptions --enable-__cxa_atexit --disable-libmudflap --with-host-libstdcxx='-static-libgcc -Wl,-Bstatic,-lstdc++,-Bdynamic -lm' --with-gmp=/work/toolchain/build/arm-none-linux-gnueabi/build/static --with-mpfr=/work/toolchain/build/arm-none-linux-gnueabi/build/static --with-ppl=/work/toolchain/build/arm-none-linux-gnueabi/build/static --with-cloog=/work/toolchain/build/arm-none-linux-gnueabi/build/static --with-mpc=/work/toolchain/build/arm-none-linux-gnueabi/build/static --with-libelf=/work/toolchain/build/arm-none-linux-gnueabi/build/static --enable-threads=posix --with-local-prefix=/opt/FriendlyARM/toolschain/4.5.1/arm-none-linux-gnueabi/sys-root --disable-nls --enable-symvers=gnu --enable-c99 --enable-long-long
Thread model: posix
gcc version 4.5.1 (ctng-1.8.1-FA)

Estou recebendo um erro e a mensagem "Sua versão do GCC não relata a FP ABI compilada."

De agora em diante os passos que passei:

Obtenha o node.js

wget http://nodejs.org/dist/v0.10.35/node-v0.10.35.tar.gz 
tar xzvf node-v0.10.35.tar.gz 
cd node-v0.10.35/

Ambiente de configuração

export PATH=$PATH:/opt/FriendlyARM/toolschain/4.5.1/bin
export PKG_CONFIG_PATH=/usr/arm-linux-gnueabi/lib/pkgconfig 
export CC=/opt/FriendlyARM/toolschain/4.5.1/bin/arm-none-linux-gnueabi-gcc
export CXX=/opt/FriendlyARM/toolschain/4.5.1/bin/arm-none-linux-gnueabi-g++
export AR=/opt/FriendlyARM/toolschain/4.5.1/bin/arm-none-linux-gnueabi-ar
export RANLIB=/opt/FriendlyARM/toolschain/4.5.1/bin/arm-none-linux-gnueabi-ranlib
export LINK="${CXX}"
export CCFLAGS="-march=armv7-a -mtune=cortex-a8 -mfpu=vfp -mfloat-abi=hard -DUSE_EABI_HARDFLOAT"
export CXXFLAGS="-march=armv7-a -mtune=cortex-a8 -mfpu=vfp -mfloat-abi=hard -DUSE_EABI_HARDFLOAT"
export OPENSSL_armcap=7
export GYPFLAGS="-Darmeabi=hard -Dv8_use_arm_eabi_hardfloat=true -Dv8_can_use_vfp3_instructions=true -Dv8_can_use_vfp2_instructions=true -Darm7=1"
export VFP3=on
export VFP2=on
export PREFIX_DIR=/usr/arm-linux-gnueabi

Configurar

vagrant@vagrant:~/node-v0.10.35$ ./configure --without-snapshot --without-ssl --dest-cpu=arm --dest-os=linux --with-arm-float-abi=hard --prefix="${PREFIX_DIR}"

 { 'target_defaults': { 'cflags': [],
                       'default_configuration': 'Release',
                       'defines': [],
                       'include_dirs': [],
                       'libraries': []},
  'variables': { 'arm_fpu': 'vfpv2',
                 'arm_neon': 0,
                 'armv7': 0,
                 'clang': 0,
                 'gcc_version': 45,
                 'host_arch': 'arm',
                 'node_install_npm': 'true',
                 'node_prefix': '/usr/arm-linux-gnueabi',
                 'node_shared_cares': 'false',
                 'node_shared_http_parser': 'false',
                 'node_shared_libuv': 'false',
                 'node_shared_openssl': 'false',
                 'node_shared_v8': 'false',
                 'node_shared_zlib': 'false',
                 'node_tag': '',
                 'node_unsafe_optimizations': 0,
                 'node_use_dtrace': 'false',
                 'node_use_etw': 'false',
                 'node_use_openssl': 'false',
                 'node_use_perfctr': 'false',
                 'node_use_systemtap': 'false',
                 'openssl_no_asm': 0,
                 'python': '/usr/bin/python',
                 'target_arch': 'arm',
                 'v8_enable_gdbjit': 0,
                 'v8_no_strict_aliasing': 1,
                 'v8_use_arm_eabi_hardfloat': 'true',
                 'v8_use_snapshot': 'false',
                 'want_separate_host_toolset': 0}}
creating  ./config.gypi
creating  ./config.mk

O problema

Depois de executar make , recebo a seguinte mensagem:

Sua versão do GCC não relata o FP ABI compilado.

vagrant@vagrant:~/node-v0.10.35$ make -j 2
make -C out BUILDTYPE=Release V=1
make[1]: Entering directory '/home/vagrant/node-v0.10.35/out'
  /opt/FriendlyARM/toolschain/4.5.1/bin/arm-none-linux-gnueabi-g++ '-DENABLE_DEBUGGER_SUPPORT' '-DENABLE_EXTRA_CHECKS' '-DV8_TARGET_ARCH_ARM' '-DUSE_EABI_HARDFLOAT=1' '-DCAN_USE_VFP2_INSTRUCTIONS' -I../deps/v8/src  -Wall -Wextra -Wno-unused-parameter -pthread -fno-strict-aliasing -mfloat-abi=hard -O2 -fno-strict-aliasing -fno-tree-vrp -fno-omit-frame-pointer -fno-rtti -fno-exceptions -MMD -MF /home/vagrant/node-v0.10.35/out/Release/.deps//home/vagrant/node-v0.10.35/out/Release/obj.target/v8_base/deps/v8/src/platform-linux.o.d.raw -march=armv7-a -mtune=cortex-a8 -mfpu=vfp -mfloat-abi=hard -DUSE_EABI_HARDFLOAT -c -o /home/vagrant/node-v0.10.35/out/Release/obj.target/v8_base/deps/v8/src/platform-linux.o ../deps/v8/src/platform-linux.cc
  /opt/FriendlyARM/toolschain/4.5.1/bin/arm-none-linux-gnueabi-g++ '-DENABLE_DEBUGGER_SUPPORT' '-DENABLE_EXTRA_CHECKS' '-DV8_TARGET_ARCH_ARM' '-DUSE_EABI_HARDFLOAT=1' '-DCAN_USE_VFP2_INSTRUCTIONS' -I../deps/v8/src  -Wall -Wextra -Wno-unused-parameter -pthread -fno-strict-aliasing -mfloat-abi=hard -O2 -fno-strict-aliasing -fno-tree-vrp -fno-omit-frame-pointer -fno-rtti -fno-exceptions -MMD -MF /home/vagrant/node-v0.10.35/out/Release/.deps//home/vagrant/node-v0.10.35/out/Release/obj.target/v8_base/deps/v8/src/platform-posix.o.d.raw -march=armv7-a -mtune=cortex-a8 -mfpu=vfp -mfloat-abi=hard -DUSE_EABI_HARDFLOAT -c -o /home/vagrant/node-v0.10.35/out/Release/obj.target/v8_base/deps/v8/src/platform-posix.o ../deps/v8/src/platform-posix.cc
../deps/v8/src/platform-linux.cc:223:2: error: #error "Your version of GCC does not report the FP ABI compiled for." "Please report it on this issue" "http://code.google.com/p/v8/issues/detail?id=2140"
../deps/v8/src/platform-linux.cc: In static member function 'static bool v8::internal::OS::ArmUsingHardFloat()':
../deps/v8/src/platform-linux.cc:230:1: warning: no return statement in function returning non-void
make[1]: *** [/home/vagrant/node-v0.10.35/out/Release/obj.target/v8_base/deps/v8/src/platform-linux.o] Error 1
make[1]: *** Waiting for unfinished jobs....
../deps/v8/src/platform-posix.cc: In static member function 'static int v8::internal::OS::VSNPrintF(v8::internal::Vector<char>, const char*, va_list)':
../deps/v8/src/platform-posix.cc:338:5: note: the mangling of 'va_list' has changed in GCC 4.4
make[1]: Leaving directory '/home/vagrant/node-v0.10.35/out'
make: *** [node] Error 2

O problema parece estar relacionado a hard abi vs soft abi ... e não sei que diferença faz.

O que é hard abi ? e eu preciso disso para node.js cross-compillation?

UPDATE Cross-compiling com o GCC 4.6.3

arm-linux-gnueabihf-g++ (Ubuntu / Linaro 4.6.3-1ubuntu5) 4.6.3

Env

export CC=/usr/bin/arm-linux-gnueabihf-gcc
export CXX=/usr/bin/arm-linux-gnueabihf-g++
export AR=/usr/bin/arm-linux-gnueabihf-ar
export RANLIB=/usr/bin/arm-linux-gnueabihf-ranlib

Eu corro o mesmo comando configure e, em seguida, make e estou recebendo um erro diferente desta vez:

/usr/lib/gcc/arm-linux-gnueabihf/4.6/../../../../arm-linux-gnueabihf/bin/ld: warning: ld-linux.so.3, needed by /usr/lib/gcc/arm-linux-gnueabihf/4.6/libstdc++.so, not found (try using -rpath or -rpath-link)
/home/vagrant/node-v0.10.35/out/Release/obj.target/node/src/node.o: In function 'node::Init(int, char**)':
node.cc:(.text+0x2be0): undefined reference to 'node::SSL2_ENABLE'
node.cc:(.text+0x2c00): undefined reference to 'node::SSL3_ENABLE'
collect2: ld returned 1 exit status
make[1]: *** [/home/vagrant/node-v0.10.35/out/Release/node] Error 1
make[1]: Leaving directory '/home/vagrant/node-v0.10.35/out'
make: *** [node] Error 2

arm cross-compilation node.js

por zabumba 30.12.2014 / 16:42

2 respostas

1

Parece que você está dizendo que deseja a unidade de ponto flutuante de vetor ( -mfpu=vfp ), mas que o GCC deve gerar instruções de ponto flutuante difícil ( -mfloat-abi=hard -DUSE_EABI_HARDFLOAT ).

De opções do GCC ARM :

Using -mfloat-abi=hard with VFP coprocessors is not supported. Use -mfloat-abi=softfp with the appropriate -mfpu option to allow the compiler to generate code that makes use of the hardware floating-point capabilities for these CPUs.

Eu uso as seguintes opções com a TI AM3505 (Cortex A8 + FPU) e compila ok (GCC 4.8.2):

-march=armv7-a -mthumb-interwork -mfloat-abi=hard -mfpu=neon -mtune=cortex-a8

por 05.01.2015 / 23:15

Tags arm cross-compilation node.js

Qual é a diferença entre deixar nohup anexar a 'nohup.out' e redirecioná-lo explicitamente para um arquivo? Usuário local do CentOS não consegue visualizar diretórios / arquivos via login FTP

score 2 · Accepted Answer

Usando o GCC 4.5.1 - FAIL

arm-none-linux-gnueabi-gcc (ctng-1.8.1-FA) 4.5.1 não relata o FP ABI compilado para, conforme mencionado na mensagem de erro. Leia mais sobre o assunto

Eu tentei usar ./configure --with-arm-float-abi=softpf e soft como sugerido por Robert ou Thiago. Eu não segui esse caminho até o fim.

Ambiente

export PATH=$PATH:/opt/FriendlyARM/toolschain/4.5.1/bin
export PKG_CONFIG_PATH=/usr/arm-linux-gnueabi/lib/pkgconfig 
export CC=/opt/FriendlyARM/toolschain/4.5.1/bin/arm-none-linux-gnueabi-gcc
export CXX=/opt/FriendlyARM/toolschain/4.5.1/bin/arm-none-linux-gnueabi-g++
export AR=/opt/FriendlyARM/toolschain/4.5.1/bin/arm-none-linux-gnueabi-ar
export RANLIB=/opt/FriendlyARM/toolschain/4.5.1/bin/arm-none-linux-gnueabi-ranlib
export LINK="${CXX}"
export CCFLAGS="-march=armv7-a -mtune=cortex-a8 -mfpu=vfp -mfloat-abi=soft "
export CXXFLAGS="-march=armv7-a -mtune=cortex-a8 -mfpu=vfp -mfloat-abi=soft "
export OPENSSL_armcap=7
export GYPFLAGS="-Darmeabi=soft -Dv8_use_arm_eabi_hardfloat=false -Dv8_can_use_vfp3_instructions=true -Dv8_can_use_vfp2_instructions=true -Darm7=1"
export VFP3=on
export VFP2=on
export PREFIX_DIR=/usr

Configurar

  ./configure --without-snapshot --dest-cpu=arm --dest-os=linux --with-arm-float-abi=soft --prefix="${PREFIX_DIR}"

"Sua versão do GCC não relata o FP ABI compilado para" error

vagrant@vagrant:~/node-v0.10.35$ make
make -C out BUILDTYPE=Release V=1
make[1]: Entering directory '/home/vagrant/node-v0.10.35/out'
  /opt/FriendlyARM/toolschain/4.5.1/bin/arm-none-linux-gnueabi-g++ '-DENABLE_DEBUGGER_SUPPORT' '-DENABLE_EXTRA_CHECKS' '-DV8_TARGET_ARCH_ARM' '-DUSE_EABI_HARDFLOAT=0' -I../deps/v8/src  -Wall -Wextra -Wno-unused-parameter -pthread -fno-strict-aliasing -O2 -fno-strict-aliasing -fno-tree-vrp -fno-omit-frame-pointer -fno-rtti -fno-exceptions -MMD -MF /home/vagrant/node-v0.10.35/out/Release/.deps//home/vagrant/node-v0.10.35/out/Release/obj.target/v8_base/deps/v8/src/platform-linux.o.d.raw -march=armv7-a -mtune=cortex-a8 -mfpu=vfp -mfloat-abi=soft  -c -o /home/vagrant/node-v0.10.35/out/Release/obj.target/v8_base/deps/v8/src/platform-linux.o ../deps/v8/src/platform-linux.cc
../deps/v8/src/platform-linux.cc:223:2: error: #error "Your version of GCC does not report the FP ABI compiled for." "Please report it on this issue" "http://code.google.com/p/v8/issues/detail?id=2140"
../deps/v8/src/platform-linux.cc: In static member function 'static bool v8::internal::OS::ArmUsingHardFloat()':
../deps/v8/src/platform-linux.cc:230:1: warning: no return statement in function returning non-void
make[1]: *** [/home/vagrant/node-v0.10.35/out/Release/obj.target/v8_base/deps/v8/src/platform-linux.o] Error 1
make[1]: Leaving directory '/home/vagrant/node-v0.10.35/out'
make: *** [node] Error 2

Usando o GCC 4.6.3 - PASSA DE CROSS-COMPILAÇÃO

Removido o --without-ssl no meu comando configure e compilado bem (sem erros) com arm-linux-gnueabihf-g++ (Ubuntu / Linaro 4.6.3-1ubuntu5) 4.6.3

vagrant@vagrant:~/node-v0.10.35$ ./configure --without-snapshot --dest-cpu=arm --dest-os=linux --with-arm-float-abi=hard --prefix="${PREFIX_DIR}"

Ele compila e corre bem no alvo!

No entanto, npm mostra erros postados na pergunta aqui