Hei,

On Thu, 2006-10-05 at 13:41 +0300, Andrey Khurri wrote:

  
Do you know if this option is supported at all by sbox compilers or
should it be invoked in some other way than '-llibrary' or '-l
library'? I also thought that sbox compilers may have less available
command-line options comparing to "normal" gcc. Can it be truth?
    

No.  Scratchbox compilers are standard GCC cross-compilers.

  
Below is an output of the error for PC target: 

sbox-i686-linux-gcc: -lgthread-2.0: linker input file unused because
linking not done 
sbox-i686-linux-gcc: -lglib-2.0: linker input file unused because
linking not done 
sbox-i686-linux-gcc: -lgobject-2.0: linker input file unused because
linking not done 
sbox-i686-linux-gcc: -lglib-2.0: linker input file unused because
linking not done 
sbox-i686-linux-gcc: ../libinet6/.libs/libinet6.a: linker input file
unused because linking not done 
sbox-i686-linux-gcc: ../libhiptool/.libs/libhiptool.a: linker input
file unused because linking not done 
cc1: error: unrecognized command line option "-lgthread-2.0" 
cc1: error: unrecognized command line option "-lglib-2.0" 
cc1: error: unrecognized command line option "-lgobject-2.0" 
cc1: error: unrecognized command line option "-lglib-2.0" 
    

It would be belpful to know how exactly you invoked gcc, but I'm
guessing you passed the -c option to it.
  
Well, I am trying to compile a project which uses automake tools. So we have Makefile.am which is then used by configure script to produce Makefile. Finally, the compiler gets lots of options. I put below a more detailed part of 'make' output:

if gcc ... (some other options which, however, don't concern us) ...
-I/home/fs/akhurri/debian/hipl/hipl-userspace/agent `pkg-config gtk+-2.0 --cflags`   -g `pkg-config gtk+-2.0 --cflags` `pkg-config --cflags --libs gthread-2.0` `pkg-config --cflags --libs gobject-2.0` ../libinet6/.libs/libinet6.a ../libhiptool/.libs/libhiptool.a -DHIP_GUI_DATADIR=\"/usr/local/share/hipl/libhipgui\" -g -MT libhipgui_a-main.o -MD -MP -MF ".deps/libhipgui_a-main.Tpo" -c -o libhipgui_a-main.o `test -f 'main.c' || echo '/home/akhurri/debian/hipl/hipl-userspace/libhipgui/'`main.c; \
then mv -f ".deps/libhipgui_a-main.Tpo" ".deps/libhipgui_a-main.Po"; else rm -f ".deps/libhipgui_a-main.Tpo"; exit 1; fi
sbox-arm-linux-gcc: -lgthread-2.0: linker input file unused because linking not done
sbox-arm-linux-gcc: -lglib-2.0: linker input file unused because linking not done
sbox-arm-linux-gcc: -lgobject-2.0: linker input file unused because linking not done
sbox-arm-linux-gcc: -lglib-2.0: linker input file unused because linking not done
sbox-arm-linux-gcc: ../libinet6/.libs/libinet6.a: linker input file unused because linking not done
sbox-arm-linux-gcc: ../libhiptool/.libs/libhiptool.a: linker input file unused because linking not done
cc1: error: unrecognized command line option "-lgthread-2.0"
cc1: error: unrecognized command line option "-lglib-2.0"
cc1: error: unrecognized command line option "-lgobject-2.0"
cc1: error: unrecognized command line option "-lglib-2.0"
make[1]: *** [libhipgui_a-main.o] Error 1
make[1]: Leaving directory `/home/akhurri/debian/hipl/hipl-userspace/libhipgui'
make: *** [all-recursive] Error 1


That's right, there is a '-c' option. Also
`pkg-config --cflags --libs gthread-2.0` and `pkg-config --cflags --libs gobject-2.0` outputs are as follows respectively:

-pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include  -pthread -lgthread-2.0 -lglib-2.0

-I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include  -lgobject-2.0 -lglib-2.0

And it seems to me that the latter is exactly what compiler is not able to understand somehow.


Andrey
_______________________________________________
Scratchbox-devel mailing list
[email protected]
http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-devel

Reply via email to