怎样看下 qt tiny210 /usr/usr local bin 找不到/t

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
您的访问请求被拒绝 403 Forbidden - ITeye技术社区
您的访问请求被拒绝
亲爱的会员,您的IP地址所在网段被ITeye拒绝服务,这可能是以下两种情况导致:
一、您所在的网段内有网络爬虫大量抓取ITeye网页,为保证其他人流畅的访问ITeye,该网段被ITeye拒绝
二、您通过某个代理服务器访问ITeye网站,该代理服务器被网络爬虫利用,大量抓取ITeye网页
请您点击按钮解除封锁&c++ - How to use Qt app on tiny210 device? - Stack Overflow
to customize your list.
Announcing Stack Overflow Documentation
We started with Q&A. Technical documentation is next, and we need your help.
Whether you're a beginner or an experienced developer, you can contribute.
I want to use a Qt app on a .
I installed Qt ( qt-everywhere-opensource-src.4.8.5 ) downloaded from . I managed to compile a simple application for use on tiny210. The problem is that now when I try to run the app on the device, I get the following errors:
libc.so.6: version 'GLIBC_2.15' not found (required by libQtCore.so.4)
libc.so.6: version 'GLIBC_2.15' not found (required by libQtNetwork.so.4)
There is a libc.so.6 in /lib/ on the target device, but it is version 2.11.
I should mention that before getting those errors I also got errors for not having libQtCore.so.4, libQtNetwork.so.4 and libQtGui.so.4. I fixed those errors just by copying the compiled libraries from my host PC to the device.
First question is: Would there have been a better way to provide the needed libraries, or copying them is fine?
Second question is: How can I get over the errors mentioned above?
EDIT : I've read something about building it static, but I am not sure how, and what are the downsides of this.
EDIT2 : I managed to get over the above errors thanks to artless noise's answer, but now I get: error loading shared libraries: libQtGui.so.4: cannot open shared object file: No such file or directory.
The issue is the cross-compiler (apt-get install gcc-arm-linux-gnueabi) is ARM based and this cross compiler has a newer glibc than on the ARM device.
You can copy the libc from the cross compiler directory to your ARM device.
I suggest testing with LD_LIBRARY_PATH, before updating the main libraries.
Use ls /var/lib/dpkg/info/*arm-linux*.list to see most packages related to the ARM compiler.
You can use grep to figure out where the libraries are (or fancier things like apt-file, etc).
Crosstool-ng has a
script, but I dont see it in the U it is perfect for your issue.
If it is present on your Debian version, I would use it.
The glibc 2.15 is backwards compatible with the glibc 2.11 which is currently on your system.
Issues may arise if the compiler was configured with different options (different ABI); however if this is the case, you will have many issues with your built Qt besides the library.
In this case, you need to find a better compiler which fits your root filesystem.
So to be clear, on the target
mkdir /lib/staging
cp libc.so-2.15 /lib/staging
cd /lib/staging
ln -s libc.so-2.15 libc.so
LD_LIBRARY_PATH=/lib/staging ls
# test the library
You may have to copy additional libraries, such as pthread, resolv, rt, crypt, etc.
The files are probably in a directory like sysroot/lib.
You can copy the whole directory to the /lib/staging to test it.
If the above ls functions, then the compilers should be ABI compatible.
If you have a crash or not an executable, then the compiler and rootfs may not be compatible.
Would there have been a better way to provide the needed libraries, or copying them is fine?
Copying may be fine as per above.
If it is not fine, then either the compiler or the root filesystem must be updated.
How can I get over the errors mentioned above?
Try the above method.
As well, you maybe able to leave your root filesystem alone.
Set-up a shadow directory and
to run the Qt application with the copied files as another solution.
To test this, make a very simple program and put it along the compiler libraries in a test directory, say /lib/staging as above.
Then the test code can be run like,
$ LD_LIBRARY_PATH=/lib/staging ./hello_world
If this doesn't work, your compiler and the ARM file system/OS are not compatible.
No library magic will help.
I've read something about building it static, but I am not sure how, and what are the downsides of this.
I understand this seems like a solution.
However, if the compiler is wrong, this won't help.
The calling convention between OS, libraries and what registers are saved by the OS will be implicit in the compiled code.
You may have to .
11.7k43665
Your Answer
Sign up or
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Post as a guest
By posting your answer, you agree to the
Not the answer you&#39;re looking for?
Browse other questions tagged
Stack Overflow works best with JavaScript enabledTiny210 | S5PV210 ARM Cortex-A8 Board - FriendlyARM
Tiny210 | S5PV210 ARM Cortex-A8 Board
FriendlyARM Tiny 210 Stamp Module with 1 GHz Samsung S5PV210 ARM Cortex-A8 processor.
Specification: Stamp Module
Dimension: 64 x 50 mm
CPU: 1 GHz Samsung S5PV210 with PowerVR SGX540 graphics engine
RAM: 512 MB, 32 bit Bus
Flash: up to 1GB NAND Flash
Serial, SPI, I2C, I2S, SD/MMC, USB, LCD, Camera Interface
Analog Input and Output
User Outputs: 4x LEDs
Expansion headers (2.0 mm)
Power: 2-6V
OS Support
Windows CE 6
Specification: SDK-Board
Dimension: 180 x 130 mm
EEPROM: 256 Byte (I2C)
Ext. Memory: SD-Card socket
Serial Ports: DB9 connector (RS232), total: 4x serial port connectors)
USB: USB-A Host 1.1, miniUSB Slave/OTG 2.0
Audio Output: 3.5 mm stereo jack, connector for a speaker (Class D Amp)
Audio Input: 3.5mm jack + Condenser microphone
Ethernet: RJ-45 10/100M (DM9000)
RTC: Real Time Clock with battery
Beeper: PWM buzzer
Camera: 20 pin (2.0 mm) Camera interface
TV Output: AV Out
TV Input: AV In
LCD: 40 pin (2.0 mm), 40 pin FFC, 40 pin FFC and 45 pin FFC connector
User Inputs: 8x buttons and 1x A/D pot
Expansion headers (2.0 mm)
Power: regulated 5V
Stamp Module<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
您的访问请求被拒绝 403 Forbidden - ITeye技术社区
您的访问请求被拒绝
亲爱的会员,您的IP地址所在网段被ITeye拒绝服务,这可能是以下两种情况导致:
一、您所在的网段内有网络爬虫大量抓取ITeye网页,为保证其他人流畅的访问ITeye,该网段被ITeye拒绝
二、您通过某个代理服务器访问ITeye网站,该代理服务器被网络爬虫利用,大量抓取ITeye网页
请您点击按钮解除封锁&一、编译内核 cp mini210-tvp5150_linux_deconfig .config make 没有出现错误,烧到板上,12寸屏不能显示,修改LCD参数为屏的参数,在arch/arm/mach-s5pv210/mini210-lcds.c static struct s3cfb_lcd wvga_s70 = {
.width = 1024,
.height = 768,
.p_width = 254,
.p_height = 184,
.bpp = 32,
.freq = 62,
.timing = {
.h_fp = 12,
.h_bp = 12,
.h_sw = 4,
.v_fp = 8,
.v_fpe = 1,
.v_bp = 8,
.v_bpe = 1,
.polarity = {
.rise_vclk = 0,
.inv_hsync = 1,
.inv_vsync = 1,
.inv_vden = 0,
};重新编译,OK2. 编译RootFS
按照Tiny210手册编译,启动出错:can't open /r/dev/console
:在文件系统/dev下建立console节点,命令为sudo mknod console c 5 1&
3. 修改触摸屏驱动
因为手上的屏是12寸USB接口的超声波触摸屏,Tiny210原先的驱动不适合使用
<font color="#. 下载tslib1.4: git clone 2.编译
./autogen.sh./configure --host=arm-linux --prefix=/opt/tslib CC=/opt/FriendlyARM/toolschain/4.5.1/bin/arm-linux-gcc
make make install
之前加入--enable-inputapi=no,编译后发现在没有input.so
3. 复制/opt/tslib目录到RootFS相应目录下
4. 修改tslib/etc/ts.conf,去掉module_raw input面前的井号及空格,行首不要留有空格
5. 修改/etc/profile,在后面加入如下代码(event2是我的输入设备):
export TSLIB_ROOT=/opt/tslib
export TSLIB_TSDEVICE=/dev/input/event2
export QWS_MOUSE_PROTO=tslib:/dev/input/event2
export TSLIB_CALIBFILE=/etc/pointercal
export TSLIB_CONFFILE=$TSLIB_ROOT/etc/ts.conf
export TSLIB_PLUGINDIR=$TSLIB_ROOT/lib/ts
6. 在命令行下直接转入ts_calibrate,发现每次都提示校正失败,后面发现ts_calibrate是直接调用/bin/ts_calibrate,那是系统原来的,不适合这里使用,真正有用的是/opt/tslib/bin/ts_calibrate
7.修改/bin/qt4以适应我们的触摸屏,修改后的如下
#if [ -e /etc/friendlyarm-ts-input.conf ] ; then
# . /etc/friendlyarm-ts-input.conf
#true ${TSLIB_TSDEVICE:=/dev/touchscreen}
#if grep -Ei "\&ctp=(1|2|3)\&" /proc/cmdline &/dev/ then
# TSLIB_CONFFILE=/etc/ts-mt.conf
# TSLIB_CONFFILE=/etc/ts.conf
#export TSLIB_TSDEVICE
#export TSLIB_CONFFILE
#export TSLIB_PLUGINDIR=/usr/lib/ts
#export TSLIB_CALIBFILE=/etc/pointercal
export QWS_DISPLAY=:1
export LD_LIBRARY_PATH=/usr/local/lib:$LD_LIBRARY_PATH
export PATH=/bin:/sbin:/usr/bin/:/usr/sbin:/usr/local/bin
if [ -c ${TSLIB_TSDEVICE} ]; then
export QWS_MOUSE_PROTO="Tslib MouseMan:/dev/input/mice"
if [ ! -s /etc/pointercal ] ; then
rm /etc/pointercal
#/usr/bin/ts_calibrate
/opt/tslib/bin/ts_calibrate
export QWS_MOUSE_PROTO="MouseMan:/dev/input/mice"
export QWS_KEYBOARD=TTY:/dev/tty1
export HOME=/root
cd /usr/local/Trolltech/QtEmbedded-4.7.0-arm/demos/embedded/fluidlauncher
./fluidlauncher -qws
8. 输入 qt4看看修改是否成功
阅读(...) 评论()

我要回帖

更多关于 mac usr local 的文章

 

随机推荐