geekmaster's simple guide to tcc (tinycc)

[geekmaster]

Originally Posted by xueyou2

/mnt/us/tcc #pwd
/mnt/us/tcc
/mnt/us/tcc #./uninstall
*** tcc uninstalled ***
/mnt/us/tcc #./install
*** tcc installed ***
Uninstall with /mnt/us/tcc/uninstall
Compile demo.c with "tccmake demo"
mnt/us/tcc #ls -al /usr/lib/libm*


-rwxr-xr-x 1 root root usr/lib/libmenu.so.5->libmenu.so.5.4
lrwxrwxrwx 1root root usr/lib/libmenu.so.5.4

-rwxr-xr-x 1root root usr/lib/libmp3-parser-arm11_elunux.so
Thank you.(With usbnetwork i can access the kindle i still find the same result.)

That shows a missing symlink, as though you used an OLD install script.

Please show the output of this command:

cat /mnt/us/tcc/install

Thanks.

[xueyou2]

#cat /mnt/us/tcc/install
#!/bin/sh
cd /usr/lib
mntroot rw >/dev/null
ln -s /mnt/us/tcc/crt1.o
ln -s /mnt/us/tcc/crti.o
ln -s /mnt/us/tcc/crtn.o
cd /usr/bin >/dev/null
ln -s /mnt/us/tcc/tcc
ln -s /mnt/us/tcc/tccmake
[[ -e libm.so ]]||ln -s /lib/libm.so.6 libm.so
mntroot ro >/dev/null
echo "*** tcc installed ***"
echo Uninstall with /mnt/us/tcc/uninstall
echo Compile demo.c with "tccmake demo"

[geekmaster]

This line "cd /usr/bin >/dev/null" says "change directory to /usr/bin and discard output".

This line "[[ -e libm.so ]]||ln -s /lib/libm.so.6 libm.so" says (while in /usr/bin) "if libm.so does not exists, create a link called libm.so that points to /lib/libm.so.6"

However, earlier you showed "mnt/us/tcc #ls -al /usr/lib/libm*" (after running install) with output that did NOT contain libm.so. This should not be possible without some kind of error message.

Try executing the statements from a command prompt instead of inside the script.

Specifically, "cd /usr/lib", then "ln -s /lib/libm.so.6 libm.so"

If that fails to create the symlink (it works on my K3 with 3.3), you could try "ln -s /lib/libm-2.5.so libm.so" instead (because libm.so.6 is just a symlink itself).

I do not know why your 3.3 is acting differently from my 3.3, but I have seen cases were there were problems creating a symlink to a symlink. So, in your case symlink directly to the library instead of the other symlink as shown above.

[xueyou2]

Originally Posted by geekmaster

This line "cd /usr/bin >/dev/null" says "change directory to /usr/bin and discard output".

This line "[[ -e libm.so ]]||ln -s /lib/libm.so.6 libm.so" says (while in /usr/bin) "if libm.so does not exists, create a link called libm.so that points to /lib/libm.so.6"

However, earlier you showed "mnt/us/tcc #ls -al /usr/lib/libm*" (after running install) with output that did NOT contain libm.so. This should not be possible without some kind of error message.

Try executing the statements from a command prompt instead of inside the script.

Specifically, "cd /usr/lib", then "ln -s /lib/libm.so.6 libm.so"

If that fails to create the symlink (it works on my K3 with 3.3), you could try "ln -s /lib/libm-2.5.so libm.so" instead (because libm.so.6 is just a symlink itself).

I do not know why your 3.3 is acting differently from my 3.3, but I have seen cases were there were problems creating a symlink to a symlink. So, in your case symlink directly to the library instead of the other symlink as shown above.

Yes,it works!Great!

PHP Code:

cd /usr/lib
ln -s /lib/libm.so.6 libm.so

 

/mnt/us/tcc$ tccmake hello -lm
/mnt/us/tcc$ ./hello

x=144.000000, sqrt(x)=12.000000 


Thank you !master.

[geekmaster]

Originally Posted by xueyou2

Yes,it works!Great!
...
Thank you !master.

You are welcome.

I suppose I need to make the script a little smarter. Instead of checking "exists" (-e), it could look for a "file" (-f) of various common versions of libm.*, and link directly to that.

I do not know why the K3 had to be different. My older install script worked fine on DX,DXG,K4,K5. But K3 was missing the math lib symlink (and may have more missing lib links too).

[knc1]

Originally Posted by geekmaster

I do not know why the K3 had to be different. My older install script worked fine on DX,DXG,K4,K5. But K3 was missing the math lib symlink (and may have more missing lib links too).

The K3, v-3.2.1 image I am looking at looks to have a number of "strange things" about its library installation. Both in the compiler search path(s) and the runtime loader's search path(s).

Almost as if lab126 was only concerned about making their own software work and to H... with anyone else's.

For instance, the contents of /etc/ld.so.conf does not correspond to the library installation locations - unless they have some "invented here" program diddling with the run-time loader.

Unfortunately, my K3 is "out of service" for a photo shoot, so I can't actually check its behavior.

[geekmaster]

Originally Posted by knc1

The K3, v-3.2.1 image I am looking at looks to have a number of "strange things" about its library installation. Both in the compiler search path(s) and the runtime loader's search path(s).

Almost as if lab126 was only concerned about making their own software work and to H... with anyone else's.

For instance, the contents of /etc/ld.so.conf does not correspond to the library installation locations - unless they have some "invented here" program diddling with the run-time loader.

Unfortunately, my K3 is "out of service" for a photo shoot, so I can't actually check its behavior.

Another good reason to static link all your apps so they don't need any external loadable libraries. I like static linking so my apps will run on any eink kindle, with no worries about library version mismatch errors, but missing symlinks and other amazon screwups is yet another reason to static link.

[geekmaster]

By the way, I noticed that even when I do a major edit to an existing post, it does NOT add my new signature line. Apparently, only the site mods can add my signature to my old posts.

[knc1]

Two quick notes;

The thread topic is about tcc - so here we are interested in the compiler's search paths.
Question: does tcc support a --static option?

My mention of the runtime loader (which also uses the library files mentioned) is a related issue, but in that case the application would generate an error message when run, not while it was being compiled.

Hmm...
There is a (rarely used) way to poke the runtime loader so that it reports what it is doing, but I have forgotten the details, I will need a bit of RTFM to re-learn that trick.

[geekmaster]

tcc options only use a single "-" (even "-help")":

# tcc -help
tcc version 0.9.25 - Tiny C Compiler - Copyright (C) 2001-2006 Fabrice Bellard
usage: tcc [-v] [-c] [-o outfile] [-Bdir] [-bench] [-Idir] [-Dsym[=val]] [-Usym]
           [-Wwarn] [-g] [-b] [-bt N] [-Ldir] [-llib] [-shared] [-soname name]
           [-static] [infile1 infile2...] [-run infile args...]

General options:
  -v          display current version, increase verbosity
  -c          compile only - generate an object file
  -o outfile  set output filename
  -Bdir       set tcc internal library path
  -bench      output compilation statistics
  -run        run compiled source
  -fflag      set or reset (with 'no-' prefix) 'flag' (see man page)
  -Wwarning   set or reset (with 'no-' prefix) 'warning' (see man page)
  -w          disable all warnings
Preprocessor options:
  -E          preprocess only
  -Idir       add include path 'dir'
  -include f  #include file 'f' before everything else
  -Dsym[=val] define 'sym' with value 'val'
  -Usym       undefine 'sym'
  -M          generate include list. Implies -E
  -dM         generate macros list. Implies -E
  -MT file    use 'file' as target for -M.
Linker options:
  -Ldir       add library path 'dir'
  -llib       link with dynamic or static library 'lib'
  -shared     generate a shared library
  -soname     set name for shared library to be used at runtime
  -static     static linking
  -rdynamic   export all global symbols to dynamic linker
  -r          generate (relocatable) object file
Debugger options:
  -g          generate runtime debug info
  -bt N       show N callers in stack traces
Ignored options (for gcc compatibility):
  -std=X      
  -MD name
  -MP
  -isystem dir

[knc1]

Thanks. My own Kindle is "out of service" so I could not check that for myself.

[deep]

Im not sure if I deleted this file, but if run

tccmake cfile -lpthread 

it shows tcc: file '/usr/lib/libpthread_nonshared.a' not found

I use the version 1.5 provided by geekmaster...

[knc1]

Originally Posted by deep

Im not sure if I deleted this file, but if run

tccmake cfile -lpthread 

it shows tcc: file '/usr/lib/libpthread_nonshared.a' not found

I use the version 1.5 provided by geekmaster...

That input with that message indicates a broken symbolic link chain.
That is: the /usr/lib/libpthread library is a link to a non-existent file.

What Kindle model? (the Kindle Touch in your info box?)
What Firmware version?

[deep]

Originally Posted by knc1

What Kindle model? (the Kindle Touch in your info box?)
What Firmware version?

Yes it's the Kindle Touch...
Firmware is 5.1.0 ....

Yes probably a broken symlink .. I dont have the code sourcery libraries with me though ... maybe someone could share it ?

[knc1]

Originally Posted by deep

Yes it's the Kindle Touch...
Firmware is 5.1.0 ....

Yes probably a broken symlink .. I dont have the code sourcery libraries with me though ... maybe someone could share it ?

First...

Please post the results of this command:

ls -l /lib/libpthread* /usr/lib/libpthread*

If it is only a broken link rather than a missing file, that will give the information required for directions on how to fix it (similar to the libm problem).