VJ Blog: 2011

Tuesday, 1 November 2011

arm-linux-gnueabi-gcc no such file or directory

I got stuck with this problem for so many days.

I downloaded arm-2010q1-202-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2 
I untar the file with this command.

root@ubuntu:/tmp# sudo tar xfzv arm-2010q1-202-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2

root@ubuntu:/tmp# arm-none-linux-gnuabi-gcc -v

 arm-linux-gnueabi-gcc : no such file or directory

I don't know what was wrong. I think that I follow the manual step by step.
BTW, I am using Ubuntu 10.04.

I can not continue my work. Please tell me what did I do wrong.
Thank you in advance.

SOLUTION:
While cross compiling on 64 bit OS this problem occurs since most of the times cross compiler require lots of 32-bit binaries. So to cross-compile on 64bit we need ia32-libs package

apt-get install ia32-libs

REF:
http://www.friendlyarm.net/forum/topic/1462

Monday, 3 October 2011

Windows 7 states I'm not connected to any networks when in fact I am connected to my wireless network??

http://social.technet.microsoft.com/Forums/en/w7itpronetworking/thread/df17c593-e78f-4878-97b0-7569307934c5

Wednesday, 7 September 2011

printk and its levels

http://www.linuxquestions.org/questions/programming-9/printk-is-not-printing-432386/

If you want to change system parameters, all you need to do is write
the new values to the correct file in /proc/sys. If the file contains
an array of values, they will be overwritten in order. Let's look at
the kernel/printk file as an example. printk was first introduced in
kernel version 2.1.32. The four numbers in /proc/sys/kernel/printk
control the ``verbosity'' level of the printk kernel function. The
first number in the array is console_loglevel: kernel messages with
priority less than or equal to the specified value will be printed to
the system console (i.e., the active virtual console, unless you've
changed it). This parameter doesn't affect the operation of klogd,
which receives all the messages in any case. The following commands
show how to change the log level:

# cat kernel/printk
6 4 1 7
# echo 8 > kernel/printk
# cat kernel/printk
8 4 1 7

A level of 8 corresponds to debug messages, which are not printed on
the console by default. The example session shown above changes the
default behaviour so that every message, including the debug ones, are
printed.

Following levels are available

KERN_EMERG 0
KERN_ALERT 1
KERN_CRIT 2
KERN_ERR 3
KERN_WARNING 4
KERN_NOTICE 5
KERN_INFO 6
KERN_DEBUG 7