linux交叉编译的库在链接时提示uses VFP register arguments 20C

arm-none-linux-gnueabi-g++ -Wl,-O1 -Wl,-rpath,/opt/Qt-5.3.2/armv7-a/lib -o qtmeeting main.o mainwindow.o moc_mainwindow.o -L/mnt/hgfs/code/project/meeting/qtmeeting/lib/ -lwebrtc -L/opt/Qt-5.3.2/armv7-a/lib -lQt5Widgets -lQt5Gui -lQt5Core -lpthread
/usr/local/arm-2014.05/bin/../lib/gcc/arm-none-linux-gnueabi/4.8.3/../../../../arm-none-linux-gnueabi/bin/ld: error: /mnt/hgfs/code/project/meeting/qtmeeting/lib//libwebrtc.a(new.o) uses VFP register arguments, qtmeeting does not
/usr/local/arm-2014.05/bin/../lib/gcc/arm-none-linux-gnueabi/4.8.3/../../../../arm-none-linux-gnueabi/bin/ld: failed to merge target specific data of file /mnt/hgfs/code/project/meeting/qtmeeting/lib//libwebrtc.a(new.o)
/usr/local/arm-2014.05/bin/../lib/gcc/arm-none-linux-gnueabi/4.8.3/../../../../arm-none-linux-gnueabi/bin/ld: error: /mnt/hgfs/code/project/meeting/qtmeeting/lib//libwebrtc.a(cxa_exception.o) uses VFP register arguments, qtmeeting does not
/usr/local/arm-2014.05/bin/../lib/gcc/arm-none-linux-gnueabi/4.8.3/../../../../arm-none-linux-gnueabi/bin/ld: failed to merge target specific data of file /mnt/hgfs/code/project/meeting/qtmeeting/lib//libwebrtc.a(cxa_exception.o)
/usr/local/arm-2014.05/bin/../lib/gcc/arm-none-linux-gnueabi/4.8.3/../../../../arm-none-linux-gnueabi/bin/ld: error: /mnt/hgfs/code/project/meeting/qtmeeting/lib//libwebrtc.a(cxa_exception_storage.o) uses VFP register arguments, qtmeeting does not
/usr/local/arm-2014.05/bin/../lib/gcc/arm-none-linux-gnueabi/4.8.3/../../../../arm-none-linux-gnueabi/bin/ld: failed to merge target specific data of file /mnt/hgfs/code/project/meeting/qtmeeting/lib//libwebrtc.a(cxa_exception_storage.o)

3个回答

1.更换编译器版本,2.源文件把-mfloat-abi=hard参数修改成-mfloat-abi=softfp重新编译库

1.右键单击工程->properties->C/C++build->Setting->ARM v7 gcc compiler->Miscellaneous 把-mfloat-abi的值改成softfp;

2........................................................................................->ARM v7 gcc linker->Miscellaneous 把-mfloat-abi的值改成softfp;

3.在工程bsp包里同样把-mfloat-abi的值改成softfp。

huangcd0144
huangcd0144 linux平台而且Makefile设置-mfloat-abi=softfp或hard一样报错
大约 2 年之前 回复

总算遇到能回答的问题了
假设测试程序为 test.c。
硬浮点交叉编译:
arm-linux-gcc -march=armv7-a -mfpu=neon -mfloat-abi=hard -o test test.c
求20分

Csdn user default icon
上传中...
上传图片
插入图片
抄袭、复制答案,以达到刷声望分或其他目的的行为,在CSDN问答是严格禁止的,一经发现立刻封号。是时候展现真正的技术了!
其他相关推荐
arm-linux交叉编译的问题

_终端输入 arm-linux-gcc imgprocess.cpp -o imgprocess `pkg-config --cflags --libs opencv` -lrt -lpthread -lm -ldl 错误: /usr/local/lib/libopencv__calib3d.so: could not read symbols: File in wrong format 这个应该是pc opencv的库,我的arm opencv的库的目录在下面的路径中 /opt/FriendlyARM/toolschain/4.5.1/lib中 我在bash.bashrc中设置过了路径 输入echo $LD_LIBRARY_PATH 结果是/opt/FriendlyARM/toolschain/4.5.1/lib 但是运行之后还是那个问题怎么解决

关于x264交叉编译(linux to windows)的库在vs2005中链接失败的问题

环境: centos mingw gcc版本: [root@localhost x264]# x86_64-w64-mingw32-gcc -v Using built-in specs. COLLECT_GCC=x86_64-w64-mingw32-gcc COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-w64-mingw32/4.9.2/lto-wrapper Target: x86_64-w64-mingw32 Configured with: ../configure --prefix=/usr --bindir=/usr/bin --includedir=/usr/include --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --build=x86_64-redhat-linux-gnu --host=x86_64-redhat-linux-gnu --with-gnu-as --with-gnu-ld --verbose --without-newlib --disable-multilib --disable-plugin --with-system-zlib --disable-nls --without-included-gettext --disable-win32-registry --enable-languages=c,c++,objc,obj-c++,fortran --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-threads=posix --enable-libgomp --target=x86_64-w64-mingw32 --with-sysroot=/usr/x86_64-w64-mingw32/sys-root --with-gxx-include-dir=/usr/x86_64-w64-mingw32/sys-root/mingw/include/c++ Thread model: posix gcc version 4.9.2 20141030 (Fedora MinGW 4.9.2-1.el6) (GCC) 配置: ./configure \ --prefix=../windows/x86_64 \ --enable-static \ --enable-pic \ --host=x86_64-w64-mingw32 \ --cross-prefix=x86_64-w64-mingw32- 结果: 1、生成的x264.exe能正常在windows中运行; 2、生成的libx264.a在vs2005的工程中不能被正常链接!!! 测试程序: #include "stdafx.h" #include "stdint.h" #include "x264.h" int _tmain(int argc, _TCHAR* argv[]) { x264_param_t param; x264_encoder_open(&param); return 0; } 1>Linking... 1>VideoEncoder.obj : error LNK2019: unresolved external symbol _x264_encoder_open_148 referenced in function _wmain 1>F:\personal\sourcecode\VideoEncoder\Debug\VideoEncoder.exe : fatal error LNK1120: 1 unresolved externals 分析: dumpbin /ALL libx264.a > 1.txt String Table Size = 0x539 bytes COFF SYMBOL TABLE 000 00000000 DEBUG notype Filename | .file encoder.c 002 00000000 SECT1 notype () Static | x264_slice_header_init tag index 00000000 size 00000000 lines 00000000 next function 00000000 004 000002D0 SECT1 notype () Static | mbcmp_init 005 000007D0 SECT1 notype () Static | sprintf 006 00000800 SECT1 notype () Static | snprintf 007 00000820 SECT1 notype () Static | x264_fdec_filter_row 008 00000F00 SECT1 notype () Static | x264_set_aspect_ratio.isra.3 009 00001020 SECT1 notype () Static | x264_encoder_thread_init 00A 00001050 SECT1 notype () Static | x264_nal_end 00B 00001190 SECT1 notype () Static | x264_encoder_encapsulate_nals.constprop.13 00C 00001360 SECT1 notype () Static | x264_encoder_frame_end.part.7 00D 00002870 SECT1 notype () Static | x264_slice_write 00E 00001400 SECT7 notype Static | x264_ue_size_tab 00F 000013EC SECT7 notype Static | x264_mb_chroma_pred_mode_fix 010 00006470 SECT1 notype () Static | x264_slices_write 011 000066B0 SECT1 notype () External | x264_encoder_open_148 012 00000000 SECTB notype Static | .rdata$.refptr.x264_levels 发现libx264.a中是x264_encoder_open_148,而vs2005链接的时候寻找的是_x264_encoder_open_148,因此产生了链接问题。 经查资料,发现是因为msvc在链接c函数时都会加"_",而在linux中使用mingw编译的库却没有加"_", 在configure时增加--extra-cflags="-fleading-underscore": No working C compiler found. Makefile:3: config.mak: 没有那个文件或目录 cat: config.h: 没有那个文件或目录 有谁知道解决办法?不胜感激!

关于Qt交叉编译的问题

我的qt是qt5的版本,已经设置好了qtEmbedded4.8.1的交叉编译环境,下面是一个别人已经能在PC上面运行的project但是我放到自己的交叉编译就出现下面的错误,貌似是uic的图片什么的出了问题,但是我新手不知道怎么解决啊,我一共编译了两次,第一次由提示交叉编译的uic3好不到,只有uic于是我在指定的QtEmbedded-4.8.1-arm/bin下面给uic建立了一个软连接uic3,结果错误变少了,但是还是不能通过,求大神解决啊。 00:35:17: Running steps for project vanet... 00:35:17: Configuration unchanged, skipping qmake step. 00:35:17: Starting: "/usr/bin/make" /usr/local/Trolltech/QtEmbedded-4.8.1-arm/bin/uic3 -embed vanet ../vanet/images/current_position.png ../vanet/images/exit.png ../vanet/images/navigation.png ../vanet/images/normal_size.png ../vanet/images/position.png ../vanet/images/search.png ../vanet/images/stopnav.png ../vanet/images/zoom_in.png ../vanet/images/zoom_out.png ../vanet/images/zoomin.png ../vanet/images/zoomout.png -o qmake_image_collection.cpp Qt User Interface Compiler version 4.8.1 Usage: /usr/local/Trolltech/QtEmbedded-4.8.1-arm/bin/uic3 [options] -h, -help display this help and exit -v, -version display version -d, -dependencies display the dependencies -o place the output into -tr use func() for i18n -p, -no-protection disable header protection -n, -no-implicit-includes disable generation of #include-directives for forms generated by uic3 -g change generator make: *** [qmake_image_collection.cpp] Error 1 00:35:17: The process "/usr/bin/make" exited with code 2. Error while building/deploying project vanet (kit: ARM) When executing step 'Make' 00:35:17: Elapsed time: 00:00.

交叉编译到ARMv7失败

<div class="post-text" itemprop="text"> <p>I try to compile a go program on my Linux desktop (Linux desktop 4.10.0-28-generic #32-Ubuntu SMP Fri Jun 30 05:32:18 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux), go version <code>go version go1.8.3 linux/amd64</code> to arm:</p> <pre><code>$ GOPATH=/home/xrfang/git/hermes/ GOARM=7 GOARCH=arm go build . </code></pre> <p>the executable is generated, but seems NOT ARMv7:</p> <pre><code>$ file hermes hermes: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), statically linked, not stripped </code></pre> <p>It shows EABI5. How can I cross-compile to ARMv7? Is there anything missing on my Linux Desktop so that the cross-compile fallback to a lower ARM version?</p> <p>Thanks.</p> </div>

Android调用非NDK编译的静态库的问题

Android调用的静态库必须通过NDK编译吗?假如我用MinGW GCC编译了一个很简单的静态库,就一个add函数,有没有办法用NDK将其转化为Android的静态库?通过NDK编译出静态库文件再封装我已经会了,只需要用PREBUILT_STATIC_LIBRARY指令就行,不过NDK好像无法识别GCC编译的静态库。额,本人C/C++ 0基础,很多概念都没不太懂。

交叉编译应用程序无法运行 arm-oe-linux-gnueabi-gcc: not found

Ubuntu交叉编译的应用程序在Qualcomm 9615 A5核的Linux系统下面无法运行, 出错信息如下 /usr/bin/qmi_ping_clnt_test_0000: cd: line 1: can't cd to /home/qualcomm/nelson/ apps_proc/oe-core/build/tmp-eglibc/work/armv7a-vfp-neon-oe-linux-gnueabi/qmi-fra mework-git-r3/qmi-framework/qcci/test /usr/bin/qmi_ping_clnt_test_0000: eval: line 1: arm-oe-linux-gnueabi-gcc: not fo undn/usr/bin #

交叉编译程序无法运行 arm-oe-linux-gnueabi-gcc: not found

Ubuntu交叉编译的应用程序在Qualcomm 9615 A5核的Linux系统下面无法运行, 出错信息如下 dinapp /usr/bin/dinapp: cd: line 1: can't cd to /home/nelson/qualcomm/Margaery/apps_pro c/oe-core/build/tmp-eglibc/work/armv7a-vfp-neon-oe-linux-gnueabi/dinstar-git-r1/ dinstar /usr/bin/dinapp: eval: line 1: arm-oe-linux-gnueabi-gcc: not foundn/usr/bin #

Android Service类中调用NDK编译的库的问题

现碰到的问题如下: 在Java层写了一个类代码如下: ``` public class MeiaPush {         public native int meia_push_init ();         public native int meia_push_set_client_info (String cid, String pwd, String type, String token);         public native int meia_push_get_alarmlist (Object param, int count);         public native int meia_push_exit ();                   public int MeiaPushInit ()         {             Log.e ("Yan", "~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~");             meia_push_init ();             return meia_push_set_client_info ("00000000001", "123456", "android", "yan_yan");         } } ``` JNI层也实现了。 在其它类中调用MeiaPushInit 这个函数没有问题, 但是在Service类中调用就会出现“java.lang.unsatisfiedlinkerror native method not found” 请问 为什么会出现这个问题, 如何解决。 Service类中和其它类调用JNI函数有什么区别么? 谢谢! 这是帖子地址:[Android Service类中调用NDK编译的库的问题](http://bbs.csdn.net/topics/391019780 "")

Linux应用程序编译报错

Qualcomm 9x15平台A5应用程序编译,出错信息如下: | /home/nelson/qualcomm/Cersei/apps_proc/oe-core/build/tmp-eglibc/sysroots/x86_64-linux/usr/libexec/armv7a-vfp-neon-oe-linux-gnueabi/gcc/arm-oe-linux-gnueabi/4.6.3/ld: error: cannot open /lib/libpthread.so.0: No such file or directory | /home/nelson/qualcomm/Cersei/apps_proc/oe-core/build/tmp-eglibc/sysroots/x86_64-linux/usr/libexec/armv7a-vfp-neon-oe-linux-gnueabi/gcc/arm-oe-linux-gnueabi/4.6.3/ld: error: cannot open /usr/lib/libpthread_nonshared.a: No such file or directory | /home/nelson/qualcomm/Cersei/apps_proc/oe-core/build/tmp-eglibc/sysroots/x86_64-linux/usr/libexec/armv7a-vfp-neon-oe-linux-gnueabi/gcc/arm-oe-linux-gnueabi/4.6.3/ld: error: cannot open /lib/libpthread.so.0: No such file or directory | /home/nelson/qualcomm/Cersei/apps_proc/oe-core/build/tmp-eglibc/sysroots/x86_64-linux/usr/libexec/armv7a-vfp-neon-oe-linux-gnueabi/gcc/arm-oe-linux-gnueabi/4.6.3/ld: error: cannot open /usr/lib/libpthread_nonshared.a: No such file or directory | /home/nelson/qualcomm/Cersei/apps_proc/oe-core/build/tmp-eglibc/sysroots/x86_64-linux/usr/libexec/armv7a-vfp-neon-oe-linux-gnueabi/gcc/arm-oe-linux-gnueabi/4.6.3/ld: error: cannot open /lib/libc.so.6: No such file or directory | /home/nelson/qualcomm/Cersei/apps_proc/oe-core/build/tmp-eglibc/sysroots/x86_64-linux/usr/libexec/armv7a-vfp-neon-oe-linux-gnueabi/gcc/arm-oe-linux-gnueabi/4.6.3/ld: error: cannot open /usr/lib/libc_nonshared.a: No such file or directory | /home/nelson/qualcomm/Cersei/apps_proc/oe-core/build/tmp-eglibc/sysroots/x86_64-linux/usr/libexec/armv7a-vfp-neon-oe-linux-gnueabi/gcc/arm-oe-linux-gnueabi/4.6.3/ld: error: cannot open /lib/ld-linux.so.3: No such file or directory | /home/nelson/qualcomm/Cersei/apps_proc/oe-core/build/tmp-eglibc/sysroots/9615-cdp/usr/lib/crt1.o(.text+0x28): error: undefined reference to '__libc_start_main'

ndk调用第三方静态链接库

android ndk调用第三方静态链接库(.a文件)在android里面我要调用客户给的一个.a库(另有一个.h的头文件),我用ndk-build命令把它编译成.so的过程中一直出现问题。cmd提示如下,请问怎么解决,详细一点,各位大神,拜托了! /i_cheng/android-ndk-r7b-windows/android-ndk-r7b/toolchains/arm-linux-androide bi-4.4.3/prebuilt/windows/bin/../lib/gcc/arm-linux-androideabi/4.4.3/../../../. /arm-linux-androideabi/bin/ld.exe: ERROR: ./obj/local/armeabi/libpw.a(make_pw.o uses VFP register arguments, obj/local/armeabi/libshare.so does not :/i_cheng/android-ndk-r7b-windows/android-ndk-r7b/toolchains/arm-linux-androide bi-4.4.3/prebuilt/windows/bin/../lib/gcc/arm-linux-androideabi/4.4.3/../../../. /arm-linux-androideabi/bin/ld.exe: failed to merge target specific data of file ./obj/local/armeabi/libpw.a(make_pw.o) ollect2: ld returned 1 exit status ake: *** [obj/local/armeabi/libshare.so] Error 1

Linux下错误操作了usr/bin/ld 现在连个g++都不能编译了 怎么办

我在终端用cp了一个.so进入usr/bin/ld 结果现在连hello world都不能编译。这个怎么办?

在Linux下编译Unity的mono一直卡在这里

![图片说明](https://img-ask.csdn.net/upload/201707/25/1500967374_925546.png) 看日志有两个地方比较可疑,一个是这里 configure:3745: checking whether to enable maintainer-specific portions of Makefiles configure:3754: result: no 说没有开启maintainer-specific portions,但我不知道怎么开启,不知道是不是原因 另一处是arm-linux-androideabi-gcc: error: unrecognized command line option '-V' 这个好像和下面的 collect2: error: ld returned 1 exit status configure:4569: $? = 1 configure:4607: result: no configure: failed program was: | /* confdefs.h */ | #define PACKAGE_NAME "" | #define PACKAGE_TARNAME "" | #define PACKAGE_VERSION "" | #define PACKAGE_STRING "" | #define PACKAGE_BUGREPORT "" | #define PACKAGE_URL "" | #define PACKAGE "mono" | #define VERSION "2.6.5" | /* end confdefs.h. */ | | int | main () | { | | ; | return 0; | } 这个有关configure:4607: result: no这个意思好像是configure的4607行返回了一个no,文件夹内的确有一个configure文件,之后打开configure,4607行是这样的 4606 if test -z "$ac_file"; then : 4607 { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5 4608 $as_echo "no" >&6; } 4609 $as_echo "$as_me: failed program was:" >&5 4610 sed 's/^/| /' conftest.$ac_ext >&5 4611 4612 { { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5 4613 $as_echo "$as_me: error: in \`$ac_pwd':" >&2;} 4614 as_fn_error 77 "C compiler cannot create executables 4615 See \`config.log' for more details" "$LINENO" 5; } 4616 else 4617 { $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5 4618 $as_echo "yes" >&6; } 4619 fi 这种语言没学过,看不懂什么意思,求大神指点,卡这很久了 下面是日志 This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. It was created by configure, which was generated by GNU Autoconf 2.69. Invocation command line was $ ./configure --prefix=/home/jimmy/mono-unity-5.6/builds/android --cache-file=android_cross.cache --host=arm-eabi-linux --disable-mcs-build --disable-parallel-mark --disable-shared-handles --with-sigaltstack=no --with-tls=pthread --with-glib=embedded --enable-nls=no mono_cv_uscore=yes PATH=/home/jimmy/android-ndk_auto-r10e/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin CC=/home/jimmy/android-ndk_auto-r10e/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86/bin/arm-linux-androideabi-gcc --sysroot=/home/jimmy/android-ndk_auto-r10e/platforms/android-9/arch-arm CXX=/home/jimmy/android-ndk_auto-r10e/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86/bin/arm-linux-androideabi-g++ --sysroot=/home/jimmy/android-ndk_auto-r10e/platforms/android-9/arch-arm CPP=/home/jimmy/android-ndk_auto-r10e/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86/bin/arm-linux-androideabi-cpp CXXCPP=/home/jimmy/android-ndk_auto-r10e/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86/bin/arm-linux-androideabi-cpp CFLAGS=-DANDROID -DPLATFORM_ANDROID -DLINUX -D__linux__ -DHAVE_USR_INCLUDE_MALLOC_H -DPAGE_SIZE=0x1000 -D_POSIX_PATH_MAX=256 -DS_IWRITE=S_IWUSR -DHAVE_PTHREAD_MUTEX_TIMEDLOCK -fpic -g -funwind-tables -ffunction-sections -fdata-sections -DARM_FPU_NONE=1 -march=armv5te -mtune=xscale -msoft-float CPPFLAGS=-DANDROID -DPLATFORM_ANDROID -DLINUX -D__linux__ -DHAVE_USR_INCLUDE_MALLOC_H -DPAGE_SIZE=0x1000 -D_POSIX_PATH_MAX=256 -DS_IWRITE=S_IWUSR -DHAVE_PTHREAD_MUTEX_TIMEDLOCK -fpic -g -funwind-tables -ffunction-sections -fdata-sections -DARM_FPU_NONE=1 -march=armv5te -mtune=xscale -msoft-float CXXFLAGS=-DANDROID -DPLATFORM_ANDROID -DLINUX -D__linux__ -DHAVE_USR_INCLUDE_MALLOC_H -DPAGE_SIZE=0x1000 -D_POSIX_PATH_MAX=256 -DS_IWRITE=S_IWUSR -DHAVE_PTHREAD_MUTEX_TIMEDLOCK -fpic -g -funwind-tables -ffunction-sections -fdata-sections -DARM_FPU_NONE=1 -march=armv5te -mtune=xscale -msoft-float LDFLAGS=-Wl,--wrap,sigaction -L/home/jimmy/mono-unity-5.6/../../android_krait_signal_handler/build/obj/local/armeabi -lkrait-signal-handler -Wl,--no-undefined -Wl,--gc-sections -Wl,-rpath-link=/home/jimmy/android-ndk_auto-r10e/platforms/android-9/arch-arm/usr/lib -ldl -lm -llog -lc LD=/home/jimmy/android-ndk_auto-r10e/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86/bin/arm-linux-androideabi-ld AR=/home/jimmy/android-ndk_auto-r10e/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86/bin/arm-linux-androideabi-ar AS=/home/jimmy/android-ndk_auto-r10e/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86/bin/arm-linux-androideabi-as RANLIB=/home/jimmy/android-ndk_auto-r10e/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86/bin/arm-linux-androideabi-ranlib STRIP=/home/jimmy/android-ndk_auto-r10e/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86/bin/arm-linux-androideabi-strip CPATH=/home/jimmy/android-ndk_auto-r10e/platforms/android-9/arch-arm/usr/include ## --------- ## ## Platform. ## ## --------- ## hostname = ubuntu uname -m = x86_64 uname -r = 4.4.0-21-generic uname -s = Linux uname -v = #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 /usr/bin/uname -p = unknown /bin/uname -X = unknown /bin/arch = unknown /usr/bin/arch -k = unknown /usr/convex/getsysinfo = unknown /usr/bin/hostinfo = unknown /bin/machine = unknown /usr/bin/oslevel = unknown /bin/universe = unknown PATH: /home/jimmy/android-ndk_auto-r10e/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86/bin PATH: /usr/local/sbin PATH: /usr/local/bin PATH: /usr/sbin PATH: /usr/bin PATH: /sbin PATH: /bin ## ----------- ## ## Core tests. ## ## ----------- ## configure:2828: creating cache android_cross.cache configure:2934: checking build system type configure:2948: result: x86_64-pc-linux-gnu configure:2968: checking host system type configure:2981: result: arm-eabi-linux-gnu configure:3001: checking target system type configure:3014: result: arm-eabi-linux-gnu configure:3064: checking for a BSD-compatible install configure:3132: result: /usr/bin/install -c configure:3143: checking whether build environment is sane configure:3198: result: yes configure:3257: checking for arm-eabi-linux-strip configure:3284: result: /home/jimmy/android-ndk_auto-r10e/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86/bin/arm-linux-androideabi-strip configure:3349: checking for a thread-safe mkdir -p configure:3388: result: /bin/mkdir -p configure:3395: checking for gawk configure:3411: found /usr/bin/gawk configure:3422: result: gawk configure:3433: checking whether make sets $(MAKE) configure:3455: result: yes configure:3484: checking whether make supports nested variables configure:3501: result: yes configure:3591: checking whether UID '0' is supported by ustar format configure:3594: result: yes configure:3601: checking whether GID '0' is supported by ustar format configure:3604: result: yes configure:3612: checking how to create a ustar tar archive configure:3623: tar --version tar (GNU tar) 1.28 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Written by John Gilmore and Jay Fenlason. configure:3626: $? = 0 configure:3666: tardir=conftest.dir && eval tar --format=ustar -chf - "$tardir" >conftest.tar configure:3669: $? = 0 configure:3673: tar -xf - <conftest.tar configure:3676: $? = 0 configure:3678: cat conftest.dir/file GrepMe configure:3681: $? = 0 configure:3694: result: gnutar configure:3745: checking whether to enable maintainer-specific portions of Makefiles configure:3754: result: no configure:3771: checking whether ln -s works configure:3775: result: yes configure:3847: checking host platform characteristics configure:4065: result: ok configure:4110: checking for arm-eabi-linux-gcc configure:4137: result: /home/jimmy/android-ndk_auto-r10e/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86/bin/arm-linux-androideabi-gcc --sysroot=/home/jimmy/android-ndk_auto-r10e/platforms/android-9/arch-arm configure:4207: checking for arm-eabi-linux-gcc configure:4234: result: /home/jimmy/android-ndk_auto-r10e/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86/bin/arm-linux-androideabi-gcc --sysroot=/home/jimmy/android-ndk_auto-r10e/platforms/android-9/arch-arm configure:4503: checking for C compiler version configure:4512: /home/jimmy/android-ndk_auto-r10e/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86/bin/arm-linux-androideabi-gcc --sysroot=/home/jimmy/android-ndk_auto-r10e/platforms/android-9/arch-arm --version >&5 arm-linux-androideabi-gcc (GCC) 4.8 Copyright (C) 2013 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. configure:4523: $? = 0 configure:4512: /home/jimmy/android-ndk_auto-r10e/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86/bin/arm-linux-androideabi-gcc --sysroot=/home/jimmy/android-ndk_auto-r10e/platforms/android-9/arch-arm -v >&5 Using built-in specs. COLLECT_GCC=/home/jimmy/android-ndk_auto-r10e/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86/bin/arm-linux-androideabi-gcc COLLECT_LTO_WRAPPER=/home/jimmy/android-ndk_auto-r10e/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86/bin/../libexec/gcc/arm-linux-androideabi/4.8/lto-wrapper Target: arm-linux-androideabi Configured with: /s/ndk-toolchain/src/build/../gcc/gcc-4.8/configure --prefix=/tmp/ndk-andrewhsieh/build/toolchain/prefix --target=arm-linux-androideabi --host=x86_64-linux-gnu --build=x86_64-linux-gnu --with-gnu-as --with-gnu-ld --enable-languages=c,c++ --with-gmp=/tmp/ndk-andrewhsieh/build/toolchain/temp-install --with-mpfr=/tmp/ndk-andrewhsieh/build/toolchain/temp-install --with-mpc=/tmp/ndk-andrewhsieh/build/toolchain/temp-install --with-cloog=/tmp/ndk-andrewhsieh/build/toolchain/temp-install --with-isl=/tmp/ndk-andrewhsieh/build/toolchain/temp-install --with-ppl=/tmp/ndk-andrewhsieh/build/toolchain/temp-install --disable-ppl-version-check --disable-cloog-version-check --disable-isl-version-check --enable-cloog-backend=isl --with-host-libstdcxx='-static-libgcc -Wl,-Bstatic,-lstdc++,-Bdynamic -lm' --disable-libssp --enable-threads --disable-nls --disable-libmudflap --disable-libgomp --disable-libstdc__-v3 --disable-sjlj-exceptions --disable-shared --disable-tls --disable-libitm --with-float=soft --with-fpu=vfp --with-arch=armv5te --enable-target-optspace --enable-initfini-array --disable-nls --prefix=/tmp/ndk-andrewhsieh/build/toolchain/prefix --with-sysroot=/tmp/ndk-andrewhsieh/build/toolchain/prefix/sysroot --with-binutils-version=2.25 --with-mpfr-version=3.1.1 --with-mpc-version=1.0.1 --with-gmp-version=5.0.5 --with-gcc-version=4.8 --with-gdb-version=7.7 --with-python=/usr/local/google/home/andrewhsieh/mydroid/ndk/prebuilt/linux-x86/bin/python-config.sh --with-gxx-include-dir=/tmp/ndk-andrewhsieh/build/toolchain/prefix/include/c++/4.8 --with-bugurl=http://source.android.com/source/report-bugs.html --enable-languages=c,c++ --disable-bootstrap --enable-plugins --enable-libgomp --enable-gnu-indirect-function --disable-libsanitizer --enable-gold --enable-threads --enable-graphite=yes --with-cloog-version=0.18.0 --with-isl-version=0.11.1 --enable-eh-frame-hdr-for-static --with-arch=armv5te --program-transform-name='s&^&arm-linux-androideabi-&' --enable-gold=default Thread model: posix gcc version 4.8 (GCC) configure:4523: $? = 0 configure:4512: /home/jimmy/android-ndk_auto-r10e/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86/bin/arm-linux-androideabi-gcc --sysroot=/home/jimmy/android-ndk_auto-r10e/platforms/android-9/arch-arm -V >&5 arm-linux-androideabi-gcc: error: unrecognized command line option '-V' arm-linux-androideabi-gcc: fatal error: no input files compilation terminated. configure:4523: $? = 1 configure:4512: /home/jimmy/android-ndk_auto-r10e/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86/bin/arm-linux-androideabi-gcc --sysroot=/home/jimmy/android-ndk_auto-r10e/platforms/android-9/arch-arm -qversion >&5 arm-linux-androideabi-gcc: error: unrecognized command line option '-qversion' arm-linux-androideabi-gcc: fatal error: no input files compilation terminated. configure:4523: $? = 1 configure:4543: checking whether the C compiler works configure:4565: /home/jimmy/android-ndk_auto-r10e/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86/bin/arm-linux-androideabi-gcc --sysroot=/home/jimmy/android-ndk_auto-r10e/platforms/android-9/arch-arm -DANDROID -DPLATFORM_ANDROID -DLINUX -D__linux__ -DHAVE_USR_INCLUDE_MALLOC_H -DPAGE_SIZE=0x1000 -D_POSIX_PATH_MAX=256 -DS_IWRITE=S_IWUSR -DHAVE_PTHREAD_MUTEX_TIMEDLOCK -fpic -g -funwind-tables -ffunction-sections -fdata-sections -DARM_FPU_NONE=1 -march=armv5te -mtune=xscale -msoft-float -DANDROID -DPLATFORM_ANDROID -DLINUX -D__linux__ -DHAVE_USR_INCLUDE_MALLOC_H -DPAGE_SIZE=0x1000 -D_POSIX_PATH_MAX=256 -DS_IWRITE=S_IWUSR -DHAVE_PTHREAD_MUTEX_TIMEDLOCK -fpic -g -funwind-tables -ffunction-sections -fdata-sections -DARM_FPU_NONE=1 -march=armv5te -mtune=xscale -msoft-float -DGC_LINUX_THREADS -D_GNU_SOURCE -D_REENTRANT -DUSE_MMAP -DUSE_MUNMAP -Wl,--wrap,sigaction -L/home/jimmy/mono-unity-5.6/../../android_krait_signal_handler/build/obj/local/armeabi -lkrait-signal-handler -Wl,--no-undefined -Wl,--gc-sections -Wl,-rpath-link=/home/jimmy/android-ndk_auto-r10e/platforms/android-9/arch-arm/usr/lib -ldl -lm -llog -lc conftest.c >&5 /home/jimmy/android-ndk_auto-r10e/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: error: cannot find -lkrait-signal-handler collect2: error: ld returned 1 exit status configure:4569: $? = 1 configure:4607: result: no configure: failed program was: | /* confdefs.h */ | #define PACKAGE_NAME "" | #define PACKAGE_TARNAME "" | #define PACKAGE_VERSION "" | #define PACKAGE_STRING "" | #define PACKAGE_BUGREPORT "" | #define PACKAGE_URL "" | #define PACKAGE "mono" | #define VERSION "2.6.5" | /* end confdefs.h. */ | | int | main () | { | | ; | return 0; | } configure:4612: error: in `/home/jimmy/mono-unity-5.6': configure:4614: error: C compiler cannot create executables See `config.log' for more details ## ---------------- ## ## Cache variables. ## ## ---------------- ## ac_cv_build=x86_64-pc-linux-gnu ac_cv_env_CCASFLAGS_set= ac_cv_env_CCASFLAGS_value= ac_cv_env_CCAS_set= ac_cv_env_CCAS_value= ac_cv_env_CCC_set= ac_cv_env_CCC_value= ac_cv_env_CC_set=set ac_cv_env_CC_value='/home/jimmy/android-ndk_auto-r10e/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86/bin/arm-linux-androideabi-gcc --sysroot=/home/jimmy/android-ndk_auto-r10e/platforms/android-9/arch-arm' ac_cv_env_CFLAGS_set=set ac_cv_env_CFLAGS_value='-DANDROID -DPLATFORM_ANDROID -DLINUX -D__linux__ -DHAVE_USR_INCLUDE_MALLOC_H -DPAGE_SIZE=0x1000 -D_POSIX_PATH_MAX=256 -DS_IWRITE=S_IWUSR -DHAVE_PTHREAD_MUTEX_TIMEDLOCK -fpic -g -funwind-tables -ffunction-sections -fdata-sections -DARM_FPU_NONE=1 -march=armv5te -mtune=xscale -msoft-float' ac_cv_env_CPPFLAGS_set=set ac_cv_env_CPPFLAGS_value='-DANDROID -DPLATFORM_ANDROID -DLINUX -D__linux__ -DHAVE_USR_INCLUDE_MALLOC_H -DPAGE_SIZE=0x1000 -D_POSIX_PATH_MAX=256 -DS_IWRITE=S_IWUSR -DHAVE_PTHREAD_MUTEX_TIMEDLOCK -fpic -g -funwind-tables -ffunction-sections -fdata-sections -DARM_FPU_NONE=1 -march=armv5te -mtune=xscale -msoft-float' ac_cv_env_CPP_set=set ac_cv_env_CPP_value=/home/jimmy/android-ndk_auto-r10e/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86/bin/arm-linux-androideabi-cpp ac_cv_env_CXXCPP_set=set ac_cv_env_CXXCPP_value=/home/jimmy/android-ndk_auto-r10e/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86/bin/arm-linux-androideabi-cpp ac_cv_env_CXXFLAGS_set=set ac_cv_env_CXXFLAGS_value='-DANDROID -DPLATFORM_ANDROID -DLINUX -D__linux__ -DHAVE_USR_INCLUDE_MALLOC_H -DPAGE_SIZE=0x1000 -D_POSIX_PATH_MAX=256 -DS_IWRITE=S_IWUSR -DHAVE_PTHREAD_MUTEX_TIMEDLOCK -fpic -g -funwind-tables -ffunction-sections -fdata-sections -DARM_FPU_NONE=1 -march=armv5te -mtune=xscale -msoft-float' ac_cv_env_CXX_set=set ac_cv_env_CXX_value='/home/jimmy/android-ndk_auto-r10e/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86/bin/arm-linux-androideabi-g++ --sysroot=/home/jimmy/android-ndk_auto-r10e/platforms/android-9/arch-arm' ac_cv_env_LDFLAGS_set=set ac_cv_env_LDFLAGS_value='-Wl,--wrap,sigaction -L/home/jimmy/mono-unity-5.6/../../android_krait_signal_handler/build/obj/local/armeabi -lkrait-signal-handler -Wl,--no-undefined -Wl,--gc-sections -Wl,-rpath-link=/home/jimmy/android-ndk_auto-r10e/platforms/android-9/arch-arm/usr/lib -ldl -lm -llog -lc ' ac_cv_env_LIBS_set= ac_cv_env_LIBS_value= ac_cv_env_LT_SYS_LIBRARY_PATH_set= ac_cv_env_LT_SYS_LIBRARY_PATH_value= ac_cv_env_XMKMF_set= ac_cv_env_XMKMF_value= ac_cv_env_build_alias_set= ac_cv_env_build_alias_value= ac_cv_env_host_alias_set=set ac_cv_env_host_alias_value=arm-eabi-linux ac_cv_env_target_alias_set= ac_cv_env_target_alias_value= ac_cv_host=arm-eabi-linux-gnu ac_cv_path_install='/usr/bin/install -c' ac_cv_path_mkdir=/bin/mkdir ac_cv_prog_AWK=gawk ac_cv_prog_CC='/home/jimmy/android-ndk_auto-r10e/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86/bin/arm-linux-androideabi-gcc --sysroot=/home/jimmy/android-ndk_auto-r10e/platforms/android-9/arch-arm' ac_cv_prog_STRIP=/home/jimmy/android-ndk_auto-r10e/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86/bin/arm-linux-androideabi-strip ac_cv_prog_make_make_set=yes ac_cv_target=arm-eabi-linux-gnu am_cv_make_support_nested_variables=yes am_cv_prog_tar_ustar=gnutar mono_cv_uscore=yes ## ----------------- ## ## Output variables. ## ## ----------------- ## ACLOCAL='${SHELL} /home/jimmy/mono-unity-5.6/missing aclocal-1.15' ALPHA_FALSE='' ALPHA_TRUE='' AMD64_FALSE='' AMD64_TRUE='' AMDEPBACKSLASH='' AMDEP_FALSE='' AMDEP_TRUE='' AMTAR='$${TAR-tar}' AM_BACKSLASH='\' AM_DEFAULT_V='$(AM_DEFAULT_VERBOSITY)' AM_DEFAULT_VERBOSITY='1' AM_V='$(V)' API_VER='1.0' AR='/home/jimmy/android-ndk_auto-r10e/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86/bin/arm-linux-androideabi-ar' ARM_FALSE='' ARM_TRUE='' AS='/home/jimmy/android-ndk_auto-r10e/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86/bin/arm-linux-androideabi-as' AUTOCONF='${SHELL} /home/jimmy/mono-unity-5.6/missing autoconf' AUTOHEADER='${SHELL} /home/jimmy/mono-unity-5.6/missing autoheader' AUTOMAKE='${SHELL} /home/jimmy/mono-unity-5.6/missing automake-1.15' AWK='gawk' BISON='' BUILD_EXEEXT='' BUILD_GLIB_CFLAGS='' BUILD_GLIB_LIBS='' BUILD_MCS_FALSE='' BUILD_MCS_TRUE='' CC='/home/jimmy/android-ndk_auto-r10e/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86/bin/arm-linux-androideabi-gcc --sysroot=/home/jimmy/android-ndk_auto-r10e/platforms/android-9/arch-arm' CCAS='' CCASDEPMODE='' CCASFLAGS='' CCDEPMODE='' CC_FOR_BUILD='' CFLAGS='-DANDROID -DPLATFORM_ANDROID -DLINUX -D__linux__ -DHAVE_USR_INCLUDE_MALLOC_H -DPAGE_SIZE=0x1000 -D_POSIX_PATH_MAX=256 -DS_IWRITE=S_IWUSR -DHAVE_PTHREAD_MUTEX_TIMEDLOCK -fpic -g -funwind-tables -ffunction-sections -fdata-sections -DARM_FPU_NONE=1 -march=armv5te -mtune=xscale -msoft-float' CFLAGS_FOR_BUILD='' CPP='/home/jimmy/android-ndk_auto-r10e/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86/bin/arm-linux-androideabi-cpp' CPPFLAGS='-DANDROID -DPLATFORM_ANDROID -DLINUX -D__linux__ -DHAVE_USR_INCLUDE_MALLOC_H -DPAGE_SIZE=0x1000 -D_POSIX_PATH_MAX=256 -DS_IWRITE=S_IWUSR -DHAVE_PTHREAD_MUTEX_TIMEDLOCK -fpic -g -funwind-tables -ffunction-sections -fdata-sections -DARM_FPU_NONE=1 -march=armv5te -mtune=xscale -msoft-float -DGC_LINUX_THREADS -D_GNU_SOURCE -D_REENTRANT -DUSE_MMAP -DUSE_MUNMAP' CROSS_COMPILING_FALSE='' CROSS_COMPILING_TRUE='' CXX='/home/jimmy/android-ndk_auto-r10e/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86/bin/arm-linux-androideabi-g++ --sysroot=/home/jimmy/android-ndk_auto-r10e/platforms/android-9/arch-arm' CXXCPP='/home/jimmy/android-ndk_auto-r10e/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86/bin/arm-linux-androideabi-cpp' CXXDEPMODE='' CXXFLAGS='-DANDROID -DPLATFORM_ANDROID -DLINUX -D__linux__ -DHAVE_USR_INCLUDE_MALLOC_H -DPAGE_SIZE=0x1000 -D_POSIX_PATH_MAX=256 -DS_IWRITE=S_IWUSR -DHAVE_PTHREAD_MUTEX_TIMEDLOCK -fpic -g -funwind-tables -ffunction-sections -fdata-sections -DARM_FPU_NONE=1 -march=armv5te -mtune=xscale -msoft-float' CYGPATH_W='echo' DEFS='' DEPDIR='' DISABLE_JIT_FALSE='' DISABLE_JIT_TRUE='' DISABLE_MCS_DOCS_FALSE='' DISABLE_MCS_DOCS_TRUE='' DISABLE_PROFILER_FALSE='' DISABLE_PROFILER_TRUE='' DISABLE_SHARED_HANDLES='' DLLTOOL='' DOLT_BASH='' DSYMUTIL='' DTRACE='' DTRACEFLAGS='' DTRACE_G_REQUIRED_FALSE='' DTRACE_G_REQUIRED_TRUE='' DUMPBIN='' ECHO_C='' ECHO_N='-n' ECHO_T='' EGLIB_BUILD_FALSE='' EGLIB_BUILD_TRUE='' EGREP='' ENABLE_DTRACE_FALSE='' ENABLE_DTRACE_TRUE='' ENABLE_LLVM_FALSE='' ENABLE_LLVM_TRUE='' ENABLE_NUNIT_TESTS_FALSE='' ENABLE_NUNIT_TESTS_TRUE='' EXEEXT='' FGREP='' GETTEXT_MACRO_VERSION='' GLIB_CFLAGS='' GLIB_LIBS='' GMODULE_CFLAGS='' GMODULE_LIBS='' GMSGFMT='' GMSGFMT_015='' GREP='' HAVE_BOEHM_GC='' HAVE_MSGFMT='' HAVE_OPROFILE_FALSE='' HAVE_OPROFILE_TRUE='' HAVE_ZLIB_FALSE='' HAVE_ZLIB_TRUE='' HOST_CC='' HPPA_FALSE='' HPPA_TRUE='' IA64_FALSE='' IA64_TRUE='' INCLUDED_LIBGC_FALSE='' INCLUDED_LIBGC_TRUE='' INSTALL_2_0_FALSE='' INSTALL_2_0_TRUE='' INSTALL_2_1_FALSE='' INSTALL_2_1_TRUE='' INSTALL_4_0_FALSE='' INSTALL_4_0_TRUE='' INSTALL_DATA='${INSTALL} -m 644' INSTALL_MONOTOUCH_FALSE='' INSTALL_MONOTOUCH_TRUE='' INSTALL_PROGRAM='${INSTALL}' INSTALL_SCRIPT='${INSTALL}' INSTALL_STRIP_PROGRAM='$(install_sh) -c -s' INSTALL_UNITY_FALSE='' INSTALL_UNITY_TRUE='' INTERP_SUPPORTED_FALSE='' INTERP_SUPPORTED_TRUE='' INTL='' JIT_SUPPORTED_FALSE='' JIT_SUPPORTED_TRUE='' LD='/home/jimmy/android-ndk_auto-r10e/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86/bin/arm-linux-androideabi-ld' LDFLAGS='-Wl,--wrap,sigaction -L/home/jimmy/mono-unity-5.6/../../android_krait_signal_handler/build/obj/local/armeabi -lkrait-signal-handler -Wl,--no-undefined -Wl,--gc-sections -Wl,-rpath-link=/home/jimmy/android-ndk_auto-r10e/platforms/android-9/arch-arm/usr/lib -ldl -lm -llog -lc ' LIBC='' LIBGC_CFLAGS='' LIBGC_LIBS='' LIBGC_STATIC_LIBS='' LIBOBJS='' LIBS='' LIBTOOL='' LIPO='' LLVM_CFLAGS='' LLVM_CONFIG='' LLVM_CXXFLAGS='' LLVM_LDFLAGS='' LLVM_LIBS='' LN_S='ln -s' LTCOMPILE='' LTCXXCOMPILE='' LTLIBOBJS='' LT_SYS_LIBRARY_PATH='' M68K_FALSE='' M68K_TRUE='' MAINT='#' MAINTAINER_MODE_FALSE='' MAINTAINER_MODE_TRUE='#' MAKEINFO='${SHELL} /home/jimmy/mono-unity-5.6/missing makeinfo' MANIFEST_TOOL='' MIPS_FALSE='' MIPS_GCC_FALSE='' MIPS_GCC_TRUE='' MIPS_SGI_FALSE='' MIPS_SGI_TRUE='' MIPS_TRUE='' MKDIR_P='/bin/mkdir -p' MONO_DEBUGGER_SUPPORTED_FALSE='' MONO_DEBUGGER_SUPPORTED_TRUE='' MONO_DL_NEED_USCORE='' MSGFMT='' MSGFMT_015='' MSGMERGE='' NM='' NMEDIT='' NO_VERSION_SCRIPT_FALSE='' NO_VERSION_SCRIPT_TRUE='' OBJDUMP='' OBJEXT='' OPROFILE_CFLAGS='' OPROFILE_LIBS='' OTOOL64='' OTOOL='' PACKAGE='mono' PACKAGE_BUGREPORT='' PACKAGE_NAME='' PACKAGE_STRING='' PACKAGE_TARNAME='' PACKAGE_URL='' PACKAGE_VERSION='' PATH_SEPARATOR=':' PKG_CONFIG='' PLATFORM_DARWIN_FALSE='' PLATFORM_DARWIN_TRUE='#' PLATFORM_LINUX_FALSE='#' PLATFORM_LINUX_TRUE='' PLATFORM_SIGPOSIX_FALSE='#' PLATFORM_SIGPOSIX_TRUE='' PLATFORM_WIN32_FALSE='' PLATFORM_WIN32_TRUE='#' POWERPC64_FALSE='' POWERPC64_TRUE='' POWERPC_FALSE='' POWERPC_TRUE='' RANLIB='/home/jimmy/android-ndk_auto-r10e/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86/bin/arm-linux-androideabi-ranlib' S390_FALSE='' S390_TRUE='' S390x_FALSE='' S390x_TRUE='' SED='' SET_MAKE='' SHELL='/bin/bash' SPARC64_FALSE='' SPARC64_TRUE='' SPARC_FALSE='' SPARC_TRUE='' SQLITE3='' SQLITE='' STATIC_MONO_FALSE='' STATIC_MONO_TRUE='' STRIP='/home/jimmy/android-ndk_auto-r10e/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86/bin/arm-linux-androideabi-strip' USE_BATCH_FILES_FALSE='' USE_BATCH_FILES_TRUE='' USE_JIT_FALSE='' USE_JIT_TRUE='' USE_NLS='' VERSION='2.6.5' X11='' X86_FALSE='' X86_TRUE='' XATTR_LIB='' XGETTEXT='' XGETTEXT_015='' XGETTEXT_EXTRA_OPTIONS='' XMKMF='' ac_ct_AR='' ac_ct_CC='' ac_ct_CXX='' ac_ct_DUMPBIN='' am__EXEEXT_FALSE='' am__EXEEXT_TRUE='' am__fastdepCCAS_FALSE='' am__fastdepCCAS_TRUE='' am__fastdepCC_FALSE='' am__fastdepCC_TRUE='' am__fastdepCXX_FALSE='' am__fastdepCXX_TRUE='' am__include='' am__isrc='' am__leading_dot='.' am__nodep='' am__quote='' am__tar='tar --format=ustar -chf - "$$tardir"' am__untar='tar -xf -' arch_target='' bindir='${exec_prefix}/bin' build='x86_64-pc-linux-gnu' build_alias='' build_cpu='x86_64' build_os='linux-gnu' build_vendor='pc' datadir='${datarootdir}' datarootdir='${prefix}/share' docdir='${datarootdir}/doc/${PACKAGE}' docs_dir='' dvidir='${docdir}' eglib_dir='' exec_prefix='NONE' export_ldflags='' host='arm-eabi-linux-gnu' host_alias='arm-eabi-linux' host_cpu='arm' host_os='linux-gnu' host_vendor='eabi' htmldir='${docdir}' ikvm_native_dir='' includedir='${prefix}/include' infodir='${datarootdir}/info' install_sh='${SHELL} /home/jimmy/mono-unity-5.6/install-sh' libdir='${exec_prefix}/lib' libexecdir='${exec_prefix}/libexec' libgc_dir='' libgdiplus_loc='' libmono_cflags='-D_REENTRANT' libmono_ldflags='' libsuffix='' localedir='${datarootdir}/locale' localstatedir='${prefix}/var' mandir='${datarootdir}/man' mcs_topdir='' mcs_topdir_from_srcdir='' mkdir_p='$(MKDIR_P)' mono_build_root='' mono_cfg_dir='' mono_runtime='' oldincludedir='/usr/include' pdfdir='${docdir}' prefix='/home/jimmy/mono-unity-5.6/builds/android' program_transform_name='s,x,x,' psdir='${docdir}' reloc_libdir='lib' runstatedir='${localstatedir}/run' sbindir='${exec_prefix}/sbin' sharedstatedir='${prefix}/com' subdirs='' sysconfdir='${prefix}/etc' target='arm-eabi-linux-gnu' target_alias='' target_cpu='arm' target_os='linux-gnu' target_vendor='eabi' ## ----------- ## ## confdefs.h. ## ## ----------- ## /* confdefs.h */ #define PACKAGE_NAME "" #define PACKAGE_TARNAME "" #define PACKAGE_VERSION "" #define PACKAGE_STRING "" #define PACKAGE_BUGREPORT "" #define PACKAGE_URL "" #define PACKAGE "mono" #define VERSION "2.6.5" configure: exit 77

ndk在windows下编译问题

现在的ndk已经自带编译环境,可以直接执行ndk-build.cmd进行编译。但是遇到一个问题, 在编译时识别到相对路径时不会转换,如下图: ![图片说明](https://img-ask.csdn.net/upload/201511/02/1446464005_465688.png) 相对路径变得那么长,以至于超过了windows的最大文件长度, 求解决方法

配置Linux编译环境时出现arm-linux-gnueabihf-gcc: fatal error: no input files问题

按照步骤 下载好arm-linux-gnueabihf-gcc相关文件,改好环境变量 打开控制台输入 arm按tab也会弹出来了 ![图片说明](https://img-ask.csdn.net/upload/201905/25/1558773677_170541.jpg) 但是打开eclipse写一段代码编译时候又弹出错误 ![图片说明](https://img-ask.csdn.net/upload/201905/25/1558773773_740787.jpg) 然后我到控制台试一下 也是同样的问题 ![图片说明](https://img-ask.csdn.net/upload/201905/25/1558773922_399462.jpg)

VFP9编译的多线程文件(DLL)的问题

VFP9编译的多线程文件(DLL),能不能独立与程序结全,而不要原来的.PRG文件,如果能相对会保密一些重要的程序,我一旦将生成的它的.PRG程序移开,整个程序一编译,马上就出错了?

如何用VC6编一个联接SQL2000数据库的句柄,并编译成.fll的格式,给VFP9.0调用!

如何用VC6编一个联接SQL2000数据库的句柄,并编译成.fll的格式,给VFP9.0调用,只要求一个简单的实例,大侠高手们,高台贵手一下!

VFP如何调用C#编译的DLL

RT,如题。譬如A.DLL,里面有个类名为Ainfo,类里的方法GetAinfo(参数1,参数2)。VFP怎么调用这方法,还有这DLL存放的位置有什么规则。请大神赐教

为什么我的交叉编译CGO二进制文件不能在Raspberry Pi(Raspbian)上运行?

<div class="post-text" itemprop="text"> <p>When I compile the following snippet of code (<a href="http://play.golang.org/p/wHb5Mtco2I" rel="nofollow">playground link</a>):</p> <pre><code>package main /* #cgo LDFLAGS: -lbluetooth #include &lt;bluetooth/bluetooth.h&gt; #include &lt;bluetooth/hci.h&gt; #include &lt;bluetooth/hci_lib.h&gt; */ import "C" func main() { C.hci_get_route(nil) } </code></pre> <p>…using these environment variables:</p> <pre><code>CC=arm-linux-gnueabihf-gcc CGO_ENABLED=1 GOARCH=arm GOARM=6 </code></pre> <p>I get a 1.6Mb binary that:</p> <ul> <li>works on my ODROID-C1 (ARMv7, running Arch, from archlinuxarm.org), but</li> <li>does not work on my Raspberry Pi B+ (ARMv6, running Raspbian, from raspberrypi.org).</li> </ul> <p>When I run it on the Pi, I get a "<code>Segmentation fault</code>".</p> <p>When I run it with these environment variables:</p> <pre><code>LD_PRELOAD=/lib/arm-linux-gnueabihf/libSegFault.so SEGFAULT_USE_ALTSTACK=1 </code></pre> <p>I get this output:</p> <pre><code>*** Segmentation fault Register dump: R0: 00000000 R1: 00000001 R2: bebf37f4 R3: bebf37fc R4: 00000000 R5: 00000000 R6: 00010c59 R7: 00000000 R8: 00000000 R9: 00000000 SL: b6f33000 FP: 00000000 IP: 0000004f SP: bebf37ec LR: 00010c6b PC: 0005d7f4 CPSR: 40000030 Trap: 0000000e Error: 00000817 OldMask: 00000000 Addr: 00000001 Backtrace: Memory map: 00010000-00125000 r-xp 00000000 b3:02 16193 /home/pi/test 00135000-0013b000 rw-p 00115000 b3:02 16193 /home/pi/test 0013b000-0014a000 rw-p 00000000 00:00 0 0026b000-00290000 rw-p 00000000 00:00 0 [heap] b6d53000-b6d73000 r-xp 00000000 b3:02 16080 /lib/arm-linux-gnueabihf/libgcc_s.so.1 b6d73000-b6d7a000 ---p 00020000 b3:02 16080 /lib/arm-linux-gnueabihf/libgcc_s.so.1 b6d7a000-b6d7b000 rw-p 0001f000 b3:02 16080 /lib/arm-linux-gnueabihf/libgcc_s.so.1 b6d7b000-b6e9f000 r-xp 00000000 b3:02 4254 /lib/arm-linux-gnueabihf/libc-2.13.so b6e9f000-b6ea6000 ---p 00124000 b3:02 4254 /lib/arm-linux-gnueabihf/libc-2.13.so b6ea6000-b6ea8000 r--p 00123000 b3:02 4254 /lib/arm-linux-gnueabihf/libc-2.13.so b6ea8000-b6ea9000 rw-p 00125000 b3:02 4254 /lib/arm-linux-gnueabihf/libc-2.13.so b6ea9000-b6eac000 rw-p 00000000 00:00 0 b6eac000-b6ec0000 r-xp 00000000 b3:02 4247 /lib/arm-linux-gnueabihf/libpthread-2.13.so b6ec0000-b6ec7000 ---p 00014000 b3:02 4247 /lib/arm-linux-gnueabihf/libpthread-2.13.so b6ec7000-b6ec8000 r--p 00013000 b3:02 4247 /lib/arm-linux-gnueabihf/libpthread-2.13.so b6ec8000-b6ec9000 rw-p 00014000 b3:02 4247 /lib/arm-linux-gnueabihf/libpthread-2.13.so b6ec9000-b6ecb000 rw-p 00000000 00:00 0 b6ecb000-b6ee0000 r-xp 00000000 b3:02 44311 /usr/lib/arm-linux-gnueabihf/libbluetooth.so.3.12.0 b6ee0000-b6ee7000 ---p 00015000 b3:02 44311 /usr/lib/arm-linux-gnueabihf/libbluetooth.so.3.12.0 b6ee7000-b6ee8000 r--p 00014000 b3:02 44311 /usr/lib/arm-linux-gnueabihf/libbluetooth.so.3.12.0 b6ee8000-b6eea000 rw-p 00015000 b3:02 44311 /usr/lib/arm-linux-gnueabihf/libbluetooth.so.3.12.0 b6ef8000-b6efa000 r-xp 00000000 b3:02 25761 /usr/lib/arm-linux-gnueabihf/libcofi_rpi.so b6efa000-b6f01000 ---p 00002000 b3:02 25761 /usr/lib/arm-linux-gnueabihf/libcofi_rpi.so b6f01000-b6f02000 rw-p 00001000 b3:02 25761 /usr/lib/arm-linux-gnueabihf/libcofi_rpi.so b6f02000-b6f04000 r-xp 00000000 b3:02 4246 /lib/arm-linux-gnueabihf/libSegFault.so b6f04000-b6f0b000 ---p 00002000 b3:02 4246 /lib/arm-linux-gnueabihf/libSegFault.so b6f0b000-b6f0c000 r--p 00001000 b3:02 4246 /lib/arm-linux-gnueabihf/libSegFault.so b6f0c000-b6f0d000 rw-p 00002000 b3:02 4246 /lib/arm-linux-gnueabihf/libSegFault.so b6f0d000-b6f2a000 r-xp 00000000 b3:02 4248 /lib/arm-linux-gnueabihf/ld-2.13.so b6f2e000-b6f32000 rw-p 00000000 00:00 0 b6f32000-b6f33000 r--p 0001d000 b3:02 4248 /lib/arm-linux-gnueabihf/ld-2.13.so b6f33000-b6f34000 rw-p 0001e000 b3:02 4248 /lib/arm-linux-gnueabihf/ld-2.13.so bebd3000-bebf4000 rw-p 00000000 00:00 0 bee7f000-bee80000 r-xp 00000000 00:00 0 [sigpage] ffff0000-ffff1000 r-xp 00000000 00:00 0 [vectors] Segmentation fault </code></pre> <p>Removing <code>/usr/lib/arm-linux-gnueabihf/libcofi_rpi.so</code> from <code>/etc/ld.so.preload</code> gives me the same output, except with no lines containing <code>libcofi_rpi.so</code>.</p> <p>Trying to build a statically linked binary with <code>-tags netgo -a -ldflags "-linkmode external -extldflags -static"</code> gives me an "<code>Illegal instruction</code>" instead of the "<code>Segmentation fault</code>".</p> <p>Trying to build the binary on the Pi itself works, however, I want to cross-compile this. And cross compilation works indeed, but only on the ODROID-C1/Arch, not on the Raspberry Pi/Raspbian.</p> <p>The exact build steps I use can be reproduced using Docker:</p> <pre><code>$ docker run -it golang:1.4.1-cross bash </code></pre> <p>Inside docker, I run:</p> <pre class="lang-sh prettyprint-override"><code>echo "deb http://emdebian.org/tools/debian/ jessie main" &gt;/etc/apt/sources.list.d/crosstools.list curl -s http://emdebian.org/tools/debian/emdebian-toolchain-archive.key | apt-key add - dpkg --add-architecture armhf apt-get update apt-get install -y crossbuild-essential-armhf libbluetooth-dev:armhf export CC=arm-linux-gnueabihf-gcc export CGO_ENABLED=1 export GOARCH=arm export GOARM=6 go build -o test test.go </code></pre> <p>This gives me an executable named "test" that, as noted above, will not run on the Pi.</p> <p>Here's some info about my test devices:</p> <h3>Raspberry Pi B+:</h3> <pre><code>$ uname -a Linux raspberrypi 3.18.5+ #744 PREEMPT Fri Jan 30 18:19:07 GMT 2015 armv6l GNU/Linux $ cat /proc/cpuinfo processor : 0 model name : ARMv6-compatible processor rev 7 (v6l) BogoMIPS : 2.00 Features : half thumb fastmult vfp edsp java tls CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xb76 CPU revision : 7 Hardware : BCM2708 Revision : 0010 Serial : 000000002a69d702 $ ldd test /usr/lib/arm-linux-gnueabihf/libcofi_rpi.so (0xb6f01000) libbluetooth.so.3 =&gt; /usr/lib/arm-linux-gnueabihf/libbluetooth.so.3 (0xb6ed4000) libpthread.so.0 =&gt; /lib/arm-linux-gnueabihf/libpthread.so.0 (0xb6eb5000) libc.so.6 =&gt; /lib/arm-linux-gnueabihf/libc.so.6 (0xb6d84000) /lib/ld-linux-armhf.so.3 (0xb6f0e000) </code></pre> <p><strong>Installed Bluetooth libraries:</strong></p> <pre><code>$ dpkg -s libbluetooth3 Package: libbluetooth3 Status: install ok installed Priority: optional Section: libs Installed-Size: 172 Maintainer: Debian Bluetooth Maintainers &lt;pkg-bluetooth-maintainers@lists.alioth.debian.org&gt; Architecture: armhf Multi-Arch: same Source: bluez Version: 4.99-2 Replaces: libsdp2 (&lt;= 1.5-2) Depends: libc6 (&gt;= 2.13-28) Pre-Depends: multiarch-support Conflicts: libsdp2 (&lt;= 1.5-2) Description: Library to use the BlueZ Linux Bluetooth stack BlueZ is the official Linux Bluetooth protocol stack. It is an Open Source project distributed under GNU General Public License (GPL). Homepage: http://www.bluez.org </code></pre> <h3>ODROID-C1:</h3> <pre><code>$ uname -a Linux alarm 3.10.66-1-ARCH #1 SMP PREEMPT Wed Jan 28 18:12:35 MST 2015 armv7l GNU/Linux $ cat /proc/cpuinfo Processor : ARMv7 Processor rev 1 (v7l) processor : 0 BogoMIPS : 3.27 processor : 1 BogoMIPS : 3.27 processor : 2 BogoMIPS : 3.27 processor : 3 BogoMIPS : 3.27 Features : swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc05 CPU revision : 1 Hardware : ODROIDC Revision : 000a Serial : 1b00000000000000 $ ldd test libbluetooth.so.3 =&gt; /usr/lib/libbluetooth.so.3 (0xb6eaf000) libpthread.so.0 =&gt; /usr/lib/libpthread.so.0 (0xb6e87000) libc.so.6 =&gt; /usr/lib/libc.so.6 (0xb6d48000) /lib/ld-linux-armhf.so.3 (0xb6ed1000) </code></pre> <p><strong>Installed Bluetooth libraries &amp; development headers files:</strong></p> <pre><code>$ pacman -Qe bluez bluez 5.27-1 </code></pre> <h3>Docker build environment</h3> <pre><code>$ uname -a Linux 094aa2ed34a5 3.18.5-gentoo-tp #1 SMP Fri Feb 6 20:14:55 CET 2015 x86_64 GNU/Linux </code></pre> <p><strong>Installed Bluetooth development headers:</strong></p> <pre><code>$ dpkg -s libbluetooth-dev:armhf Package: libbluetooth-dev Status: install ok installed Priority: extra Section: libdevel Installed-Size: 429 Maintainer: Debian Bluetooth Maintainers &lt;pkg-bluetooth-maintainers@lists.alioth.debian.org&gt; Architecture: armhf Source: bluez (5.23-2) Version: 5.23-2+b1 Replaces: libsdp2-dev (&lt;= 1.5.2) Provides: libbluetooth3-dev Depends: libbluetooth3 (= 5.23-2+b1), libc6-dev | libc-dev Suggests: pkg-config Conflicts: bluez-pan, libbluetooth-dev, libsdp2-dev (&lt;= 1.5.2) Description: Development files for using the BlueZ Linux Bluetooth library BlueZ is the official Linux Bluetooth protocol stack. It is an Open Source project distributed under GNU General Public License (GPL). Homepage: http://www.bluez.org </code></pre> <hr> <p>Installing the exact same version of <code>libbluetooth-dev</code> in the Docker container as the one that is available on the Pi makes no difference.</p> <hr> <p>Copying over the newer <code>libbluetooth.so</code> from Jessie to Wheezie gives me this error:</p> <pre><code>./test: /lib/arm-linux-gnueabihf/libc.so.6: version `GLIBC_2.15' not found (required by /home/pi/libbluetooth.so.3.17.11) </code></pre> <hr> <h3>UPDATE:</h3> <p>Tried with Arch on the Pi, the cross compiled binary also segfaults, giving the same message ("<code>Illegal instruction (core dumped)</code>") with <code>GOARM=5</code>, <code>6</code> or <code>7</code>.</p> <p>So far I haven't found a way to cross-compile CGO code for the Pi, linked against <code>libbluetooth</code>.</p> <p>Will try with the Raspberry Pi 2 tomorrow.</p> </div>

VFP9在win7下编辑成员数据的问题

VFP9 在 Win7环境下无法编辑 成员数据时出现 ![图片说明](https://img-ask.csdn.net/upload/201502/08/1423406113_969476.png) 选1没反应,选2出现![图片说明](https://img-ask.csdn.net/upload/201502/08/1423406124_257777.png) 求教什么原因,怎么解决

在中国程序员是青春饭吗?

今年,我也32了 ,为了不给大家误导,咨询了猎头、圈内好友,以及年过35岁的几位老程序员……舍了老脸去揭人家伤疤……希望能给大家以帮助,记得帮我点赞哦。 目录: 你以为的人生 一次又一次的伤害 猎头界的真相 如何应对互联网行业的「中年危机」 一、你以为的人生 刚入行时,拿着傲人的工资,想着好好干,以为我们的人生是这样的: 等真到了那一天,你会发现,你的人生很可能是这样的: ...

删库了,我们一定要跑路吗?

在工作中,我们误删数据或者数据库,我们一定需要跑路吗?我看未必,程序员一定要学会自救,神不知鬼不觉的将数据找回。 在 mysql 数据库中,我们知道 binlog 日志记录了我们对数据库的所有操作,所以 binlog 日志就是我们自救的利器。 接下来就来开启程序员自救之路。 想要自救成功,binlog 这把利器一定要好,在自己之前,我们一定要确定我们有 binlog 这把利器,以下就是确保有 bi...

再不跳槽,应届毕业生拿的都比我多了!

跳槽几乎是每个人职业生涯的一部分,很多HR说“三年两跳”已经是一个跳槽频繁与否的阈值了,可为什么市面上有很多程序员不到一年就跳槽呢?他们不担心影响履历吗? PayScale之前发布的**《员工最短任期公司排行榜》中,两家码农大厂Amazon和Google**,以1年和1.1年的员工任期中位数分列第二、第四名。 PayScale:员工最短任期公司排行榜 意外的是,任期中位数极小的这两家公司,薪资...

我以为我学懂了数据结构,直到看了这个导图才发现,我错了

数据结构与算法思维导图

技术大佬:我去,你写的 switch 语句也太老土了吧

昨天早上通过远程的方式 review 了两名新来同事的代码,大部分代码都写得很漂亮,严谨的同时注释也很到位,这令我非常满意。但当我看到他们当中有一个人写的 switch 语句时,还是忍不住破口大骂:“我擦,小王,你丫写的 switch 语句也太老土了吧!” 来看看小王写的代码吧,看完不要骂我装逼啊。 private static String createPlayer(PlayerTypes p...

华为初面+综合面试(Java技术面)附上面试题

华为面试整体流程大致分为笔试,性格测试,面试,综合面试,回学校等结果。笔试来说,华为的难度较中等,选择题难度和网易腾讯差不多。最后的代码题,相比下来就简单很多,一共3道题目,前2题很容易就AC,题目已经记不太清楚,不过难度确实不大。最后一题最后提交的代码过了75%的样例,一直没有发现剩下的25%可能存在什么坑。 笔试部分太久远,我就不怎么回忆了。直接将面试。 面试 如果说腾讯的面试是挥金如土...

和黑客斗争的 6 天!

互联网公司工作,很难避免不和黑客们打交道,我呆过的两家互联网公司,几乎每月每天每分钟都有黑客在公司网站上扫描。有的是寻找 Sql 注入的缺口,有的是寻找线上服务器可能存在的漏洞,大部分都...

讲一个程序员如何副业月赚三万的真实故事

loonggg读完需要3分钟速读仅需 1 分钟大家好,我是你们的校长。我之前讲过,这年头,只要肯动脑,肯行动,程序员凭借自己的技术,赚钱的方式还是有很多种的。仅仅靠在公司出卖自己的劳动时...

上班一个月,后悔当初着急入职的选择了

最近有个老铁,告诉我说,上班一个月,后悔当初着急入职现在公司了。他之前在美图做手机研发,今年美图那边今年也有一波组织优化调整,他是其中一个,在协商离职后,当时捉急找工作上班,因为有房贷供着,不能没有收入来源。所以匆忙选了一家公司,实际上是一个大型外包公司,主要派遣给其他手机厂商做外包项目。**当时承诺待遇还不错,所以就立马入职去上班了。但是后面入职后,发现薪酬待遇这块并不是HR所说那样,那个HR自...

女程序员,为什么比男程序员少???

昨天看到一档综艺节目,讨论了两个话题:(1)中国学生的数学成绩,平均下来看,会比国外好?为什么?(2)男生的数学成绩,平均下来看,会比女生好?为什么?同时,我又联想到了一个技术圈经常讨...

副业收入是我做程序媛的3倍,工作外的B面人生是怎样的?

提到“程序员”,多数人脑海里首先想到的大约是:为人木讷、薪水超高、工作枯燥…… 然而,当离开工作岗位,撕去层层标签,脱下“程序员”这身外套,有的人生动又有趣,马上展现出了完全不同的A/B面人生! 不论是简单的爱好,还是正经的副业,他们都干得同样出色。偶尔,还能和程序员的特质结合,产生奇妙的“化学反应”。 @Charlotte:平日素颜示人,周末美妆博主 大家都以为程序媛也个个不修边幅,但我们也许...

MySQL数据库面试题(2020最新版)

文章目录数据库基础知识为什么要使用数据库什么是SQL?什么是MySQL?数据库三大范式是什么mysql有关权限的表都有哪几个MySQL的binlog有有几种录入格式?分别有什么区别?数据类型mysql有哪些数据类型引擎MySQL存储引擎MyISAM与InnoDB区别MyISAM索引与InnoDB索引的区别?InnoDB引擎的4大特性存储引擎选择索引什么是索引?索引有哪些优缺点?索引使用场景(重点)...

如果你是老板,你会不会踢了这样的员工?

有个好朋友ZS,是技术总监,昨天问我:“有一个老下属,跟了我很多年,做事勤勤恳恳,主动性也很好。但随着公司的发展,他的进步速度,跟不上团队的步伐了,有点...

我入职阿里后,才知道原来简历这么写

私下里,有不少读者问我:“二哥,如何才能写出一份专业的技术简历呢?我总感觉自己写的简历太烂了,所以投了无数份,都石沉大海了。”说实话,我自己好多年没有写过简历了,但我认识的一个同行,他在阿里,给我说了一些他当年写简历的方法论,我感觉太牛逼了,实在是忍不住,就分享了出来,希望能够帮助到你。 01、简历的本质 作为简历的撰写者,你必须要搞清楚一点,简历的本质是什么,它就是为了来销售你的价值主张的。往深...

外包程序员的幸福生活

今天给你们讲述一个外包程序员的幸福生活。男主是Z哥,不是在外包公司上班的那种,是一名自由职业者,接外包项目自己干。接下来讲的都是真人真事。 先给大家介绍一下男主,Z哥,老程序员,是我十多年前的老同事,技术大牛,当过CTO,也创过业。因为我俩都爱好喝酒、踢球,再加上住的距离不算远,所以一直也断断续续的联系着,我对Z哥的状况也有大概了解。 Z哥几年前创业失败,后来他开始干起了外包,利用自己的技术能...

现代的 “Hello, World”,可不仅仅是几行代码而已

作者 |Charles R. Martin译者 | 弯月,责编 | 夕颜头图 |付费下载自视觉中国出品 | CSDN(ID:CSDNnews)新手...

!大部分程序员只会写3年代码

如果世界上都是这种不思进取的软件公司,那别说大部分程序员只会写 3 年代码,恐怕就没有程序员这种职业。

离职半年了,老东家又发 offer,回不回?

有小伙伴问松哥这个问题,他在上海某公司,在离职了几个月后,前公司的领导联系到他,希望他能够返聘回去,他很纠结要不要回去? 俗话说好马不吃回头草,但是这个小伙伴既然感到纠结了,我觉得至少说明了两个问题:1.曾经的公司还不错;2.现在的日子也不是很如意。否则应该就不会纠结了。 老实说,松哥之前也有过类似的经历,今天就来和小伙伴们聊聊回头草到底吃不吃。 首先一个基本观点,就是离职了也没必要和老东家弄的苦...

HTTP与HTTPS的区别

面试官问HTTP与HTTPS的区别,我这样回答让他竖起大拇指!

程序员毕业去大公司好还是小公司好?

虽然大公司并不是人人都能进,但我仍建议还未毕业的同学,尽力地通过校招向大公司挤,但凡挤进去,你这一生会容易很多。 大公司哪里好?没能进大公司怎么办?答案都在这里了,记得帮我点赞哦。 目录: 技术氛围 内部晋升与跳槽 啥也没学会,公司倒闭了? 不同的人脉圈,注定会有不同的结果 没能去大厂怎么办? 一、技术氛围 纵观整个程序员技术领域,哪个在行业有所名气的大牛,不是在大厂? 而且众所...

男生更看重女生的身材脸蛋,还是思想?

往往,我们看不进去大段大段的逻辑。深刻的哲理,往往短而精悍,一阵见血。问:产品经理挺漂亮的,有点心动,但不知道合不合得来。男生更看重女生的身材脸蛋,还是...

程序员为什么千万不要瞎努力?

本文作者用对比非常鲜明的两个开发团队的故事,讲解了敏捷开发之道 —— 如果你的团队缺乏统一标准的环境,那么即使勤劳努力,不仅会极其耗时而且成果甚微,使用...

为什么程序员做外包会被瞧不起?

二哥,有个事想询问下您的意见,您觉得应届生值得去外包吗?公司虽然挺大的,中xx,但待遇感觉挺低,马上要报到,挺纠结的。

当HR压你价,说你只值7K,你该怎么回答?

当HR压你价,说你只值7K时,你可以流畅地回答,记住,是流畅,不能犹豫。 礼貌地说:“7K是吗?了解了。嗯~其实我对贵司的面试官印象很好。只不过,现在我的手头上已经有一份11K的offer。来面试,主要也是自己对贵司挺有兴趣的,所以过来看看……”(未完) 这段话主要是陪HR互诈的同时,从公司兴趣,公司职员印象上,都给予对方正面的肯定,既能提升HR的好感度,又能让谈判气氛融洽,为后面的发挥留足空间。...

面试阿里p7,被按在地上摩擦,鬼知道我经历了什么?

面试阿里p7被问到的问题(当时我只知道第一个):@Conditional是做什么的?@Conditional多个条件是什么逻辑关系?条件判断在什么时候执...

终于懂了TCP和UDP协议区别

终于懂了TCP和UDP协议区别

无代码时代来临,程序员如何保住饭碗?

编程语言层出不穷,从最初的机器语言到如今2500种以上的高级语言,程序员们大呼“学到头秃”。程序员一边面临编程语言不断推陈出新,一边面临由于许多代码已存在,程序员编写新应用程序时存在重复“搬砖”的现象。 无代码/低代码编程应运而生。无代码/低代码是一种创建应用的方法,它可以让开发者使用最少的编码知识来快速开发应用程序。开发者通过图形界面中,可视化建模来组装和配置应用程序。这样一来,开发者直...

面试了一个 31 岁程序员,让我有所触动,30岁以上的程序员该何去何从?

最近面试了一个31岁8年经验的程序猿,让我有点感慨,大龄程序猿该何去何从。

大三实习生,字节跳动面经分享,已拿Offer

说实话,自己的算法,我一个不会,太难了吧

程序员垃圾简历长什么样?

已经连续五年参加大厂校招、社招的技术面试工作,简历看的不下于万份 这篇文章会用实例告诉你,什么是差的程序员简历! 疫情快要结束了,各个公司也都开始春招了,作为即将红遍大江南北的新晋UP主,那当然要为小伙伴们做点事(手动狗头)。 就在公众号里公开征简历,义务帮大家看,并一一点评。《启舰:春招在即,义务帮大家看看简历吧》 一石激起千层浪,三天收到两百多封简历。 花光了两个星期的所有空闲时...

立即提问
相关内容推荐