where are gtk+-2.0 libraries in rhe codesourcery toolchain
Linux - Embedded & Single-board computerThis forum is for the discussion of Linux on both embedded devices and single-board computers (such as the Raspberry Pi, BeagleBoard and PandaBoard). Discussions involving Arduino, plug computers and other micro-controller like devices are also welcome.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
where are gtk+-2.0 libraries in rhe codesourcery toolchain
Hi All,
I am using Ubuntu 11.10 and the Code Sourcery 2011.09 toolchain. Our target is a BeagleBoard (ARM). We can use the toolchain to compile for our target successfully, as long as we don't use gtk. When we try to include gtk/gtk we get this:
fatal error: gtk/gtk.h: No such file or directory
We cannot find gtk+-2.0 anywhere in the toolchain.
Can anyone tell us where to find it or do we have to install it and if so, where from?
Thanks for your help.
Last edited by Famwen; 01-30-2012 at 09:02 AM.
Reason: spelling
Distribution: PCLinuxOS2023 Fedora38 + 50+ other Linux OS, for test only.
Posts: 17,513
Rep:
Welcome to LQ.
Quote:
We can use the toolchain to compile for our target successfully,
as long as we don't use gtk.
I guess, you have just been lucky (until now) that no any extra
libraries were required. Usually nothing but the libs supplied by
*libc and gcc are part of a tool chain.
Distribution: PCLinuxOS2023 Fedora38 + 50+ other Linux OS, for test only.
Posts: 17,513
Rep:
Say your other arm stuff has a location like /opt/arm/ .
Then start with glib http://ftp.gnome.org/pub/gnome/sources/glib/ ,
like : cd glib-2.24.2/ && ./configure --prefix=/opt/arm/ && make
&& sudo make install :
Then the libraries will have this location : /opt/arm/lib/
The following packages, atk etc. , something like :
export LD_LIBRARY_PATH=/opt/arm/lib
&& export PKG_CONFIG_LIBDIR=/opt/arm/lib/pkgconfig && <etc.>
And : Please use the Report button :
To get this thread moved to Embedded.
dennis@Ubuntu:~/glib-2.24.2$ ./configure --prefix=/home/dennis/arm-2011.09 && make && sudo make install
It worked fine, however, any compiling that was done was not done with our cross compiler whose name is "arm-none-linux-gnueabi-gcc" is there a way to tell configure to use this compiler?
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for the BeOS... no
checking for Win32... no
checking for Mac OS X Carbon support... checking for style of include used by make... GNU
checking for gcc... arm-none-linux-gnueabi-gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... configure: error: in `/home/dennis/glib-2.24.2':
configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.
We do not know what ./config wants for the --host parameter. Can you help?
configure: WARNING: If you wanted to set the --build type, don't use --host.
If a cross compiler is detected then cross compile mode will be used.
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for arm-strip... no
checking for strip... strip
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking build system type... i686-pc-linux-gnu
checking host system type... arm-unknown-none
checking for the BeOS... no
checking for Win32... no
checking for Mac OS X Carbon support... checking for style of include used by make... GNU
checking for arm-gcc... arm-none-linux-gnueabi-gcc -I /home/dennis/arm-2011.09/arm-none-linux-gnueabi
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... yes
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether arm-none-linux-gnueabi-gcc -I /home/dennis/arm-2011.09/arm-none-linux-gnueabi accepts -g... yes
checking for arm-none-linux-gnueabi-gcc -I /home/dennis/arm-2011.09/arm-none-linux-gnueabi option to accept ISO C89... none needed
checking dependency style of arm-none-linux-gnueabi-gcc -I /home/dennis/arm-2011.09/arm-none-linux-gnueabi... gcc3
checking how to run the C preprocessor... arm-none-linux-gnueabi-gcc -I /home/dennis/arm-2011.09/arm-none-linux-gnueabi -E
no
checking whether to enable garbage collector friendliness... no
checking whether to disable memory pools... no
checking for arm-gcc... (cached) arm-none-linux-gnueabi-gcc -I /home/dennis/arm-2011.09/arm-none-linux-gnueabi
checking whether we are using the GNU C compiler... (cached) yes
checking whether arm-none-linux-gnueabi-gcc -I /home/dennis/arm-2011.09/arm-none-linux-gnueabi accepts -g... (cached) yes
checking for arm-none-linux-gnueabi-gcc -I /home/dennis/arm-2011.09/arm-none-linux-gnueabi option to accept ISO C89... (cached) none needed
checking dependency style of arm-none-linux-gnueabi-gcc -I /home/dennis/arm-2011.09/arm-none-linux-gnueabi... (cached) gcc3
checking how to run the C preprocessor... arm-none-linux-gnueabi-gcc -I /home/dennis/arm-2011.09/arm-none-linux-gnueabi -E
checking for arm-c++... no
checking for arm-g++... no
checking for arm-gcc... no
checking for arm-CC... no
checking for arm-cxx... no
checking for arm-cc++... no
checking for arm-cl... no
checking for c++... c++
configure: WARNING: using cross tools not prefixed with host triplet
checking whether we are using the GNU C++ compiler... yes
checking whether c++ accepts -g... yes
checking dependency style of c++... gcc3
checking for arm-gcc... (cached) arm-none-linux-gnueabi-gcc -I /home/dennis/arm-2011.09/arm-none-linux-gnueabi
checking whether we are using the GNU C compiler... (cached) yes
checking whether arm-none-linux-gnueabi-gcc -I /home/dennis/arm-2011.09/arm-none-linux-gnueabi accepts -g... (cached) yes
checking for arm-none-linux-gnueabi-gcc -I /home/dennis/arm-2011.09/arm-none-linux-gnueabi option to accept ISO C89... (cached) none needed
checking dependency style of arm-none-linux-gnueabi-gcc -I /home/dennis/arm-2011.09/arm-none-linux-gnueabi... (cached) gcc3
checking whether arm-none-linux-gnueabi-gcc -I /home/dennis/arm-2011.09/arm-none-linux-gnueabi and cc understand -c and -o together... yes
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... 64
checking for pkg-config... /usr/bin/pkg-config
checking for gawk... (cached) mawk
checking for perl5... no
checking for perl... perl
checking for indent... no
checking for perl... /usr/bin/perl
checking for a Python interpreter with version >= 2.4... python
checking for python... /usr/bin/python
checking for python version... 2.7
checking for python platform... linux2
checking for python script directory... ${prefix}/lib/python2.7/site-packages
checking for python extension module directory... ${exec_prefix}/lib/python2.7/site-packages
checking for iconv_open... yes
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking whether we are using the GNU C Library 2.1 or newer... yes
checking Whether to cache iconv descriptors... no
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for inflate in -lz... no
configure: error: *** Working zlib library and headers not found ***
If you were using Ubuntu with the Linaro toolchain, you would not need to cross-compile the libs for ARM, you should be able to use dpkg-cross / xapt instead.
Last edited by cnxsoft; 02-14-2012 at 09:31 AM.
Reason: Forget to specify toolchain
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.